View Single Post
Old 05-02-2015, 09:17 AM   #10
skreutzer
Software Developer
skreutzer considers 'yay' to be a thoroughly cromulent word.skreutzer considers 'yay' to be a thoroughly cromulent word.skreutzer considers 'yay' to be a thoroughly cromulent word.skreutzer considers 'yay' to be a thoroughly cromulent word.skreutzer considers 'yay' to be a thoroughly cromulent word.skreutzer considers 'yay' to be a thoroughly cromulent word.skreutzer considers 'yay' to be a thoroughly cromulent word.skreutzer considers 'yay' to be a thoroughly cromulent word.skreutzer considers 'yay' to be a thoroughly cromulent word.skreutzer considers 'yay' to be a thoroughly cromulent word.skreutzer considers 'yay' to be a thoroughly cromulent word.
 
skreutzer's Avatar
 
Posts: 190
Karma: 89000
Join Date: Jan 2014
Location: Germany
Device: PocketBook Touch Lux 3
So what are you actually interested in? Just to make your own format because you can? That's fine, I don't mind ;-)

Quote:
Originally Posted by RobertDDL View Post
No, sorry, I'm not.
Of course you don't have to even bother with interconverting the Markdown flavors, my suggestion was directed to Hitch in case incompatibilities between Markdown flavors are considered a real issue here. But what about switching your parser from your custom syntax to Markdown compatible, but reduced instruction set?

An inline TOC can't be the job of a reading software (or shouldn't), because it would have to make decisions regarding layout, and sometimes the result would be inconsistent with the rest of the publication. Therefore it is the job of the author or generator software, and it would be almost trivial if HTML wouldn't have been designed that poorly in the first place. At least EPUB3 does a much better job in this regard. Please note that reading systems usually implement the TOC of an EPUB in an operational way.

Last edited by skreutzer; 05-02-2015 at 09:33 AM.
skreutzer is offline   Reply With Quote