Preventing hyphenation in chapter titles?

[AlexBell]

Originally Posted by JSWolf

You cannot use Sony Readers to test hyphenation. They don't support hyphenation so they wont ever hyphenate. The version of ADE used is either too old or Sony chose not to support hyphenation.

That's not my experience. I'm looking at the screen of my Sony PRS T3 as I type this, and although I can't provide a screenshot I can see that

friend of her childhood Vladimir Mihailovitch breaks at Mihailo-
vitch and provides a hyphen.

[stumped]

Yes, like I said. The annoyance is that it hyphenates badly and you cannot disable it, you have to edit the book cuss and add a line to suppress it.
But mine is long gone and I will not ever buy another sony reader. The t3 is very fragile.

[JSWolf]

Originally Posted by stumped

Yes, like I said. The annoyance is that it hyphenates badly and you cannot disable it, you have to edit the book cuss and add a line to suppress it.
But mine is long gone and I will not ever buy another sony reader. The t3 is very fragile.

Sony no longer makes Readers and the T3 is no more or less fragile than Amazon or Kobo. It all depends on how you treat your Reader.

I have a T1 that still works. But it is very slow and doesn't handle high res graphics all that well.

[graycyn]

Originally Posted by JSWolf

If you are using the hyphenation dictionary that comes with the firmware, that's fairly useless as well because the settings in the hyphenation dictionary are set too high.

LEFTHYPHENMIN 5
RIGHTHYPHENMIN 5

That means you won't get hyphens unless the line can handle 6 characters (including the hyphen). Also, words won't hyphen if they are less than 5 to the left & right of the hyphen. I found a hyphenation dictionary that works very well and set the options to allow more hyphenation and less craters (gaps). Install it and try your ePub again.

https://www.mobileread.com/forums/sho...d.php?t=252405

I've installed your hyphenation dictionary, thank you!

However, using only

-webkit-hyphens: none !important;
-epub-hyphens: none !important;
-moz-hyphens: none !important;

still worked on the Kobo Aura HD, at massive font sizes and margins there were NO HYPHENS in my chapter headings.

I ran through the assorted Android apps that I've explored in the past, there was only ONE that showed hyphens in chapter headings and that was the Nook app. It seems that most of the apps I tested limit the size you can increase the font and also the same with margins, so making chapter headings break and hyphenate in those apps simply couldn't happen in the case of this book.

The W3C CSS validator did, however, consider that both adobe-hyphenate and hyphens properties were ERRORS for CSS 2 and CSS 2.1.

The actual error messages were:

h3 Property adobe-hyphenate doesn't exist : none
h3 Property hyphens doesn't exist in CSS level 2 but exists in [css3] : none

So perhaps the safest thing is to include the adobe-hyphenate, which should fix the book for the Nook app and just ignore the error message? The book seems to work fine even if I include this and have supposedly invalid CSS.

[Jellby]

Originally Posted by graycyn

The W3C CSS validator did, however, consider that both adobe-hyphenate and hyphens properties were ERRORS for CSS 2 and CSS 2.1.

Then I'm sorry but the W3C CSS validator is wrong (for our purpose at least). As said before, the CSS spec says that unknown properties should simply be ignored. There should be an option to treat non-existing properties as warnings.

A different thing would be, for instance, if you had "visibility: none". "visibility" is a known property, but "none" is not an allowed value for it, so that's clearly an error.

[graycyn]

Originally Posted by Jellby

Then I'm sorry but the W3C CSS validator is wrong (for our purpose at least). As said before, the CSS spec says that unknown properties should simply be ignored. There should be an option to treat non-existing properties as warnings.

A different thing would be, for instance, if you had "visibility: none". "visibility" is a known property, but "none" is not an allowed value for it, so that's clearly an error.

Thank you and thank you everyone! I feel better about including adobe-hyphenate now! Before, I just felt completely unsure, since it was an error message rather than a warning.

The Android apps I ran the book through (in case anyone is interested) were:

Aldiko, Bluefire, Bookari, Cool Reader, FBReader, Gitden Reader, Google Play Books, Kobo, Lithium, Moon+ Reader, Nook, Overdrive, Pocketbook and UBReader.

Some supported the CSS better than others, but the book was readable in all with or without adobe-hyphenate included.

Sent from my Nexus 9 using Tapatalk