epub-azw3 @page in comment prevents publisher fonts

[phossler]

I think there is a conversion problem epub --> azw3 that affects Publisher Fonts in my Kindle touch

I have this is my style sheet for an epub. Doing a 'defaults' conversion makes the Publisher Font what looks like bold Helvetica

If I insert a space between '@' and 'page' or '@ page' then the publisher font setting is correct.

I would have thought that the comment would be ignored during conversion or by the KT

/* Pixels are used for @page and body (for the ereaders that will recognize 
 them) because pixels don't scale and if a reader increases the text size, we 
 don't want the margins to blow up. Note that these values will produce 
 extra-wide margins on the Kindle Fire, because the view for that ereader is 
 narrow already. */
html, body {
  height: 100%;
  margin: 0;
  padding: 0;
  border-width: 0;
  font-family: "Georgia", serif;
}
@page {
  margin: 5pt;
  }

It's easy enough to fix, but I have to re-edit a number of epubs to insert that space

[JSWolf]

You will need to post the entire CSS so we can see what the coding is for the embedded fonts. @page is not the problem.

[phossler]

Originally Posted by JSWolf

You will need to post the entire CSS so we can see what the coding is for the embedded fonts. @page is not the problem.

No problem. I'll do a 'before' and 'after' with a bare bones epub, and convert to azw3.

I'm using KindlePreviewer to check

That can be my week end project

Now with my luck, it won't be reproduce-able with a small epub.

I have an epub (#1) that converted fine, and an epub (#2) that didn't

Transplanting the 2 stylesheets #1 --> #2 caused #2 to convert

Transplanting the 2 stylesheets #2 --> #1 caused #1 to not convert correctly

Inserting the space into the @page inside the comment in #1 and then converting allowed publisher fonts to be used

BTW, KindleGen did not work either, so I really don't think it a Calibre issue, but more of a Kindle issue

[kovidgoyal]

All calibre conversions contain @page, that is definitely not the problem. Most likely there is something in the stylesheet the kindle cannot handle and puttin a space after @ is causing parsing for the whole stylesheet to fail, thereby allowing the book to work.

[phossler]

Originally Posted by kovidgoyal

All calibre conversions contain @page, that is definitely not the problem. Most likely there is something in the stylesheet the kindle cannot handle and putting a space after @ is causing parsing for the whole stylesheet to fail, thereby allowing the book to work.

I realize that @page is used and normally does not cause any problems.

However, in this case the @page was in a comment in a stylesheet with regular text/words following it. The rest of the stylesheet had the @font lines needed to embed the publisher fonts

I'm leaning towards a problem on the Kindle side

I was thinking that the Kindle was not honoring the comments and trying to actually process the @page command unsuccessfully and caused the style sheet to be ignored, and therefore the publisher fonts also in the failed stylesheet were ignored

It appeared to me that adding the space and making it '@ page' would pass the Kindle parser, and then the style sheet would not fail and thus the embedded fonts would be displayable bu using the Kindle Publisher Font.

I want to run a simple test to do a little more testing

[JSWolf]

If you don't post your CSS, it's all a guessing game.

[phossler]

Originally Posted by JSWolf

If you don't post your CSS, it's all a guessing game.

Understand

After I try my tests to verify that I can reproduce my issue, I'll post

[phossler]

The 'With At' have the @page in the comment on line 28 of Georgia.css

The 'Without At' have a space between the @ and the page in the comment on line 28 of Georgia.css

As far as I can tell, that's the only difference.

Side_by_Side show the Kindle Previewer with Publisher Fonts for both.

Thanks for looking

[kovidgoyal]

https://github.com/kovidgoyal/calibr...5fe2531066ac0b

[phossler]