Re: [Ltru] 2.1: casing

Btw, I note that 3.1.3 discusses casing in registry records, and it expresses the exceptions directly in terms of script and region. I suppose that is fine for the registry but doesn’t work quite as well for tags in cases like sgn-BE-FR.

Also, btw, I note that the current registry doesn’t strictly follow the rule for the exception that you gave. In particular, it lists grandfathered tags “sgn-BE-fr”, “sgn-BE-nl” and “sgn-CH-de”.

Peter

From: ltru-bounces at ietf.org [mailto:ltru-bounces at ietf.org] On Behalf Of Peter Constable
Sent: Monday, July 07, 2008 11:31 AM
To: Phillips, Addison; Mark Davis
Cc: LTRU Working Group
Subject: Re: [Ltru] 2.1: casing

That works.

Peter

From: Phillips, Addison [mailto:addison at amazon.com]
Sent: Monday, July 07, 2008 11:18 AM
To: Mark Davis; Peter Constable
Cc: LTRU Working Group
Subject: RE: [Ltru] 2.1: casing

Done, with some minor modifications:

<t>Although case distinctions do not carry meaning in language tags, consistent formatting and presentation of the tags will aid users. The format of the tags and subtags in the registry is RECOMMENDED. In this format, all subtags are lowercase, with two exceptions: those two-letter tags and four-letter subtags that are neither initial nor occur after singletons. Such two-letter tags are all uppercase (as in the tag "en-CA-x-ca") and four-letter subtags are titlecase (as in the tag "az-Latn-x-latn").</t>

Addison Phillips

Globalization Architect -- Lab126

Internationalization is not a feature.

It is an architecture.

From: ltru-bounces at ietf.org [mailto:ltru-bounces at ietf.org] On Behalf Of Mark Davis
Sent: Monday, July 07, 2008 10:59 AM
To: Peter Constable
Cc: LTRU Working Group
Subject: Re: [Ltru] 2.1: casing

I had misread the text also. Looking at what Addison said and John did, I think we could make it clearer with:

In this format, all subtags, including all those following singletons (that is, in extension or private-use sequences) are in lowercase. The exceptions to this are: all other non-initial two-letter subtags are uppercase and all other non-initial four-letter subtags are titlecase.

=>

In this format, all subtags are in lowercase except for two possibilities: those two-letter tags and four-letter subtags that are neither initial nor occur after singletons. Such two-letter tags are all uppercase (eg, en-CA) and four-letter subtags are titlecase (eg, az-Latn).

Mark

On Mon, Jul 7, 2008 at 10:48 AM, Peter Constable <petercon at microsoft.com> wrote:

That helps clear up the last sentence. But I still see a problem with "In this format, all subtags… are in lowercase", which doesn't appear to be what is really intended.

Peter

From: mark.edward.davis at gmail.com [mailto:mark.edward.davis at gmail.com] On Behalf Of Mark Davis
Sent: Monday, July 07, 2008 10:35 AM
To: John Cowan
Cc: Peter Constable; LTRU Working Group
Subject: Re: [Ltru] 2.1: casing

+1 I think that'd be clearer wording.

Mark

On Mon, Jul 7, 2008 at 8:29 AM, John Cowan <cowan at ccil.org> wrote:

Peter Constable scripsit:

> This paragraph doesn't make complete sense to me:
>
> ---------------------
> Although case distinctions do not carry meaning in language tags,
> consistent formatting and presentation of the tags will aid users. The
> format of the tags and subtags in the registry is RECOMMENDED. In
> this format, all subtags, including all those following singletons
> (that is, in extension or private-use sequences) are in lowercase. The
> exceptions to this are: all other non-initial two-letter subtags are
> uppercase and all other non-initial four-letter subtags are titlecase.

I think striking the two instances of "other" deals with the problem:
all subtags are lowercase, except for non-initial two-letter tags, which
are uppercase, and non-initial four-letter tags, which are titlecase.

(Come to think of it, that's probably a clearer wording; I hereby
propose it.)

Note that the "non-initial two-letter subtags need not be region subtags:
we write sgn-BE-FR, for example.

--
That you can cover for the plentiful John Cowan
and often gaping errors, misconstruals, http://www.ccil.org/~cowan
and disinformation in your posts cowan at ccil.org
through sheer volume --that is another
misconception. --Mike to Peter

_______________________________________________
Ltru mailing list
Ltru at ietf.org
https://www.ietf.org/mailman/listinfo/ltru