[#4595] New block syntax — Daniel Amelang <daniel.amelang@...>

I'm really sorry if this isn't the place to talk about this. I've

25 messages 2005/03/21
[#4606] Re: New block syntax — "David A. Black" <dblack@...> 2005/03/21

Hi --

[#4629] Re: New block syntax — "Sean E. Russell" <ser@...> 2005/03/30

On Monday 21 March 2005 16:17, David A. Black wrote:

[#4648] about REXML::Encoding — speakillof <speakillof@...>

Hi.

15 messages 2005/03/31
[#4659] Re: about REXML::Encoding — "Sean E. Russell" <ser@...> 2005/04/04

On Thursday 31 March 2005 09:44, speakillof wrote:

Re: Win32 Non-ASCII Filename Access

From: Austin Ziegler <halostatue@...>
Date: 2005-03-09 16:21:57 UTC
List: ruby-core #4536
On Thu, 10 Mar 2005 01:18:53 +0900, Vincent Isambart
<vincent.isambart@gmail.com> wrote:
> Hi,
>> I don't think it's as big an issue on Unix-based operating
>> systems except perhaps MacOS, because most other Unix OSes can't
>> handle wide character filenames and will therefore encode most
>> international filenames as UTF-8, if the environment setting is
>> correct.
> MacOS X uses filenames encoded in UTF-8, AFAIK. (GUI: UTF-16,
> filesystem: UTF-8). The only difference may be in the
> normalization form used (I think I saw something about it in
> glib).

According to what I've read, that is dependent upon the filesystem
used, and OS X may transparently expose filenames as UTF-8 for older
programs. Can anyone confirm this?

HFS+ actually stores filenames as UCS-2 (just like NTFS and FAT32),
but in a slightly different form than Win32. MacOS X uses decomposed
characters (e.g., e + combining accent acute == 薊 whereas Win32
simply uses precomposed characters (e.g., 薊.

-austin
-- 
Austin Ziegler * halostatue@gmail.com
               * Alternate: austin@halostatue.ca


In This Thread

Prev Next