Quote:
Originally Posted by Avistew
I'm used to programs that do it automatically, although I've only seen that in French, I'm realising now. I guess because French has longer words as well as more logical rules for hyphenating, such programs are both more needed and easier to make.
Basically the program decides if it's better to leave a word whole or to cut it, and where to cut it (usually between double consonants, always between syllables).
Since in French one syllable doesn't have any influence on how the previous or next one are pronounced, cutting between syllables doesn't make it harder to read at all.
I'm guessing this isn't supported in lrf though. I know rtf and doc files support it in French though, but all my programs are in English now and I can't find the option to do that anywhere.
I've also been having trouble with special spaces, the type that can't be cut.
For instance in French, double punctuation has one space before and one space after (double punctuation is ";" ":" "?" "!" and French quotation marks). The space before (or after, for opening French quotation marks) cannot be cut (it's a specific one different from a regular space) and needs to be linked to the word before (after) it.
This isn't supported in lrf so you sometimes end up with these symbols at the beginning of a line, which can be very annoying.
It is however supported in doc and rtf as a special symbol, but I'd have to see if these special symbols are recognised on the reader.
If they are, I might end up switching to rtf for my favourite format.
|
I used to use RTF for my ebooks, but I ran into a very frustrating problem with typefaces. What I found with RTF files on my ebook reader is that I haven't been able to get it to consistenly display the general default typeface that I want (serif, san-serif, or monospace). With many RTF ebooks, they display in the default san-serif typeface, regardless of the actual font in the RTF file. In the stories that I write, I use specific typefaces to indicate what the text is (main text, character's thoughts, headings, and so on).
That is the main reason that I switched to PDF for my ebooks. I use my word processor to make my ebooks and I can take full advantage for its formatting capabilities (including hard spaces which is one way to solve the double punctuation problem that you mentioned). When I'm finished, I can export them to PDF and they will look exactly they way I want them to. Although I do lose the ability to increase the font size, the control over an ebook is worth the tradeoff.