View Single Post
Old 12-24-2012, 09:33 PM   #418
DuckieTigger
Wizard
DuckieTigger ought to be getting tired of karma fortunes by now.DuckieTigger ought to be getting tired of karma fortunes by now.DuckieTigger ought to be getting tired of karma fortunes by now.DuckieTigger ought to be getting tired of karma fortunes by now.DuckieTigger ought to be getting tired of karma fortunes by now.DuckieTigger ought to be getting tired of karma fortunes by now.DuckieTigger ought to be getting tired of karma fortunes by now.DuckieTigger ought to be getting tired of karma fortunes by now.DuckieTigger ought to be getting tired of karma fortunes by now.DuckieTigger ought to be getting tired of karma fortunes by now.DuckieTigger ought to be getting tired of karma fortunes by now.
 
DuckieTigger's Avatar
 
Posts: 4,742
Karma: 246906703
Join Date: Dec 2011
Location: USA
Device: Oasis 3, Oasis 2, PW3, PW1, KT
Quote:
Originally Posted by eureka View Post
;fc-cache updates Fontconfig cache, i.e. tells system to rescan fonts folders, including /mnt/us/fonts, and makes found fonts known to system. It does framework restart, but framework restart is required just for updating list of known fonts on Java side (reader program). Full restart is superfluous. USE_ALT_FONTS handling is completely implemented in some part of framework and no other system component is interested in it's existence. Refer to technical details in my original post.
No offence, but that was prior to 5.3.1 - why the trouble of it working not as easy in 5.3.1 as it did in 5.3.0? Did something change? Some code break that Amazon does not care about?
DuckieTigger is offline   Reply With Quote