1 Nov 01:00
Re: Re: IPA as a script
John Cowan <cowan <at> ccil.org>
2006-11-01 00:00:04 GMT
2006-11-01 00:00:04 GMT
Doug Ewell scripsit: > 1a. Roughly how many phonetic transcription systems are there that need > encoding? About a dozen, if you mean transcriptions into systems that can potentially handle any speech sound. > 1b. Roughly how many scripts have phonetic transcription systems based > on them that need encoding? About one in common use; who knows how many individual oddities. > 2. Do we want to petition ISO 15924/RA to add that number of "script" > subtags, for things that are at least arguably not scripts? I wouldn't want to petition for more than one. -- -- John Cowan cowan <at> ccil.org http://ccil.org/~cowan Original line from The Warrior's Apprentice by Lois McMaster Bujold: "Only on Barrayar would pulling a loaded needler start a stampede toward one." English-to-Russian-to-English mangling thereof: "Only on Barrayar you risk to lose support instead of finding it when you threat with the charged weapon."
[LTRU "resolution" or similar]
> That is certainly something I'd consider. This WG owns the 4646 LT
> space, so if it seems like the sensible solution to us and the
> 15924 JAC won't budge, we can ask them to reserve an ID.
I'm guessing, and maybe it's completely wrong: I guess it's more in
the "IETF style" if somebody (e.g. you) drafts a short text, then we
discuss it until enough of us like it, "sign" it as individuals, and
send it to somebody at the 15924-side. Noting that the individuals
who signed it are currently working on 4646bis in the IETF LTRU WG.
Like Harald's 3683 petition last year, everybody was free to sign it,
some did, others didn't, and after some time Harald sent it to the
IESG or maybe only Scott (the A-D at this time). For something more
"official" we'd need to convince the Chairs and the A-D, that could
get them into lots of trouble (appeals etc.), but what we do or don't
as individuals is nobody's business but our own. Of course we would
not claim to speak on behalf of LTRU, let alone the IETF.
IMO LTRU doesn't "own" the LT space, it only proposes some rules to
manage it, approved by the IESG on behalf of the IETF after a Last
Call. The IETF is free to change those rules later (as it did for
1766 and 3066), and while they are in force the review list "owns"
this space to some (small) degree, most of it is determined by the
source standards following the approved rules.
Frank
RSS Feed