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 keyboard(Continue reading)Keyboards 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
Keyboards 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.
> 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
RSS Feed