Re: utf-8 filenames in phar files.
| From: | Yasuo Ohgaki | Date: | Sat, 15 Feb 2014 10:53:37 +0000 |
| Subject: | Re: utf-8 filenames in phar files. | ||
| References: | 1 2 3 4 5 6 7 8 9 10 11 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-72626@lists.php.net to get a copy of this message | ||
On Sat, Feb 15, 2014 at 7:50 PM, Lester Caine <lester@lsces.co.uk> wrote:
> My previous post did not appear on the list ;)
>
>
> Yasuo Ohgaki wrote:
>
>> A lot of the current confusion does seem to be based around the
>> Windows
>> Wide-API as documented in 'The Problem' section of that document. It
>> would
>> seem that my 'naive' view of simply using UTF-8 strings is thwarted
>> by these
>> problems?--
>>
>> Unicode is like one name with several encoding. We cannot get away from
>> conversions, normalization especially.
>>
>
> That is why personally I'm just looking at UTF8. Which is enough of a mine
> field on it's own, but since a large swath of what we are working with now
> is only UTF8 it does seem to be the right base going forward?
>
I have problem, too. It seems someone is working on DKIM.
Anyway, there are problems, but UTF-8 is way to go. We just cannot remove
conversions. Normalization has number of issues, including security related
one.
Regards,
--
Yasuo Ohgaki
yohgaki@ohgaki.net