Trying to simplify my work flow (confused about the heading/language again)

[Tex2002ans]

Originally Posted by odamizu

Omigod! I've been doing this wrong for years!

I've always used widows:0, orphans:0 to get pages to be the same length — and it works, I just had to ignore the fact that my css never fully validated.

And there was a lot of bogus information about widows/orphans: 0 floating around for years. Luckily, it all looks to be ironed out now.

[odamizu]

Originally Posted by Tex2002ans

And there was a lot of bogus information about widows/orphans: 0 floating around for years.

Okay, that makes me feel better cuz I know I didn't come up with widows/orphans:0 on my own. I read it somewhere while trying to figure out how to get my pages to be the same length.

Speaking of which, the two remaining validation errors that I've learned to ignore are: unrecognized media amzn-kf8 and Property adobe-hyphenate doesn't exist

Is there a correct way to do @media amzn-kf8 and adobe-hyphenate to clear those errors as well?

[Tex2002ans]

Originally Posted by odamizu

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.

Originally Posted by odamizu

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:

• 2016 "Preventing hyphenation in chapter titles?"
• 2018 "Auto-Hyphenation"
• 2019 "Turn off ligatures (temporarily)?"

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.

[odamizu]

Thanks, Tex2002ans.

I understand media queries and adobe-hyphenate. What I meant was, I use them for my own purposes, but it always throws a validation error, which I ignore. Then the "invalid" css succeeds in making my ereaders do what I want them to.

I was just wondering if there was a different media query that wouldn't throw a css validation error, but it looks like "amzn-kf8" is the proper media type for kf8, according to the Kindle Publishing Guidelines.

And if adobe-hyphenate is the proper css for ADE/RMSDK, that answers that question as well.

But at least I got rid of the widows/orphans validation error

[yekim54]

Originally Posted by odamizu

Omigod! I've been doing this wrong for years!

I've always used widows:0, orphans:0 to get pages to be the same length — and it works, I just had to ignore the fact that my css never fully validated.

I never realized widows:1, orphans:1 would do what I wanted and validate.

Same here. I've been using the advice in the following post the past 9+ years:

https://www.mobileread.com/forums/sh...2&postcount=19

[Tex2002ans]

Originally Posted by odamizu

But at least I got rid of the widows/orphans validation error

Originally Posted by yekim54

Same here. I've been using the advice in the following post the past 9+ years

Well wipe that 0 and make it a 1.

0 is invalid, always has been:

CSS specs (widows and orphans):

Only positive integers are allowed as values of orphans and widows. Negative values and zero are invalid and must cause the declaration to be ignored.

Originally Posted by odamizu

What I meant was, I use them for my own purposes, but it always throws a validation error, which I ignore.

What throws a validation error?

epubcheck? Calibre's check? Or something else?

Originally Posted by odamizu

Then the "invalid" css succeeds in making my ereaders do what I want them to.

When CSS runs against a property it doesn't understand, it's designed to completely ignore that part. (For example, if a CSS2 reader runs across CSS3, it will also have no idea what those properties mean... but it will render the parts it does understand.) So proprietary entries like adobe-hyphenate shouldn't hurt one bit.

But, there are a few CSS implementation bugs to note:

• RMSDK doesn't like actual invalid code. (Missing ; or missing a {}.)
  • It chucks away THE ENTIRE CSS file.
• Other devices have issues with Media Queries.
  • Example, there was bugs on Nooks where everything after a Media Query (even if valid) got ignored.
  • Key is to move them to the very end, or in their own separate CSS file: https://github.com/dvschultz/99problems/issues/22

[DiapDealer]

Originally Posted by Tex2002ans

What throws a validation error?

epubcheck? Calibre's check? Or something else?

More than likely she's talking about the online W3C CSS validation service. That's what Sigil's CSS validation tool uses.

[odamizu]

Originally Posted by DiapDealer

More than likely she's talking about the online W3C CSS validation service. That's what Sigil's CSS validation tool uses.

Bingo! When I check my css thru Sigil using W3C CSS validation service, it always gives me "unrecognized media amzn-kf8" and "Property adobe-hyphenate doesn't exist".

I ignore it, my ereaders ignore it, and all is good except the OCD part of me that would rather get a clean bill of health on my css