From: Sytse W. <s.b...@st...> - 2002-09-29 16:25:11
|
On Sun, Sep 29, 2002 at 05:39:17PM +0600, Yuri wrote: > Hi all! > > I think we have to clear out what we have do with *.ttf fonts. IMHO it's > too expensive and kinda silly for every project to have it's own set of > true type fonts. > > I suggest that we should put all fonts to on dir somewhere in > enlightenment/e17/data/fonts (evas2 uses unicode ttf, right?) > > What do you think? It's indeed completely useless to put all these fonts in each and every package that uses them. I think just hardcoding a new data dir for those fonts would solve this problem, but still isn't really satisfying. This should be configurable in the evas2 configuration files. Besides, package maintainers should make a separate package containing the needed fonts (probably from the evas2 source) and let evas2 depend on this package. They could put it in /usr/X11R6/lib/X11/fonts/TrueType/e or something like that, so that you would still have the option of not including them in the X font path and not including the fonts installed in /usr/X11R6/lib/X11/fonts/TrueType in the evas font path, using each and every truetype font in X and evas2 programs would also be possible. Also, the system administrator should be able to put defaults for all users in /etc, which are used if some key is not found in the per-user configuration database in the user's home directory. I guess this is part of a much larger discussion about how e17 should be configured, which was at some point stopped while not really being finished. So wouldn't it be good to open it again? Sytse Wielinga |