On 07 Jun 2002 22:55:11 +0200, Olivier Chapuis wrote: > > The solution? > > at present time a font name is given as follow: > > shadow_stuff:xft_orand_core_font_description[[/A][/B]] > > where A is the _real_ charset of the font and B the name > of an iconv converter (from/to UTF-8 to/from the charset of the > font). In a normal situation these charsets hints are not > needed (good font name and standard iconvs). > > What we can do is to add an other hint in between ( and ) before > the "/" hints: (C)/A/B. C indicates that the charset/encoding of > the chars which should be displayed. Of course this have sense > only with an unicode font or if C is UTF-8. Moreover, in the case > of an xft font the default for C should be the locale charset as > with core fonts the default is the charset of the loaded font. > > Any comments before I start to implement this?
String encoding should better be a property of a string, not a font. But practically it is good (easier) to specify it together with font(s). Hovewer string encoding should by definition be the same with all fonts in the *Font font list, so it should be specified just like shadow=1:. The default may be different for different font types (if you think so), but if a user specified a string encoding, map it to any found font. I think encoding=utf-8: is a good syntax; encoding is applied to strings and ideally (i.e. hopefully) users will not confuse it with font charset. Regards, Mikhael. -- Visit the official FVWM web page at <URL:http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
