[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Ltru] Re: Inversions and other problems



Addison Phillips wrote:
 
> IOW, the rules would be:
> 1. Follow the source standard.
> 2. Split multiple names into multiple description fields.
> 3. Omit or edit problematic items, subject to consensus.

Where (2) is "normally indicated by a semicolon" (?)

I like the "inverted form", it allows to spot all related
subtags in a list sorted by descriptions, e.g. all subtags
with one or more descriptions starting with "Arabic".

Or very visible in Mark's list, find out if "Quechua" is
the same as "Quichua" - but I didn't try that ;-)

Creating a derived list without inversions is apparently
simple, but the opposite direction isn't necessarily.

The @DOUBLE_COMMA stuff is apparently limited to a few 
enumerations, for "redundant" subtags we could improve it:

Instead of (example, one of six):
- German, Swiss variant, traditional orthography
+ German traditional orthography, Swiss variant

The nedis / rozaj cases could get a semicolon...

- Natisone dialect, Nadiza dialect
- Resian, Resianic, Rezija
+ Natisone dialect; Nadiza dialect
+ Resian; Resianic; Rezija

...resulting in multiple descriptions.  But IMO that's
unnecessary, also unnecessary for zh-min and zh-min-nan,
where the @DOUBLE_COMMA is an ordinary enumeration in
grandfathered tags.  

Frank



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




Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.