Quote:
Originally Posted by jandrew
Not sure what you mean here, markdown always supported atx style headings like:
# level one heading
## level two heading (and so on)
or am I missing your point in this grepping matter?
|
Sorry, my mistake then -- I had been referring to the Markdown flavor that is described in the Wikipedia article,
http://en.wikipedia.org/wiki/Markdown which states that headings level 1 are followed by a line of === while headings level 2 are followed by a line of ---, and only from heading level 3 on the # prefix is used.
http://daringfireball.net/projects/m.../syntax#header states that headings can either have that style, or # and ## for levels 1 and 2 -- in that second case, this is exactly the same what I do. Some other differences remain, but they are not grave.
Quote:
Originally Posted by Hitch
Quite honestly, despite his multiple explanations, I'm damned if I understand WHY, because the entire choice seems to be about the idea that the NCX is superfluous, and the OPF unnecessary, and that it's "needlessly complicated," which is great if you're dealing with a one-page long
book, but once you're past 270KB, you have other choices to make...
|
This is a misunderstanding, sorry if I have contributed to it by not having made my point clear enough. Whatever I've said about ePub in another thread, I am really
not proposing plain text as a better alternative to ePub. But, plain text exists, and is here to stay, and will always be the most easily accessed and most compatible format available, so,
when you use it, it makes sense to give a few thoughts to
how you use it.
Plain text to be read
as is is one thing, converting it to something else (like ePub, giving you a TOC) is another thing -- I've tried to cover both, but my emphasis is on the first. (That other thread, BTW, was about a software that converts plain text to ePub, where the author MobiEpubMaker said "Italic/bold style can't be supported by text file so it can't be supported by this software", so I just wanted to show that, along with headings, it can be.)
And, BTW, my InkPad reads plain text quite nicely, and when reading a novel, whether p- or e-book, I usually don't look at the TOC anyway. To the InkPad a heading in a plain text file is a line that is preceded by 3 blank lines -- easily done. And, it ignores blank lines, so I replace them with something unobtrusive. Or, I convert the text to HTML to ePub and read the ePub. All this I can easily do with a plain text file, without needing a markup language,
if it follows some simple style conventions.
But, again, I only wanted to discuss
how to use plain text in a certain context,
when it is used. (And, on a personal note, I have a blind friend for whom plain text is the only format she can reliably read on all of her devices -- this has taught me to value simplicity.)