ID for language-invariant strings
CE Whitehead
cewcathar at hotmail.com
Tue Mar 18 18:15:38 CET 2008
Hi, I believe that Doug said Karen had reported that the subtag [zxx] was originally broader in meaning; so yes I think a subtag modification request to broaden its meaning would be a good idea.
At the same time, I think we should clarify the usage of [und].
--C. E. Whitehead
cewcathar at hotmail.com
Peter Constable petercon at microsoft.com wrote
> So, we still have three sets of opinion on how to tag. Let me ask a different question: do
> people think there should be a single convention to be used for the kind of scenario I’ve
> described, or should the be left to be determined by application developers?
Absolutely!
> Some clarifications wrt my specific application scenario: the strings are not intended to be
> presented to users as a fallback, they are intended for programmatic usage.
[zxx] is for programmatic usage
That said, some application could still choose to use this form of the font-family name to present to users as a fallback.Karen_Broome at spe.sony.com Karen_Broome at spe.sony.com Mon Mar 17 22:25:05 CET 2008
> Any chance we could broaden the semantic of the "zxx" tag?
> I still think we did the wrong thing here and the "non-applicable" tag is
> more appropriate for all the use cases mentioned.
Agreed, this is the solution
> > I can keep restating the point I've made from the beginning. The> > semantic for "zxx" should have been defined as "not applicable"> > which was the use case presented at the time it was created. Since> > it was not expressed in this way, now we need another tag, I think.> >
?? Another subtag??
Peter Constable petercon at microsoft.com Tue Mar 18 17:03:28 CET 2008 > The intent of the description on the ISO 639-3 site could be interpreted in three ways:
> (i) the author cannot identify the language> (ii) the language cannot be identified by any body of experts> (iii) the reader is not able to assume any language identity
We need to clarify this.
C. E. Whitehead
cewcathar at hotmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.alvestrand.no/pipermail/ietf-languages/attachments/20080318/4e4cf1b2/attachment.html
More information about the Ietf-languages
mailing list