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

[Kenichi Handa]

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
emacs-unicode.

> 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
address@hidden