Re: [Ltru] Corrections to 4646bis-11

John Cowan wrote:
> Scripsi:
> 
>>         They are intended to identify information which is commonly used
>>         in association with language tags but is not part of language
>>         identification.
> 
> "which is ... but which are ..." should be "which is ... which is ...";
> the implicit subject in either case is "information".

<editor hat="on">Done</editor>

> 
>> 3.1.1: change the definition of folding to "Folding is always done on
>> Unicode default grapheme boundaries".  That says what the current text
>> says, and also prohibits folding in the middle of a Hangul syllable
>> written as separate jamo.
> 
> I think we should reconsider this as Frank suggests, and fold only
> at whitespace, the same rule that RFC 2822 headers and the like use.
> As things stand, we cannot fold at whitespace except by placing the
> break after the space, making it a trailing space.
> 

<technicalContributor>

I dunno, John. The problem here is messy, since, if we fold on 
whitespace, we preclude comments in a native language that doesn't use 
whitespace or we at least forcibly break it in a weird way (unfolding 
the text results in a spurious space being created). Although currently 
all comments are in English, I can certainly imagine including a quote 
or descriptive text in-language.

Note that any trailing space is eaten by the unfolding rules. In 
record-jar's draft, I solved this by including a continuation character.

I'm not suggesting that we include the continuation character and I'm 
not quite against your/Frank's suggested change (since I suspect we are 
engaged in a bit of over-engineering, as there isn't evidence of our 
needing this feature just yet). I just want to be a bit careful here.

So... I guess in the course of the paragraph above I've talked myself 
into making the change.....

</technicalContributor>

-- 
Addison Phillips
Globalization Architect -- Yahoo! Inc.
Chair -- W3C Internationalization Core WG

Internationalization is an architecture.
It is not a feature.

_______________________________________________
Ltru mailing list
Ltru@ietf.org
https://www1.ietf.org/mailman/listinfo/ltru