Quote:
Originally Posted by mergen3107
Adding fonts to kindle_abiword/share/fonts/ did not trigger font cache update. Abiwork launched instantly and new fonts did not appear.
Somehow, highlighting the text and choosing its font through Ctrl+D (paragraph options) doesn't work - it falls back to some weird font named "\XKt", where X is a weird symbol looking like curvy small omega with a bar with ticks. See screenshot.
From other news, scrollbars are now much bigger and more usable.
Language selection works! Windows is now scaled much bigger, and usable, including bigger scrollbars. I was able to select Russian - although I need to fix my keyboard layout first to test its spelling.
|
I was under the (wrong) assumption that new fonts would be detected automatically when they were added. Last night I added instructions to the main post after I added some fonts myself to test it out. Also, I'm pretty damn sure it checks /mnt/us/fonts, so if you already have some there try just deleting the cache files as outlined below before adding anything to /mnt/us/kindle_abiword/share/fonts. I don't know what, if anything happens if you have the same fonts present in both directories. Out of caution I would delete them from /kindle_abiword/share/fonts if you have them in the other place too.
"I shipped a font cache with the release, because font cache generation takes about 45 seconds. If you already have custom fonts on your Kindle, or want to add some to /kindle_abiword/share/fonts, you will need to delete the font cache files in /kindle_abiword/.cache/fontconfig. Once you delete those files and relaunch Abiword, it will look like the program isn't launching, but really it's building the new font cache silently. Please be patient. Every launch after that is quick and normal. Please don't try to launch Abiword a second time while this process is working. It will open when the process is complete. It's normal to see your home screen until it launches."