5:16 p.m.
Hello
Now the compilation with
./configure --with-mule --with-xim --with-xfs=emacs --with-xim
worked but I can't use True Type fonts.
- I see that there are 2 types of true fonts, the ones which
xfontsel finds like purisa
- and others I installed later in /usr/share/fonts
with
sudo cp /home/user/Desktop/*.ttf /usr/share/fonts/myfonts/
and refresh your font cache like this:
sudo fc-cache -f
The first ones are listed in options-->fonts (in both I must say 21.4.21
and 21.5.28) however in both cases Purisa is not highlighted and cannot
be selected this way,
Also
(set-face-font 'default "-*-purisa-*-*-*-*-*-*-*-*-*-*")
Does not work. So I am puzzled, I don't know who, mentioned that he uses
ttf fonts for a while, how?
Thanks and regards
Uwe Brauer
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
6:18 p.m.
Uwe Brauer writes:
(set-face-font 'default
"-*-purisa-*-*-*-*-*-*-*-*-*-*")
Does not work.
I already told you: (set-face-font 'default "Purisa"). Unlike GNU
Emacs, we use the native names for fonts, we don't force them into
XLFD form (which doesn't support all the features of fontconfig,
although it might -- barely -- be enough to emulate Windows/Mac font
specs).
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
7:02 a.m.
I've been using TrueType fonts in XEmacs for ages.
I build with
./configure '--with-gcc' '--with-cflags=-Wextra' \
'--with-cflags-debugging=-ggdb' '--with-xft=all'
'--with-wmcommand' \
'--with-mule=no' '--with-memory-usage-stats' \
'--with-error-checking=none'
I use
(custom-set-faces
'(muse-header-1 ((t (:size "13pt" :bold t))))
'(muse-header-2 ((t (:size "12pt" :bold t))))
'(muse-header-3 ((t (:size "11pt" :bold t))))
'(muse-header-4 ((t (:size "10pt" :bold t)))))
in ~/.xemacs/custom.el and
XEmacs*EmacsFrame.geometry: 123x63
XEmacs.bold-italic.attributeFont: DejaVu Sans Mono:style=Bold \
Oblique:size=10
XEmacs.bold.attributeFont: DejaVu Sans \ Mono:style=Bold:size=10
XEmacs.default.attributeBackground: white
XEmacs.default.attributeFont: DejaVu Sans \ Mono:style=Book:size=10
XEmacs.default.attributeForeground: black
XEmacs.italic.attributeFont: DejaVu Sans \
Mono:style=Oblique:size=10
XEmacs*xftFont: DejaVu Sans:style=Book:size=10
XEmacs.modeline.attributeFont: DejaVu Sans:style=Book:size=10
XEmacs.modeline.attributeBackground: white
in ~/.Xdefaults.
--- Vladimir
on 12/23/2008 09:16 AM Uwe Brauer said the following:
Hello
Now the compilation with
./configure --with-mule --with-xim --with-xfs=emacs --with-xim
worked but I can't use True Type fonts.
- I see that there are 2 types of true fonts, the ones which
xfontsel finds like purisa
- and others I installed later in /usr/share/fonts
with
sudo cp /home/user/Desktop/*.ttf /usr/share/fonts/myfonts/
and refresh your font cache like this:
sudo fc-cache -f
The first ones are listed in options-->fonts (in both I must say 21.4.21
and 21.5.28) however in both cases Purisa is not highlighted and cannot
be selected this way,
Also
(set-face-font 'default "-*-purisa-*-*-*-*-*-*-*-*-*-*")
Does not work. So I am puzzled, I don't know who, mentioned that he uses
ttf fonts for a while, how?
Thanks and regards
Uwe Brauer
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
--
Vladimir G. Ivanovic
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
4:55 p.m.
>>>> "Vladimir" == Vladimir G Ivanovic
<vgivanovic(a)comcast.net> writes:
I've been using TrueType fonts in XEmacs for ages.
I build with
./configure '--with-gcc' '--with-cflags=-Wextra'
\
'--with-cflags-debugging=-ggdb' '--with-xft=all'
'--with-wmcommand' \
'--with-mule=no' '--with-memory-usage-stats' \
'--with-error-checking=none'
I use
(custom-set-faces
'(muse-header-1 ((t (:size "13pt" :bold t))))
'(muse-header-2 ((t (:size "12pt" :bold t))))
'(muse-header-3 ((t (:size "11pt" :bold t))))
'(muse-header-4 ((t (:size "10pt" :bold t)))))
in ~/.xemacs/custom.el and
XEmacs*EmacsFrame.geometry: 123x63
XEmacs.bold-italic.attributeFont: DejaVu Sans Mono:style=Bold \
Oblique:size=10
XEmacs.bold.attributeFont: DejaVu Sans \ Mono:style=Bold:size=10
XEmacs.default.attributeBackground: white
XEmacs.default.attributeFont: DejaVu Sans \ Mono:style=Book:size=10
XEmacs.default.attributeForeground: black
XEmacs.italic.attributeFont: DejaVu Sans \
Mono:style=Oblique:size=10
XEmacs*xftFont: DejaVu Sans:style=Book:size=10
XEmacs.modeline.attributeFont: DejaVu Sans:style=Book:size=10
XEmacs.modeline.attributeBackground: white
in ~/.Xdefaults.
Thanks but this did not work out for me completely. For reasons I don't
understand only the geometry part of the .Xdefaults was used while the
fonts were replaced by *fixed*, however I could change to the DejaVu
fonst you use, by
Options-->font-->DejaVu
*however* when I select purisa, then again xemacs uses fixed instead of
purisa.
Purisa _is_ installed, even it is shown by xfontsel.
Can you please try to use Purisa and tell me the result?
BTW what shall I do with the ttf fonts, which are installed but not
displayed by xfontsel????
Thanks
Uwe Brauer
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
1:09 a.m.
on 12/27/2008 08:55 AM Uwe Brauer said the following:
Options-->font-->DejaVu
*however* when I select purisa, then again xemacs uses fixed instead of
purisa.
Purisa _is_ installed, even it is shown by xfontsel.
Can you please try to use Purisa and tell me the result?
I used "Purisa:style=Medium:size=10" in my .Xdefaults file, merged it
using 'xrdb' and then ran "xemacs -vanilla". Attached is a Print
Screen dump.
BTW:
1. Options->Font shows Purisa as selected.
2. xfontsel does not list Purisa (or purisa)
3. fc-list shows "Purisa:style=Medium"
4. I did get some warnings from XEmacs about being unable to deduce
bold or italic versions of Purisa. These are expected since bold and
italic versions are not available (and might not even make sense in Thai).
5. I used the Fedora Project RPM "thaifonts-scalable" to obtain Purisa:
$ rpm -qi thaifonts-scalable
Name: thaifonts-scalable Relocations: (not relocatable)
Version: 0.4.9 Vendor: Fedora Project
Release: 3.fc9 Build Date: Thu 07 Feb
2008 10:36:30 PM PST
Install Date: Sat 27 Dec 2008 03:40:13 PM PST Build Host:
xenbuilder4.fedora.phx.redhat.com
Group: User Interface/X Source RPM:
thaifonts-scalable-0.4.9-3.fc9.src.rpm
Size: 3008781 License: GPLv2+
Signature: DSA/SHA1, Tue 28 Oct 2008 10:06:53 PM PDT, Key ID
bf226fcc4ebfc273
Packager: Fedora Project
URL: http://linux.thai.net/projects/thaifonts-scalable
Summary: A collection of scalable Thai fonts
Description:
This package collects scalable Thai fonts available in free licenses.
Thai scalable fonts included here are:
- Kinnari, Garuda and Norasi from the National Font project
- DB Thai Text from DearBook
- TlwgMono, PseudoMono, Purisa by TLWG
I'm going to remove this package in 24 hours, so if you have any more
requests, fire away!
--- Vladimir
--
Vladimir G. Ivanovic
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
12:52 p.m.
Uwe Brauer writes:
Purisa _is_ installed, even it is shown by xfontsel.
xfontsel is irrelevant to Xft. Check what fc-list knows about.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
4:45 p.m.
New subject: translated menus with Xft/fontconfig?
I am using the Xft support in XEmacs for a long time already
and like a lot.
But until now I always disabled it for the menus because
I couldn’t figure out how to make it work for the translated menus.
Now I tried again but I still cannot figure out how to make it work.
The sumo package comes with translated menus for 4 languages:
mfabian＠magellan:~$ rpm -ql xemacs-packages | grep app-defaults
/usr/share/xemacs/mule-packages/etc/app-defaults
/usr/share/xemacs/mule-packages/etc/app-defaults/de
/usr/share/xemacs/mule-packages/etc/app-defaults/de/Emacs
/usr/share/xemacs/mule-packages/etc/app-defaults/de_DE
/usr/share/xemacs/mule-packages/etc/app-defaults/de_DE.UTF-8
/usr/share/xemacs/mule-packages/etc/app-defaults/de_DE.UTF-8/Emacs
/usr/share/xemacs/mule-packages/etc/app-defaults/de_DE＠euro
/usr/share/xemacs/mule-packages/etc/app-defaults/fr
/usr/share/xemacs/mule-packages/etc/app-defaults/fr/Emacs
/usr/share/xemacs/mule-packages/etc/app-defaults/fr_FR
/usr/share/xemacs/mule-packages/etc/app-defaults/fr_FR.UTF-8
/usr/share/xemacs/mule-packages/etc/app-defaults/fr_FR.UTF-8/Emacs
/usr/share/xemacs/mule-packages/etc/app-defaults/fr_FR＠euro
/usr/share/xemacs/mule-packages/etc/app-defaults/ja
/usr/share/xemacs/mule-packages/etc/app-defaults/ja/Emacs
/usr/share/xemacs/mule-packages/etc/app-defaults/ja_JP
/usr/share/xemacs/mule-packages/etc/app-defaults/ja_JP.EUC
/usr/share/xemacs/mule-packages/etc/app-defaults/ja_JP.UTF-8
/usr/share/xemacs/mule-packages/etc/app-defaults/ja_JP.UTF-8/Emacs
/usr/share/xemacs/mule-packages/etc/app-defaults/ja_JP.eucJP
/usr/share/xemacs/mule-packages/etc/app-defaults/ja_JP.ujis
/usr/share/xemacs/mule-packages/etc/app-defaults/ro
/usr/share/xemacs/mule-packages/etc/app-defaults/ro/Emacs
/usr/share/xemacs/mule-packages/etc/app-defaults/ro_RO
/usr/share/xemacs/mule-packages/etc/app-defaults/ro_RO.UTF-8
/usr/share/xemacs/mule-packages/etc/app-defaults/ro_RO.UTF-8/Emacs
mfabian＠magellan:~$
(The files in the .UTF-8 subdirectories are versions converted
to UTF-8 while building the xemacs.rpm package).
Starting XEmacs in single byte locales works fine, i.e.
LANG=de_DE＠euro xemacs
loads the German menus and they look OK, including the
non-ASCII characters (umlauts).
But in multibyte locales it does not work, i.e.
LANG=de_DE.UTF-8 xemacs
does load the German menus but all non-ASCII characters are not
displayed correctly. It doesn’t seem to be a font problem but rather an
encoding problem because in de_DE.UTF-8 locale, an ü is displayed as ü,
i.e. it looks like the multibyte characters don’t work at all.
Is a special setup necessary to make this work or doesn‘t it
work at all at the moment?
--
Mike FABIAN <mfabian(a)suse.de> http://www.suse.de/~mfabian
睡眠不足はいい仕事の敵だ。
I � Unicode
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
7:20 a.m.
New subject: translated menus with Xft/fontconfig?
Mike FABIAN writes:
I am using the Xft support in XEmacs for a long time already
and like a lot.
But until now I always disabled it for the menus because
I couldn’t figure out how to make it work for the translated menus.
It doesn't work, AFAIK. That's one of the reasons I opposed putting
Xft into the mainline way back when.
Working around it might be as easy as replacing calls to
XftDrawString8 with XftDrawStringUtf8 in lwlib/xlwmenu.c.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
1:43 p.m.
New subject: translated menus with Xft/fontconfig?
Stephen J. Turnbull wrote:
> I am using the Xft support in XEmacs for a long time already
> and like a lot.
>
> But until now I always disabled it for the menus because
> I couldn’t figure out how to make it work for the translated menus.
It doesn't work, AFAIK. That's one of the reasons I opposed putting
Xft into the mainline way back when.
Working around it might be as easy as replacing calls to
XftDrawString8 with XftDrawStringUtf8 in lwlib/xlwmenu.c.
XftDrawString8() assumes that the text is ISO-8859-1 (specifically, it
treats each byte as a unicode codepoint). If you have text in some
other encoding, you need to convert it to unicode yourself.
Obviously, using XftDrawStringUtf8 will fail if the text isn't in
UTF-8. While nothing prevents you from specifying menu labels in UTF-8
regardless of the locale's encoding, editing the app-defaults file is
likely to be a pain if it contains text in multiple encodings.
Using mbstowcs() and XftDrawString32 wouldn't be much more complex,
and should handle most cases, i.e. so long as wchar_t is UCS-4 and
setlocale(LC_CTYPE,"") is in effect.
--
Glynn Clements <glynn(a)gclements.plus.com>
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
1:56 p.m.
New subject: translated menus with Xft/fontconfig?
"Stephen J. Turnbull" <stephen(a)xemacs.org> さんは書きました:
Mike FABIAN writes:
> I am using the Xft support in XEmacs for a long time already
> and like a lot.
>
> But until now I always disabled it for the menus because
> I couldn’t figure out how to make it work for the translated menus.
It doesn't work, AFAIK. That's one of the reasons I opposed putting
Xft into the mainline way back when.
Working around it might be as easy as replacing calls to
XftDrawString8 with XftDrawStringUtf8 in lwlib/xlwmenu.c.
Yes, this works indeed. I have a patch attached which does this.
But of course this works only, if the translated app-defaults
files are UTF-8 encoded.
Until now I have packaged:
/usr/share/xemacs/mule-packages/etc/app-defaults/de/Emacs (iso-8859-1 encoded)
/usr/share/xemacs/mule-packages/etc/app-defaults/de_DE (symlink to de directory)
/usr/share/xemacs/mule-packages/etc/app-defaults/de_DE.UTF-8/Emacs (utf-8 encoded)
After applying the attached patch, having only
/usr/share/xemacs/mule-packages/etc/app-defaults/de/Emacs (utf-8 encoded)
works enough for de_DE, de_DE＠euro, and de_DE.UTF-8 locales with Xft.
*But* in the non-Xft case, functions like XmbDrawString() are used which
expect the encoding of the current locale, i.e. they need files with
different encodings in different subdirectories like de/Emacs and
de_DE.UTF-8/Emacs.
The easiest (and in my opinion nicest as well) way to fix this would be
to use Xutf8DrawString() and friends for the non-Xft case and make the
app-defaults files always UTF-8 encoded. But according to the manual
page of Xutf8DrawString:
The function Xutf8DrawString is an extension introduced by The XFree86
Project, Inc. in their 4.0.2 release. Its presence is indicated by the
macro X_HAVE_UTF8_STRING.
and I don’t know if there are still systems around which do not have
Xutf8DrawString.
--
Mike FABIAN <mfabian(a)suse.de> http://www.suse.de/~mfabian
睡眠不足はいい仕事の敵だ。
I � Unicode
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
2:55 p.m.
New subject: translated menus with Xft/fontconfig?
Glynn Clements <glynn(a)gclements.plus.com> さんは書きました:
Stephen J. Turnbull wrote:
> > I am using the Xft support in XEmacs for a long time already
> > and like a lot.
> >
> > But until now I always disabled it for the menus because
> > I couldn’t figure out how to make it work for the translated menus.
>
> It doesn't work, AFAIK. That's one of the reasons I opposed putting
> Xft into the mainline way back when.
>
> Working around it might be as easy as replacing calls to
> XftDrawString8 with XftDrawStringUtf8 in lwlib/xlwmenu.c.
XftDrawString8() assumes that the text is ISO-8859-1 (specifically, it
treats each byte as a unicode codepoint). If you have text in some
other encoding, you need to convert it to unicode yourself.
Obviously, using XftDrawStringUtf8 will fail if the text isn't in
UTF-8. While nothing prevents you from specifying menu labels in UTF-8
regardless of the locale's encoding, editing the app-defaults file is
likely to be a pain if it contains text in multiple encodings.
I think making the app-defaults files *always* UTF-8 *only* is
the best solution here.
Using mbstowcs() and XftDrawString32 wouldn't be much more
complex,
and should handle most cases, i.e. so long as wchar_t is UCS-4 and
setlocale(LC_CTYPE,"") is in effect.
Then you need differently encoded app-defaults files for e.g.
de_DE and de_DE.UTF-8 locale. This is an unnecessary complexity
in my opinion. One file in UTF-8 encoding seems cleaner to me.
--
Mike FABIAN <mfabian(a)suse.de> http://www.suse.de/~mfabian
睡眠不足はいい仕事の敵だ。
I � Unicode
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
4:52 p.m.
New subject: translated menus with Xft/fontconfig?
Glynn Clements writes:
XftDrawString8() assumes that the text is ISO-8859-1 (specifically,
it
treats each byte as a unicode codepoint). If you have text in some
other encoding, you need to convert it to unicode yourself.
To be precise, XftFooN() for N=8, N=16, or N=32 treats text as encoded
in Unicode, with each N bits treated as an (unsigned) nonnegative
integer character code. While XftFooUtfN() for N=8 or N=16 is a
variable-width encoding.
Obviously, using XftDrawStringUtf8 will fail if the text isn't
in
UTF-8. While nothing prevents you from specifying menu labels in UTF-8
regardless of the locale's encoding, editing the app-defaults file is
likely to be a pain if it contains text in multiple encodings.
There's no locale to worry about; this is a multilingualized, not an
internationalized, feature. Another way to look at it is that this is
internal XEmacs data, and is in whatever encoding is convenient for
loading as a resource, just as a C file would be. IMO, that's X
Compound Text for the legacy XFontSet approach to multilingualization,
and UTF-8 for Xft.
The only real problem with switching to UTF-8 globally (in both data
files and Lisp files) is 21.4's lack of support for Unicode. Perhaps
Julian will fix that for us.
The other problem with multilingual widgets (the tabs visibly have the
same problem, and progress gauges would too if they were M17N at all)
is font selection. This really ought to be done via a face, but
native widgets currently don't play well with faces, while the kludgy
XEmacs widgets like the toolbar (which is actually a gadget drawn
directly by the Emacs text widget, as are the gutters themselves) do a
better job of honoring face specifications, but they're kludgy.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
7:40 p.m.
New subject: translated menus with Xft/fontconfig?
Ar an chéad lá is fiche de mí Eanair, scríobh Mike FABIAN:
"Stephen J. Turnbull" <stephen(a)xemacs.org> さんは書きました:
> Mike FABIAN writes:
> > I am using the Xft support in XEmacs for a long time already
> > and like a lot.
> >
> > But until now I always disabled it for the menus because
> > I couldn’t figure out how to make it work for the translated menus.
>
> It doesn't work, AFAIK. That's one of the reasons I opposed putting
> Xft into the mainline way back when.
>
> Working around it might be as easy as replacing calls to
> XftDrawString8 with XftDrawStringUtf8 in lwlib/xlwmenu.c.
Yes, this works indeed. I have a patch attached which does this.
But of course this works only, if the translated app-defaults
files are UTF-8 encoded.
We have the information about what encoding the X11 server thinks the app
defaults are in already; see device-x.c:coding_system_of_xrm_database. It
seems to me that if we told the lwlib code about this, passed it
internal-format strings (instead of transforming to Qlwlib_encoding before
passing to lwlib), we could leave it to do its own, correct translation; to
UTF-8 if using Xft, to the encoding of the Xrm database, falling back to
Qnative, if not. No test implementation from me today, sorry.
IIRC the XFree86 or X.org people deprecated Xutf8DrawString within a couple
of years of introducing it.
--
¿Dónde estará ahora mi sobrino Yoghurtu Nghe, que tuvo que huir
precipitadamente de la aldea por culpa de la escasez de rinocerontes?
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
9:53 p.m.
New subject: translated menus with Xft/fontconfig?
Stephen J. Turnbull wrote:
> Obviously, using XftDrawStringUtf8 will fail if the text
isn't in
> UTF-8. While nothing prevents you from specifying menu labels in UTF-8
> regardless of the locale's encoding, editing the app-defaults file is
> likely to be a pain if it contains text in multiple encodings.
There's no locale to worry about; this is a multilingualized, not an
internationalized, feature. Another way to look at it is that this is
internal XEmacs data, and is in whatever encoding is convenient for
loading as a resource, just as a C file would be. IMO, that's X
Compound Text for the legacy XFontSet approach to multilingualization,
and UTF-8 for Xft.
Mike FABIAN wrote:
The easiest (and in my opinion nicest as well) way to fix this would
be
to use Xutf8DrawString() and friends for the non-Xft case and make the
app-defaults files always UTF-8 encoded.
w.r.t. both comments: so menu labels aren't intended to be
customisable via ~/.Xdefaults or ~/app-defaults/Emacs?
If they are, then requiring the labels to be in UTF-8 means that that
~/.Xdefaults (etc) must be in UTF-8, so either the user has to deal
with multiple encodings in that file, or any other applications
customised via that file must use UTF-8, which essentially means that
the user must use a UTF-8 locale.
--
Glynn Clements <glynn(a)gclements.plus.com>
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
2:10 a.m.
New subject: translated menus with Xft/fontconfig?
Glynn Clements writes:
w.r.t. both comments: so menu labels aren't intended to be
customisable via ~/.Xdefaults or ~/app-defaults/Emacs?
No, and "hell, no" (the name of the app-defaults file is XEmacs ;-),
respectively. The default menu labels are initialized by X resources
(a lazy kludge IMHO), but this should be considered an implementation
detail, similar to initializing Lisp variables in C. User
customizations of menus should be done in Lisp.
I don't have an objection to making it easier to use X resources to
customize XEmacs, but this is clearly secondary to improving Lisp
support of menu customization for several reasons. Use of
.Xresources, .Xdefaults, or app-defaults files is a dying art, killed
by GNOME and KDE, not to mention the dominance of Windows where they
are a completely foreign concept. X's handling of of non-UTF-8
locales is less than stellar, and won't improve. Use of anything
other than UTF-8 (and maybe UTF-16 on Windows) in configuration files
is also going the way of the dinosaurs.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
5571
days inactive
5601
days old
14 comments
6 participants
participants (6)
-
Aidan Kehoe -
Glynn Clements -
Mike FABIAN -
Stephen J. Turnbull -
Uwe Brauer -
Vladimir G. Ivanovic