[quiris]

Originally Posted by quiris

KDP service works in the same manner as PD Service. So I wrote to KDP Team about the issue and I got answer

A new status update. After a couple of months waiting for answer I got another curious answer:

I worked with our technical team and got to know the below:

The only difference between test20.epup and test21.epub is
in test20.epub's font file:
p*{ font-family: "Lobster 1.4"; }

in test21.epub's font file:

p*, h1* { font-family: "Lobster 1.4"; }

The content present in the only html is

<!-- h1>test</h1-->

<!--p>test</p-->

In test20.epub the font-family lobster is getting applied only to P tag and the other tag h1 gets the default family.

Here font-family "lobster" is calculated as the major font family and is placed in the body tag.

Now the default font-family getting applied in the h1 tag is getting overridden by "lobster" and hence this is a conflicting behavior and hence font-fix tool is doing a strip fix .

In test21.epub since the font-family is getting applied to both p tag and h1 tag the font-family is maintained. Here the majority font-family is lobster and is not conflicting

The fix for this is to use the same font file as test21.epub or give a separate font-family for h1 tag.

In case if you have more questions, do not hesitate to contact us back, we are here to help and we will gladly assist you.

Thanks for using Amazon KDP.