[oe] Bug 2430 -- TrueType fonts handling and solution for it

Shawn Rutledge shawn.t.rutledge at gmail.com
Tue Jan 22 01:16:24 UTC 2008


> Any ideas/objections?

Why does there need to be a font list on the filesystem?  Is it
prohibitive for a GUI to scan all the font files on startup?  I'm
guessing it is...

Well how about a FUSE filesystem which notices when a font file is
changed, and automatically updates the font list?  It's just a sort of
cache which contains the font name and some other metadata right?
Something like what you generate using mkfontdir on X?  Or maybe FUSE
is not even necessary... just put the timestamp into the list, for
each entry, then some init script can stat() each font file, and for
each file whose timestamp has changed or it does not have an entry at
all, update the list.

Eventually filesystems ought to have extended metadata.  Some do
already.  Then you could query the extended attributes of a font file
without having to open the font itself.

IMO installing a font, on any OS, ought to be no harder than copying
the file into the right place.




More information about the Openembedded-devel mailing list