[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [mew-int 01596] Re: windows 1252
From: |
Kenichi Handa |
Subject: |
Re: [mew-int 01596] Re: windows 1252 |
Date: |
Fri, 14 Nov 2003 21:02:20 +0900 (JST) |
User-agent: |
SEMI/1.14.3 (Ushinoya) FLIM/1.14.2 (Yagi-Nishiguchi) APEL/10.2 Emacs/21.3 (sparc-sun-solaris2.6) MULE/5.0 (SAKAKI) |
In article <address@hidden>, "Stephen J. Turnbull" <address@hidden> writes:
> According to the standard, apps that implement compound text must
> implement extended segments, and if you implement utf-8 anyway, this
> would be trivial to support. But that doesn't mean they do.
The ctext spec says:
The name of the encoding should be registered with the X
Consortium to avoid conflicts and ...
But, the "registry" file included in X11R6.6 doesn't contain
UTF-8 nor "ISO-8859-15".
> Isn't UTF8_STRING also XFree86 only?
I don't think so. The above "registry" file have this note
at the tail.
[134] In R6.6 X.Org is reserving the string UTF8_STRING for use as an ICCCM
property type and selection target. The ICCCM spec will be updated
in a future release to fully specify UTF8_STRING.
---
Ken'ichi HANDA
address@hidden
- Re: [mew-int 01593] Re: windows 1252, (continued)
- Re: [mew-int 01585] Re: windows 1252, Kenichi Handa, 2003/11/07
- Re: [mew-int 01596] Re: windows 1252, 山本和彦, 2003/11/10
- Re: [mew-int 01596] Re: windows 1252, Kenichi Handa, 2003/11/10
- Re: [mew-int 01596] Re: windows 1252, Stephen J. Turnbull, 2003/11/12
- Re: [mew-int 01596] Re: windows 1252, Kenichi Handa, 2003/11/12
- Re: [mew-int 01596] Re: windows 1252, Stephen J. Turnbull, 2003/11/13
- Re: [mew-int 01596] Re: windows 1252, Kenichi Handa, 2003/11/13
- Re: [mew-int 01596] Re: windows 1252, Stephen J. Turnbull, 2003/11/14
- Re: [mew-int 01596] Re: windows 1252,
Kenichi Handa <=
- Re: [mew-int 01596] Re: windows 1252, Eli Zaretskii, 2003/11/13
- Re: [mew-int 01596] Re: windows 1252, Kenichi Handa, 2003/11/13