KFX output linux

[xxyzz]

I'm now trying to figure out how sections are created, I guess each block level HTML tag is a section?

I think the kindle previewer cli must be able to "see" the book HTML since it could ignore hidden tags and find the css rules of a tag. The style rules are tricky to implement, maybe using a headless browser?

Here is the code: https://github.com/xxyzz/kpfgen, it could only add the cover section for now.

[jhowell]

Originally Posted by xxyzz

I'm now trying to figure out how sections are created, I guess each block level HTML tag is a section?

Each individual HTML file of the EPUB being converted becomes a section. For reflowable books sections usually correspond to chapters. For fixed-layout books, such as comics, sections are individual pages or page spreads. Sections are called skeletons in KF8 format.

Originally Posted by xxyzz

I think the kindle previewer cli must be able to "see" the book HTML since it could ignore hidden tags and find the css rules of a tag. The style rules are tricky to implement, maybe using a headless browser?

The Kindle Previewer parses the HTML and CSS contained in an EPUB to determine what styles are applied to each element and produces the KFX equivalents for those styles with some adjustments.

Originally Posted by xxyzz

Here is the code: https://github.com/xxyzz/kpfgen, it could only add the cover section for now.

I will take a look at it when I have some more free time.

[jhowell]

Originally Posted by xxyzz

Thanks! Are there any other table, row or field not used in KFX file?

I started looking at your kpfgen repository and realized when I answered this question originally that I forgot about some key/value pairs that are removed during conversion from KPF to KFX. Those keys with local symbols starting with yj.authoring, yj.conversion, yj.print, or yj.semantics are not needed.

[xxyzz]

I have figured out how to use selenium to check if an element is displayed and get all the css rules applied to it.

I guess the text of tags in the same "block" are in the same "structure", probably by checking the "display" css rule. But I don't know which html tag creates the "container" type "structure". It seems the table tag creates the "table" type, and most tags are "text" type.

I could get all the css rules of an element but kindle previewer only uses a few rules on an element and it also change the rule type and value, for example, "padding-left: 1em;" is changed to

margin_left: {
    value: 3.7039999961853027e0,
    unit: percent
  }

I hope the original rule could work so I don't have to guess how they compute this value...

[jhowell]

Originally Posted by xxyzz

I guess the text of tags in the same "block" are in the same "structure", probably by checking the "display" css rule. But I don't know which html tag creates the "container" type "structure". It seems the table tag creates the "table" type, and most tags are "text" type.

As far as I know "structure" is only used for organization of the Ion code and has no semantic meaning. KFX renders the same if a structure is replaced by its contents.

Originally Posted by xxyzz

I could get all the css rules of an element but kindle previewer only uses a few rules on an element and it also change the rule type and value, for example, "padding-left: 1em;" is changed to

margin_left: {
    value: 3.7039999961853027e0,
    unit: percent
  }

I hope the original rule could work so I don't have to guess how they compute this value...

This is an example of "Enhanced Typesetting". Amazon applies heuristics to transform formatting for more consistent rendering across books. In this case making the amount of padding dependent on the screen size instead of on the font size. Sometimes it works and other times it messes things up.

I believe using the original style will work but of course it will render differently from what Amazon produces.

[xxyzz]

The code kind of works now. I test this book https://standardebooks.org/ebooks/le...d/john-tenniel and some titles in context table are not clickable and images somehow can't display. And I haven't add any css rules.