From: "U.Nakamura" <usa@...>
Date: 2010-05-06T22:26:59+09:00
Subject: [ruby-core:30057] Re: [Bug #1685] Some windows unicode path issues remain

Hello,

In message "[ruby-core:30054] Re: [Bug #1685] Some windows unicode path issues remain"
    on May.06,2010 21:38:19, <billk@cts.com> wrote:
> > For compatibility.
> > 
> > I will not change filesystem encoding in Windows in 1.9 series.
> > In all methods which returns filenames, the default encoding
> > of returned value must be filesystem encoding.
> > So, if someone want to get filename with another encoding, he/she
> > should specify the encoding by some way.
> > Of course, it is necessary to decide the "some way" of each
> > methods.
> 
> Ah.
> 
> So my rb_w32_ugetcwd patch is not very useful, at present,
> since there is no "some way" to specify the encoding via
> Dir.pwd.

Unfortunately...


> Well then, this becomes a philosophical question at this point,
> but in an effort to better understand, I am wondering:
> 
> How does it break compatibility, if we allow filesystem encoding
> to become UTF-8 when rb_default_external_encoding is UTF-8?

You should advocate using default_internal instead of
default_external :)
It's acceptable for me.


> I admit I don't understand why it's considered a globbing problem.

FileUtils uses Dir.entries to get filenames to remove.


> Does the UTF-8 support somehow make the globbing more difficult?
> I thought it was just the same situation as above: a filesystem
> encoding problem?

Yes, you are right.


Regards,
-- 
U.Nakamura <usa@garbagecollect.jp>