[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Automatically Saved Files Employ Different Coding

From: Kenichi Handa
Subject: Re: Automatically Saved Files Employ Different Coding
Date: Tue, 30 Mar 2004 12:51:24 +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>, Alexander Winston <address@hidden> writes:
> I'm unsure as to why Emacs has problems converting Arabic to UTF-8 from
> the original encoding,

The arabic support of Emacs is very poor... almost nothing.
In the HELLO file, Arabic characters are in private charsets
inherited from Mule.  In Mule we had fairly ad-hoc bidi
support using those charsets, but it is not yet implemented
in Emacs.  Perhaps, those Arabic characters should be
changed to mule-unicode-0100-24ff or mule-unicode-e000-ffff.

> as I normally do not encounter any problems using
> Arabic. See screenshots
> <http://home.comcast.net/~alexander.winston/w3m.png> and
> <http://home.comcast.net/~alexander.winston/ar.png>, for example. The
> former was taken while using w3m and the latter while using Emacs; both
> were taken while viewing <http://www.arabia.com/>, a site that seems to
> use valid UTF-8.

You do have a problem using Arabic because the rendering is
incorrect.  In you images, it seems that all Arabic letters
are rendered by isolated form, not with correct
initial/medial/final form.

Ken'ichi HANDA

reply via email to

[Prev in Thread] Current Thread [Next in Thread]