Quote:
Originally Posted by hawhill
Just go and try, I'd say. You can bind-mount another freetype in place and restart the framework, no permanent changes needed.
|
Yep, I always forget that it's linux, after all.
Well, did it.
Device:
Kindle Paperwhite with firmware 5.3.3
I've enabled the "USE_ALT_FONTS" hack.
I've uploaded the libfreetype.so.6.8.1 packaged by ixtab to /mnt/us and I've bind-mounted it as suggested:
Code:
mount -o bind /mnt/us/libfreetype.so.6.8.1 /usr/lib/libfreetype.so.6.3.20
Then I restarted framework (via JBPatch). The library got loaded painlessly. Result:
no damage, just some rendering issues:
- The 1st snapshot shows the "Aa" dialog with the default library. The "Junicode" font is garbled.
- The 2nd snapshot shows what happens with libfreetype.so.6.8.1. "Junicode" is OK but some fonts (HYMyeongJo, HYGothic, MYing Hei T, Song T) are not displayed. Further more, Caecilia condensed is not condensed at all and there are some other minor differences on how some other fonts are rendered;
- The 3rd snapshot is what I get after issuing a font cache rebuild with ";fc-cache". All fonts are displayed, but Caecilia condensed is still not condensed, those which weren't rendered at point 2 are quite different from those at point 1 and those with minor difference with point 1 are still different.
Hope this can be some way useful for developers.
At the moment I think I'll stay with the bundled 6.3.20 and try to rebuild Junicode to see if something changes.
Thank you hawhill!!!