On Mon, Feb 1, 2010 at 3:31 PM, Albert Cahalan <acaha...@gmail.com> wrote: > On Sat, Jan 30, 2010 at 2:50 PM, C. Scott Ananian <csc...@cscott.net> wrote: > >> Really, the problems described here can all be solved by careful font >> selection and configuration. Fontconfig allows 'virtual fonts' which >> can combine the best parts of a number of font files. > > Please explain how this solves the problem of having > multiple fonts in the GUI that all look the same to a > single-language user. > > (for example, 100 fonts with foreign-sounding names > that all look **exactly** like DejaVu Sans)
You should configure fontconfig to only show *one* "Sans" font which includes the relevant parts of all these other script-specific fonts for the appropriate unicode ranges. Fonts which map script-specific differences which do not have a roman-script equivalent should either be given names which make this clear (made up example: "Sans (North Korea)", "Sans (South Korea)") and/or omitted from deployments targeted at roman-script language groups, with a fontconfig which directs the use of an appropriate alias font ("Sans", which has compromise glyphs for Korean, listed as an alias for both "Sans (North Korea)" and "Sans (South Korea)"). --scott -- ( http://cscott.net/ ) _______________________________________________ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel