MobileRead Forums - View Single Post

tomsem · 03-02-2024, 02:01 PM

I downloaded some unsupported language texts from Gutenberg: Czech, Hungarian, Hebrew, Tibetan.

No issues with Czech (but Send To Kindle doesn't complain about these) and Hungarian.

Tibetan didn't work: square boxes where the glyphs should be. Adding a custom font with explicit support for Tibetan didn't help. The ePub file previews correctly. I tried side loading the .mobi version but it didn't even show up in Library listing. I tried .txt but it shows boxes with hex codes in them. And you cannot use custom fonts with .txt files. What does Amazon have against Tibetan?

The Hebrew samples from Gutenberg did not specify page-progression-direction="rtl" attribute in <spine> tag. Apple Books figures it out without it and properly assumes 'right binding'. I had to add it explicitly before converting to KFX to achieve correct behavior.

No hyphenation, of course.

03-02-2024, 02:01 PM	#1482
tomsem Grand Sorcerer Posts: 6,959 Karma: 27060153 Join Date: Apr 2009 Location: USA Device: iPhone 15PM, Kindle Scribe, iPad mini 6, PocketBook InkPad Color 3	I downloaded some unsupported language texts from Gutenberg: Czech, Hungarian, Hebrew, Tibetan. No issues with Czech (but Send To Kindle doesn't complain about these) and Hungarian. Tibetan didn't work: square boxes where the glyphs should be. Adding a custom font with explicit support for Tibetan didn't help. The ePub file previews correctly. I tried side loading the .mobi version but it didn't even show up in Library listing. I tried .txt but it shows boxes with hex codes in them. And you cannot use custom fonts with .txt files. What does Amazon have against Tibetan? The Hebrew samples from Gutenberg did not specify page-progression-direction="rtl" attribute in <spine> tag. Apple Books figures it out without it and properly assumes 'right binding'. I had to add it explicitly before converting to KFX to achieve correct behavior. No hyphenation, of course. Last edited by tomsem; 03-02-2024 at 02:06 PM.