Quote:
Originally Posted by Solitaire1
The reason I mentioned verbosity is to avoid ambiguity and confusion. However, there are ways to reduce the amount of code needed while still avoiding confusion and ambiguity.
One way via the use of commonly established defaults. The only time coding is needed is if it isn't the default. As an example, the default is one blank line between each paragraph (the amount of space is determined by the font in use), but this can easily be changed from this starting point. But if the default is fine no coding is needed.
Another way that might work even better is to avoid formatting within the ebook itself. Instead, the parts of the ebook are tagged to indicate what they are (such as Main Body, Chapter Heading, Page Header, and Page Footer) without any indication how they are to be displayed. This is one of the ideas behind CSS (separating the formatting of the text from what the text is).
The way the text will be displayed is handled by the ebook reader itself via a set of display defaults (such setting the reader to display the Main Body in Times New Roman 12 point with a 36 point indent on the first line of each paragraph and no blank space after the paragraph). The advantage of this is that the same ebook can be used on various ereaders, and each reader can be set to display the text in a manner suitable for it. It also avoids the problem of some types of formatting (such as full justification, and certain fonts) not being available since it's an issue of the ereader, not the ebook format.
|
All good points, and one more reason I use FB2. The file is
only concerned with content, and the display and formatting is handled by the reader, which is usually tailored for the device. So reading the same book on a PocketBook360 (5" display) and an Irex DR1000S (10" display) will obviously result in different formatting, different fonts (types as well as sizes), and so on.