On Thu, Jul 04, 2002 at 04:57:51PM +1000, Shao Zhang wrote:
> Hi,
>
> On [Thu, 4 Jul 2002 07:19:20 +0200], Olivier Chapuis <olivier.chapuis_at_free.fr> wrote:
> > On Thu, Jul 04, 2002 at 10:37:17AM +1000, Shao Zhang wrote:
> >> On [Wed, 3 Jul 2002 11:14:43 +0000], Mikhael Goikhman <migo_at_homemail.com> wrote:
> >> > On 03 Jul 2002 15:47:14 +1000, Shao Zhang wrote:
> >> > It should be "StringEncoding=gb2312.1980-0". A dot, not a dash.
> >> > It is critical to specify it correctly.
> >>
> >> Sorry, it was a typo. I had it right in the config file.
> >>
> >
> > So, we need more info. Can you send the output of "echo $LC_CTYPE"
> > and of "locale".
>
> I don't have LC_CTYPE, LC_ALL and LANG defined at all. I did not see any
> reference of them in the fvwm manpage. Strangely, FreeBSD does not have
> zh_CN.GB2312 locale installed. But I did try with a Big5 font with the
> following:
>
> export LC_CTYPE=zh_TW.Big5 LC_ALL=zh_TW.Big5 LANG=zh_TW.Big5
>
In this case, you should use a Big5 font, e.g.:
Style "foo" Font -*-fixed-medium-r-normal--16-*
should load a big5-0 font if you have any which match the previous
pattern.
Note that, as it is say in the fvwm man page, fvwm will display CJK
in the good way only if you use the appropriate locale (or you can
use appropriate (xft) iso10646-1 font + StringEncoding). If not and
you enforce a multibyte font by specifying its charset the rendering
can only be approximative (but not as bad as you get). In fact,
for GB2312 things should work not so bad at all, but unfortunately
not for you and I do not see the reason ...
Maybe you can try to use an iso10646-1 font:
Style "foo" "StringEncoding=GB2312.1980-0:an_iso10646-1_font_with_simplified_chinese_char
e.g., -gnu-unifont-medium-r-normal--16-160-75-75-c-80-iso10646-1 may have
simplified chinese glyph.
You may also try some ttf fonts (you should find/install a ttf font with
chinese glyph and add the path to XftConfig; I may help).
Anyway I would like to find the problems ...
> with still the same result.
>
> > Seems you run FreeBSD, this is maybe the reason of
> > the problem. I think that BSD libc do not has iconv. Do you have
> > (gnu) libiconv installed on your machine? (if not install it and
> > recompile fvwm, maybe configure should require an iconv). What
> > is the version of XFree?
>
> I thought libiconv is always required in 2.5.2.
>
I think that fvwm-2.5.2 compiles and works without any iconv
(I never test this).
Regards, Olivier
--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Thu Jul 04 2002 - 09:28:32 BST