View Single Post
Old 10-02-2014, 07:29 PM   #85
Tony_A20
Enthusiast
Tony_A20 knows what's going on.Tony_A20 knows what's going on.Tony_A20 knows what's going on.Tony_A20 knows what's going on.Tony_A20 knows what's going on.Tony_A20 knows what's going on.Tony_A20 knows what's going on.Tony_A20 knows what's going on.Tony_A20 knows what's going on.Tony_A20 knows what's going on.Tony_A20 knows what's going on.
 
Tony_A20's Avatar
 
Posts: 39
Karma: 25000
Join Date: Dec 2009
Device: Kindle 3
Understand The KDP Team

Hello Quiris,

Thanks for posting the KDP Team status update (however cryptic).

Although I’m not exactly sure what the writer means by the use of “*” this is what I understand:

Two HTML documents were tested each with the same content, but with different styling declarations.

The document contents were:

<h1>test</h1>
<p>test</p>

The first document (20), had the style p {font-family: “Lobster 1.4”;}

The second document (21) had the style p, h1 {font-family: “Lobster 1.4”;}

When the first document (20) was parsed by the KDP upload software, the Lobster font used for the paragraph tag was considered more significant than the default font used for the heading tag, and consequently was considered applicable to the complete document body.

Apparently , because the heading tag used a default style rather than the style assigned to the document body, it caused an error situation and a KDP software error handling routine disallowed and removed the conflicting font from the document.

When the second document (21) was examined by the KDP upload software, the Lobster font was again assigned as a document-wide parameter.

In this document, because there was no difference in font use between the tagged text and the body parameter, no program editing error occured, the error trap did not execute, and the font was included in the document.

If my understanding is correct, there are three separate errors in the KDP upload software:


1. The algorithm used to determine font use and applicability is logically incorrect.
2. The arbitrary application of a partictular font to the whole document thereby essentially negates any default expectations and cause an error condition.
3. The error handling solution to the problem caused by 2. is incorrect.

Conclusion: poor system analysis, poor design, poor programming.

Solution: none proposed by the KDP Team.

A shot-in-the-dark work-around for us poor users:

Choose and list all used fonts in the body tag leaving no default text.
Assign a separate style selector classification for each type of font use.
Complain like hell to KDP.

Is my understanding correct; is the work-around nonsense?

Tony
Tony_A20 is offline   Reply With Quote