View Single Post
Old 10-12-2019, 06:39 PM   #33
Tex2002ans
Wizard
Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.
 
Posts: 2,306
Karma: 13057279
Join Date: Jul 2012
Device: Kobo Forma, Nook
Quote:
Originally Posted by odamizu View Post
Is there a correct way to do @media amzn-kf8
That's a Media Query.

If you read the Kindle Publishing Guidelines (PDF), it's under "Appendix D: Media Queries"... they give example code.

amzn-ke8 is not applicable to EPUB readers, so they (theoretically) should ignore that section of code, but support for Media Queries depends on device. (And many are buggy.)

As long as you code things properly, there shouldn't be much harm in using them.

Quote:
Originally Posted by odamizu View Post
adobe-hyphenate to clear those errors as well?
I wrote about the valid way to apply CSS hyphens (and explain each of the settings) in multiple different posts:

adobe-hyphenate is/was a valid way to apply it only in ADE/RMSDK... but I would still recommend against trying to disable hyphenation.

Side Note: There are also a few newer things in CSS3 dealing with hyphenation. Like specifying how many characters allowed to the left/right of the hyphens, or how many hyphen line-endings allowed in a row.

See above topics for many more details.

Last edited by Tex2002ans; 10-12-2019 at 06:45 PM.
Tex2002ans is offline   Reply With Quote