LTRU Language Tag Registry Update working group (3066bis)

Mark Davis | 3 Dec 2005 03:39

Re: The special status of i-default in lookup

    more granular matching scheme

=>

    more fine-grained matching scheme

=====

    the set of language ranges in a language priority list

=>

    the list of language ranges in a language priority list
    [list, since it is ordered]

=====

    a case insensitive manner

=>

    a case-insensitive manner
    [missing hyphens in compound adjectives]

=====

    Implementations might also wish to use semantic information external

=>

(Continue reading)

headers

Martin Duerst | 5 Dec 2005 09:56

Various comments from Mark (was: Re: The special status of i-default in lookup)

Hello Mark, others,

I have taken the liberty to change the subject.

My personal comments, as a technical contributor,
below.

At 11:39 05/12/03, Mark Davis wrote:
 >    more granular matching scheme
 >
 >=>
 >
 >    more fine-grained matching scheme

I wanted to complain about not knowing which
way 'granular' goes several times. Thanks for
proposing a good solution.

 >=====
 >
 >    the set of language ranges in a language priority list
 >
 >=>
 >
 >    the list of language ranges in a language priority list
 >    [list, since it is ordered]

great fix

 >=====

(Continue reading)

headers

Mark Davis | 5 Dec 2005 12:54

Re: Various comments from Mark

Good comments. Responses below.

Martin Duerst wrote:

> Hello Mark, others,
>
> I have taken the liberty to change the subject.
>
> My personal comments, as a technical contributor,
> below.
>
> At 11:39 05/12/03, Mark Davis wrote:
> >    more granular matching scheme
> >
> >=>
> >
> >    more fine-grained matching scheme
>
> I wanted to complain about not knowing which
> way 'granular' goes several times. Thanks for
> proposing a good solution.
>
> >=====
> >
> >    the set of language ranges in a language priority list
> >
> >=>
> >
> >    the list of language ranges in a language priority list
> >    [list, since it is ordered]

(Continue reading)

headers

Addison Phillips | 2 Dec 2005 00:00

RE: The special status of i-default in lookup

I've done my best to edit in both (Martin's version of) John's suggestion below and (Martin's version of)
Harald's suggestion regarding implementation. I added Harald's text to Section 3.1 "Choosing Types of Matching".

The modified version is now hosted as "Editor's Copy" on inter-locale.com. See:

http://www.inter-locale.com/ID/draft-ietf-ltru-matching-08.txt 
http://www.inter-locale.com/ID/draft-ietf-ltru-matching-08.html

http://www.inter-locale.com/ID/draft-ietf-ltru-matching-08.xml


I made a few other edits as well, mostly cleanup of the English and bugfix. Any comments before I submit this?

The diff, by the way, can be viewed using this URI:

http://tinyurl.com/83cge


(or, if you prefer, the full URI follows)

http://tools.ietf.org/tools/rfcdiff/rfcdiff.pyht?url1=http://www.inter-locale.com/ID/draft-ietf-ltru-matching-07.txt&url2=http://www.inter-locale.com/ID/draft-ietf-ltru-matching-08.txt


Addison

Addison P. Phillips
Globalization Architect, Quest Software

Internationalization is not a feature.
It is an architecture. 

> -----Original Message-----
> From: ltru-bounces <at> ietf.org [mailto:ltru-bounces <at> ietf.org] On Behalf Of
> Martin Duerst

(Continue reading)