[Top][All Lists]

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

Re: address@hidden: setting utf-16 as file-name-coding-system locks up e

From: Kenichi Handa
Subject: Re: address@hidden: setting utf-16 as file-name-coding-system locks up emacs]
Date: Fri, 13 Aug 2004 10:46:35 +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>, Jason Rumney <address@hidden> writes:

> Part of this discussion has occured off list, so you may not have seen 
> my previous mail on this.

> Currently Emacs uses the standard C library functions for file I/O on 
> all platforms. In my judgement, changing this would be too much work to 
> take on during feature-freeze, especially since it is complicated by the 
> fact that the full Unicode API is not supported on all versions of Windows.

Of course, I agree that we shouldn't change the current
behaviour now.  I was talking about what to do in

> In future when this is implemented, I do not see the need for 
> "windows-file-name" coding-system. In the versions of Windows where the 
> Unicode API is fully supported, there is no need for 
> file-name-coding-system, since it is known to be 
> utf-16-le-with-signature. In the cases where those APIs are not 
> supported, then file-name-coding-system should be used with the standard 
> C library as now.

Ok, I see.

Ken'ichi HANDA

reply via email to

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