On Fri, Jul 05, 2002 at 12:04:40PM +1000, Shao Zhang wrote:
> Hi,
>
> On [Thu, 4 Jul 2002 16:16:49 +0200], Olivier Chapuis <olivier.chapuis_at_free.fr> wrote:
> >> > 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).
>
> This is indeed my problem. I had --with-iconv-include instead of
> --with-iconv-includes, and that made a huge difference.
>
> GB fonts works fine now,
fine. We should be more clear about iconv detection.
> but not big5 fonts. Fvwm crashes when I try to
> specify any Big5 font. Anyone else getting this?
>
This is fixed now (in the current cvs).
But, again the good way to display CJK is either:
- Use the appropriate locale and load font without specifying
the charset or with a charset which matches "the" locale charset.
- Or use iso10646-1 font (core or ttf) with the good set of
char and use StringEncoding=good_encoding when you a load font.
For example with Big5 (with a non "Big5 locale"), all ascii
characters will be replaced by a space (of course when fvwm
does not crash).
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 Fri Jul 05 2002 - 02:00:33 BST