Stephen J. Turnbull writes:
>>>>> "giacomo" == giacomo boffi
<giacomo.boffi(a)polimi.it> writes:
giacomo> #8 0x0825da46 in write_string_to_stdio_stream_1 (stream=0x4046bd40,
con=0x0,
giacomo> ptr=0xbfffbf00 "FcConfigSubstitute'ed name is Bitstream Vera
Sans,Verdana,Arial,Albany AMT,Luxi Sans,Nimbus Sans L,Helvetica,Nachlieli,Kochi Gothic,AR
PL KaitiM GB,AR PL KaitiM Big5,ï¼ï¼³ ã\202´ã\202·ã\203\203ã\202¯,Baekmuk Dotum,"...,
len=228, must_flush=1) at print.c:158
Aargh! Do you really have a font with a name encoded in UTF-8? I
was hoping not to have to deal with this for a while....
If you actually have such a font and got it from Debian, let me
know what it is so I can get it and try to reproduce the bug.
i got it from debian, sure [1], but i must confess that i installed a
bunch of fonts without really knowing... so this explains why at home
xemacs-xft is fine...
ok, i'll try removing a package a time and starting xemacs-xft
i'll post my finds asap,
ciao
gb
[1] there are quite a few fonts that i have found in a windows
installation, and copied to debian, but these _should_ be the same
both here and at home... so let's start with the (remove one font
package -- start xemacs -- repeat) plan