[mew-int 01623] Re: windows 1252

[Kenichi Handa]

In article <87vfpndwnl.fsf at example.com>, "Stephen J. Turnbull" <stephen at example.com> 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
handa at example.com