Hi, strictly speaking, UTF8 would violate the X Logical Font Description definition, which states that the whole XLFD has to be in ISO8859-1 graphic characters excluding '-', '?', '*', ',' and '"'. And how would you distinguish when to use UTF8 conversion and when ISO8859-1 ? You could try if a UTF8 string is valid, but i'm not sure if this would catch all cases.
Just my 2 cents Philipp >>>>>>>>>>>>>>>>>> Urspr�ngliche Nachricht <<<<<<<<<<<<<<<<<< Am 13.11.01, 00:29:23, schrieb Edward "G.J." Lee <[EMAIL PROTECTED]> zum Thema Re: [Render] RE: xft font substitution: > On Mon, Nov 12, 2001, [EMAIL PROTECTED] wrote: > "-aliasarphic-�s�ө���-medium-r-normal--0-0-0-0-c-0-big5-0" \ > "-Arphic-AR PL Mingti2L Big5-medium-r-normal--0-0-0-0-c-0-big5-0" > "-aliasarphic-�з���-medium-r-normal--0-0-0-0-c-0-big5-0" \ > "-Arphic-AR PL KaitiM Big5-medium-r-normal--0-0-0-0-c-0-big5-0" > so that when the homepage need "�s�ө���" the browser will use > "AR PL Mingti2L Big5", and "�з���" will use "AR PL KaitiM Big5" > automatically? > As your explain, Xft can recognize UTF-8 font family names. Is it > possible that XLFD can use UTF-8 font family names too? I try > UTF-8 and big5 but in vain. The property of FAMILY_NAME is type > ATOM, seems can use ISO-8859-1 encoding only? > (I'm sorry, if I misunderstand something, I'm still new to X) _______________________________________________ Render mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/render
