Quote:
Originally Posted by kovidgoyal
1) If you remove the language from calibre metadata it will be removed from the book when the metadata in the book is updated. That is the desired and correct behavior. And if you want to change editor preferences, the preferences in the last closed instance will win. So close all but one instance and change them there.
|
The problem is that some imported Docx don't set the Language in the Calibre Meta Data. I don't know why.
Generally, yes, the ebook metadata should reflect the Calibre data, but surely the dc:language field should never be completely deleted silently?
I've solved this by making sure the Language is not empty in the Calibre Metadata GUI when I add a docx.
I guess I had more than one instance of the editor open. I do know about last one closes, wins!
Quote:
Originally Posted by kovidgoyal
2) This is a bug in the Kobo firmware, not calibre. Spaces or indeed any legal characters in a font file name dont prevent them from working or make them incorrect. The is no "correct" filename for a font file.
|
I think I didn't explain properly. The Kobo doesn't care if there are spaces or not. The Check program in the Editor complains about spaces in the filenames. If Check "fixes" this or it's manually edited, the fonts then don't work in the Kobo, but did before!
Embed Fonts in the GUI of Conversion often adds spaces (Kobo doesn't care, but Check does). If I use Embed Fonts in the Editor it never puts spaces and creates a fonts.css. That works with Kobo and Check.
So
a.) The Conversion GUI and Editor GUI do fonts differently, the Editor version is compatible with Check.
b.) There is no FW issue on the Kobo, it works with or without spaces in the Font file name.
c.) If there are spaces and Check complains, and you fix it so that Check and Epub Check both pass, then the fonts don't work on the Kobo. If you ignore Check's complaint, the Kobo is fine.
Quote:
Originally Posted by kovidgoyal
3) Opena bug report and attach a sample demonstrating the issue.
|
Where do I open a bug report?
The font-weight: 5; in the Gaelic font always happens with Embed Fonts (Conversion GUI or Editor, on the Editor there is a message about 400)
The list of panose numbers in a font css after embed font is rare. I don't remember which docx conversions caused it.
Thanks.
So:
1) I need to make sure Language Field in Metadata is not empty. I don't know why sometimes it is. I always check metadata and browse for cover after a docx import as they never have a cover.
2) For now I will delete fonts in Editor and use Embed via Editor, OR ignore Check's complaint about spaces or other illegal characters as "fixing" breaks it. Certainly there is a bug in Check as to how it automatically changes font names, but manually editing fails, so either leaving it alone or using Embed in the Editor is the solution. It's not the Kobo as it copes with either version of Embed Fonts (spaces or not).
3) Not a big deal. Simple to fix in fonts.css or page_styles.css and actually no ereader I have cares. I think only Check finds the numeric font weight or panose list a fault. Not sure about Epub Check.