Quote:
Originally Posted by mandy314
Thank you, DuckieTigger. (Wonder, how they achieve this)
Now for the pre-rendering. [imho]Putting soft-hyphens or html-tags for hyphenation in the file is a good thing. It is inside the scope of html/css and can bring some advantages: uk vs us-hyphenation, exclusion of names of places/persons etc. Depends how good it is done by publishers/amazon.
|
I don't believe that soft-hyphens are inserted everywhere. There probably is an option to override automatic hyphens on a per word basis for exceptions. May that be either different rules by specifying a different language (e.g. in mixed language texts), forcing no hyphenation, and adjusting the placement with soft hyphens (names, places, madeup words).
It doesn't really matter if possible hyphen positions are inserted before or not - that is only half the problem. The actual hyphenation must be done on the fly to have it look right. It is a non-trivial problem and requires a very good algorithm (if Amazon is smart they use a multi pass algorithm). Otherwise with dumb hyphenation you can end up with hyphens everywhere - which looks stupid. What happens on Amazon's hyphenation looks very good - very seldom are hyphens displayed and I have never run accross a page with too many (e.g. there is no
OMG, every other line is hyphenated). There is a fallback occasionally when hyphenation fails - sometimes a line is not justified when it should. I believe that is done when the hyphenation algorithm cannot decide fast enough on how to optimize gaps between words trying out different hyphen positions. I rather have very very few ragged right lines than a forced justification creating too much white space. Those lines would stick out like a sore thumb if forced.
Overall very happy with hyphenation on the Voyage. And if that requires a new file format to preprocess and assist the on-the-fly algorithm, then I am all for it. The results are amazing and good looking.