View Single Post
Old 04-14-2012, 02:37 PM   #201
NiLuJe
BLAM!
NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.
 
NiLuJe's Avatar
 
Posts: 5,259
Karma: 5220867
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW & PW2; Kobo H2O
I don't have the KT default fontconfig files on hand, so I may be talking out of my ass, but on the K3, I went with another approach for the browser (which also used fc):

The default local.conf used bidirectional aliases (map caecilia to serif, then serif to caecilia with an ordered prefer list), simply putting the custom font on top of those lists was enough. (Cf. local.conf).

The downside is I had to bindmount it on top of the default file. (Granted, I don't remember trying doing this in a *new* file, like we usually do in a fc setup, because I already had to bindmount the main config file anyway to put the fc cache in a single writable directory.)

On the other hand, I never really used the browser much, so I didn't test this extensively, so, err, just throwing it out there ;D.

Last edited by NiLuJe; 04-14-2012 at 02:44 PM.
NiLuJe is offline   Reply With Quote