Re: [I18ndir] I-D on filesystem I18N

["Asmus Freytag (c)" <[e-mail]>]

On 7/7/2020 8:13 PM, Nico Williams wrote:
> On Tue, Jul 07, 2020 at 07:27:15PM -0700, Asmus Freytag (c) wrote:
>> On 7/7/2020 6:40 PM, Nico Williams wrote:
>> [...]
>>
>> It would be good to lay the foundation by reminding everyone of these
>> subtleties.
> That's fair.  Of course, for a -00, I had only so much time before the
> submission deadline for IETF 108 (for which I think there may still be
> time to organize a "lunch-time" meeting of this directorate).
I'll move on to the rest of your document.
Nobody's blaming you - I've been often enough on the other side and 
despite all defensiveness, always end up benefiting from knowing how my 
readers actually parse my text.
>
>>>> writing colleagues would disagree that U+0131 "could" or should
>>>> be considered equivalent to U+0069.  In my experience, that
>>> The idea was to describe how an admin might square that circle in a
>>> case-insensitive filesystem, and then I did not endorse it.  The idea
>>> was to describe how custom case-folding tailorings (FYI, that's the term
>>> Unicode uses, 'tailoring') might come about.
>>>
>>> There will be time to address all the nits.  The big idea is more
>>> interesting.
>> The danger of reviewing the test while reading along from the start.
>> However, the only way I know how to review anything that's not in a
>> change-tracked editable format.
> Fair.  FYI, I did put it in a GitHub repository.  Sending PRs is not as
> convenient as suggesting or making edits in a collaborative editor like
> google docs though :(
Indeed.

I'm not a natural with GitHub. So, I'll stick to this method.

A./