[ruby-core:17322] Re: [Ruby 1.9 - Bug #178] (Closed) File.open on sprintf-formatted string fails with encoding conversion error on OS X

At 15:36 08/06/18, Yui NARUSE wrote:
>Issue #178 has been updated by Yui NARUSE.
>
>Status changed from Open to Closed
>Assigned to set to Yui NARUSE
>% Done changed from 0 to 100
>
>This problem is from the same bug of Bug #179,
>and it was fixed at r17403.
>Thanks,

Great, thanks!

>> It may be that it is an attempt to refer to the fact that UTF-8
>> usually is used in decomposed form (NFD) on the Mac. But that
>> would not be relevant for opening a file, because the Mac OS
>> accepts any kind of normalization, and converts to NFD by itself
>> (similar to a file system that accepts both upper- and lower-case,
>> but internally uses only one case).
>
>Yeah, that's true when you write to filesystem,
>but when you read from filesystem you may want to know
>whether they are composed or decomposed.

That may indeed be the case. But this really only applies to
filenames (and maybe similar names of resources) on the Mac.
For such a small subset of data, I think it's overkill if
as a consequence, processing together with other data is
blocked (as we saw in the bug report).
As far as I understand, it doesn't apply to file contents or
other data on the Mac. Also, as soon as you concatenate two
strings, there is no guarantee that NFD is kept (unless of
course you implement separate string concatenation for this
specific encoding). In general, the best thing to do if you
want to know is to check, and the best thing if you want to
be sure is to check, and then to change if necessary. But we
still have to implement this (maybe for -3?).

[Also, if the meaning of UTF8-MAC is really NFD, it might
be better to actually call it that way.]

Regards,    Martin.



#-#-#  Martin J. Du"rst, Assoc. Professor, Aoyama Gakuin University
#-#-#  http://www.sw.it.aoyama.ac.jp       mailto:[e-mail]