+1<br><br><div><span class="gmail_quote">On 11/10/06, <b class="gmail_sendername">Peter Constable</b> <<a href="mailto:email@example.com">firstname.lastname@example.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
From: <a href="mailto:email@example.com">firstname.lastname@example.org</a> [mailto:<a href="mailto:email@example.com">firstname.lastname@example.org</a>] On Behalf Of Michael Everson
<br><br>>>Perhaps the ISO 15924 RA would like to suggest a alternative solution to<br>>>its user community in view of the request for a solution?<br>><br>> It's not the RA's job to do that, really.<br><br>
It *is* the RAs job to register tags that users want to use, and to service the user needs for which ISO 15924 was created. If the RA does't feel a particular user need should be met using the standard when users are suggesting that it should, then IMO the RA should be prepared to suggest where an alternative solution might lie. Just the the ISO 639 JAC needs to be prepared to do.
<br><br><br>> However, I (for my part) did suggest that the<br>> following might be used:<br><br>Yes, but users are saying these alone are not considered sufficient for the needs, and you have not provided a solution to that extent.
<br><br><br>>>They may differ greatly from one another<br>>>formally, but in terms of function they clearly<br>>>form a group that unites them with one another<br>>>but differentiate them from Latin practical
<br>>>orthographies in common use.<br>><br>> ISO 15924 is based on form.<br><br>Well, let's consider this. Is Fraser a subset of Latin or separate script? In terms of form, it is very clearly a subset of Latin, yet I believe I've heard you say it must be considered a separate script because of its unicameral behaviour. Phonetic transcriptions -- certainly those I'm familiar with -- are absolutely unicameral. (
E.g. in Americanist, "a" and "A" represent distinct sounds.) So, by that line of reasoning, you ought equally to consider phonetic transcriptions separate scripts. I think we'd all agree that that's not where we want to go. But I suggest to you it ought to be enough to say that phonetic transcriptions based on Latin have some distinctive behaviour that warrants considering them a script variant.
<br><br><br>>>But the functionality of phonetic transcriptions<br>>>is clearly distinct, and the desirability for a<br>>>user of getting content in phonetic<br>>>transcription vs. common practical orthography
<br>>>is in general very real.<br>><br>> That still does not mean that IPA, or UPA, or<br>> Landsmålsalfabetet, or Webster's spelling, are<br>> scripts other than Latin. Nor does it mean that<br>> they belong to some collective variant of Latin
<br><br>I think you are too swayed by an academic, graphology perspective and have lost site of the fact that ISO 15924 exists NOT as a form of academic documentation but rather to serve practical IT purposes. (I find this very reminiscent of the es-americas issue: you opposed it because it didn't fit your understanding of dialectology when you were missing the very real practical IT need.)
<br><br><br><br>> I understand that you have a problem because of<br>> the way that your parsing taxonomy works. I don't<br>> see how that translates into changing the intent<br>> of ISO 15924 into<br><br>So, let's revisit the intent:
<br><br>"The codes were devised for use in terminology, lexicography, bibliography, and linguistics, but they may be used for any application requiring the expression of scripts in coded form. This International Standard also includes guidance on the use of script codes in some of these applications."
<br><br>Again, you've got users saying that they have a need -- including in lexicography and linguistics -- to code Latin-based phonetic transcriptions as a script variant. The intent of the standard is to code just such things, and to provide usage guidance. Please encode "Latp", or please provide guidance as to how the practical need can be better met.
<br><br><br><br>> What script is this in?<br>><br>> crdiloetis kari da mza k'amatobden tu romeli iqo upro dzlieri.<br>><br>> It's Latin, isn't it?<br><br>Yes; and note the complete in appropriateness of
<br><br> Crdiloetis kari da mza k'amatobden tu romeli iqo upro dzlieri.<br><br>The capitalization has just turned this content into some completely different "orthography" with no known usage. Clearly this is Latin, but with exceptional rules --
i.e. a distinct variant of Latin.<br><br><br><br>> I comprehend what you are describing. I don't<br>> think that ISO standards should be, hm, abused in<br>> this way.<br><br>This is not an abuse but a very reasonable and practical IT application. It can only be seen as an abuse if you insist of thinking of the intent of the standard as being to provide academic documentation of scripts, or if you find a much better way to engineer solutions to the IT needs. Again, the RA has not done the latter, so I must assume the RA is doing the former, which is deviating from the intent of the standard.
<br><br><br>> *Latp is no different than, say an ISO<br>> 639 tag *enc, taken to be a variety of "eng"<br>> 'English' designed for use by speakers of<br>> varieties of "Commonwealth English" (en-GB,
<br>> en-IE, en-ZA, en-AU, en-NZ) which may share many<br>> features and be difficult for speakers of other<br>> varieties of English to understand. It would make<br>> your filter much easier, but it would be the
<br>> wrong thing to do.<br><br>I think a much closer analogy would be an ISO 639 ID zh that encompasses yue, cmn, etc. And ISO 639 does encode zh.<br><br><br><br>Peter<br>_______________________________________________
<br>Ietf-languages mailing list<br><a href="mailto:Ietfemail@example.com">Ietffirstname.lastname@example.org</a><br><a href="http://www.alvestrand.no/mailman/listinfo/ietf-languages">http://www.alvestrand.no/mailman/listinfo/ietf-languages