12 May 01:00
Re: Re: [psg.com #951] extensibility via codes not maintained by ISO
John Cowan <jcowan <at> reutershealth.com>
2005-05-11 23:00:38 GMT
2005-05-11 23:00:38 GMT
JFC (Jefsey) Morfin scripsit: > Frank documented what you can do with this mental twist. Scripts are named > in ISO 15924 ane are collections of characters documented in ISO 10646 with > their digital value. Many ISO 15924 scripts are not presently encoded, and ISO 15924 in no way depends on ISO 10646. > UTF-8 global script. UTF-8 is not a script. > Anyway, non of them gives me a correct French keyboardKeyboards are neither scripts nor encodings. > BTW , I always wander (and nobody answered) what is going to be the use for > your browser to know the name of the Script? Will it tell you "Hi! John, > you entered Mongolian script", or will it call a collection of digital > records to do someting with them? Or is it just for statistics? A browser could look for a Mongolian font, or could replace the document with a note that it is in a script you don't understand, or transliterate it into a script you do understand. But of course language tags are not confined to browsers: they can also be used, for example, to catalogue resources. -- -- Babies are born as a result of the John Cowan mating between men and women, and most http://www.reutershealth.com men and women enjoy mating. http://www.ccil.org/~cowan --Isaac Asimov in Earth: Our Crowded Spaceship jcowan <at> reutershealth.com
> I read rule (4) to mean that VU would not be added, which is
> one thing you have objected to.
Oops, I was counting bullets, and the 4th bullet discusses the
Recommended-Prefix. And the IM example is not the 9th bullet
but the 10th:
| Codes assigned by ISO 639, ISO 15924, or ISO 3166 that do not
| conflict with existing subtags of the associated type but
| which represent the same meaning as an existing subtag of
| that type are entered into the IANA registry as new records.
| The field 'canonical value' for that record MUST contain the
| existing subtag of the same meaning
For some obscure reasons I thought that that's the "no problem"
rule. But you see "new tag for an already registered entity"
as conflict / problem. Therefore you skip the 10th bullet and
arrive at number 11, the "conflict" rule. Maybe you should
define "conflict", I thought that it's only about collisions.
Yes, and 3.3.11.4 says "don't register if it's unnecessary".
> The phrase "no new entry is created" seems to forbid the
> creation of 'VU'. That could be changed to produce your
> following example, of course. It does also seem to conflict
> with the "rule 9" you cite
Now identified as 3.3.10.
["decanonicalization"]
> it conflicts with guarantees of stability for tags.
"Stable" means that NH is always what NH stood for, that's the
<doug do="not read this line"> same piece of land </doug>
no matter what its actual name (e.g.Vanuatu) or canonical tag
(either NH or VU) might be. Forever. Stable. But maybe you
have another idea of "stable" (?)
> thus certain processors might transform tags from "en-NH" to
> "en-VU" per this text in Section 2.2.9:
Yes, and that sounds like a good idea. Like jw -> jv etc.
> content authors having to choose a different tag than
> previously
If they love NH they are free to stick to it. If they insist
on canonical the are forced to adapt. Like everybody else in
Vanuatu. It's not that bad, I'm almost used to EUR instead of
DEM after some years.
[scenario 4, Use: VU]
> It is different than 'Canonical': it could be informative,
> for example, instead of normative (as canonical is)
This "normative vs. informative" is W3C magic, it's not worse
than IETF magic, but, hm... okay, I get what you mean. It's
a bit strange to say "Use: VU" but "Canonical: NH" for the same
piece of [***] Or "Use: yi" but "Canonical: ji" for the same
language.
If what you propose is to replace the "normative Canonical" by
an "informative Use" everywhere it's okay, as I said W3C magic.
[missing MUST NOT Suppress-Script and rationale]
> You will recall that I argued against Suppress-Script (even
> though I *also* thought of it and named it).
| when X = 'SUPPRESS-SCRIPT' then do
| if DEFS.N <> '' then exit TRAP( LINE REC )
| DEFS.N = '-' || YY ; XREF = XREF + 1
| end
Names. If I want a DEFS DEFault-Script" I just do it 
RSS Feed