ID for language-invariant strings

CE Whitehead cewcathar at
Sat Mar 15 18:45:51 CET 2008

Hi,I now support Mark who suggested you use [und].  I still do not see the need for another subtag here; we have [zxx], [mul], [mis]. and [und].I still need convincing that we need another subtag.
To me the solution would be to add a comment to [und] stating that it can be used when some text processing might be needed.  (We also might also add comments explaining [mis] and [mul]--for me I'd only use [mul] when I was targeting speakers of multiple languages.)
To me you have not determined the language of your strings; it seems that's what you are saying; so go for [und].
Best, C. E. W.* * *ID for language-invariant stringsPeter Constable petercon at >> I don't understand the problem here...>> Hyphenation should leave them alone; word wrapping>> should do something basic, etc. (Converting a space to a new line is>> theoretically an error in your names as it might be in program text,>> but in both cases, if it's one the author worried about, they should>> have set it non-wrapping.) Language detection and "smart">> handling is wrong; changing a font named "Coöperate!"  to "Co->> <NL>operate!" is entirely correct English, but wrong for a fontname,> I wasn't suggesting that such things be done to name strings that get used in programmatic APIs, nor that things like spelling changes or other transformations might be applied to the data itself. But it may be appropriate to do things with copies of the data for intermediate purposes to obtain some result. For example, suppose from a long list of reference names for cultural elements from some domain, the app wants to support some search functionality, and wants to apply stemming or recognize alternate spellings in order to provide relevant results. > PeterTo process these are you not going to have to indicate the language of each then?  I guess you are simply saying that you want to recognize the alternate spellings as valid names; and then process.  So you want a subtag that permits processing.  But not [und]?  I don't see the point of having the subtags [zxn] and [und].  [und] is for content in an undetermined language whereas [zxn] is for text that should not be processed ( ).  I now support Mark who suggested you use [und]. * * *Frank Ellermann nobody at > > What's the rule for personal names?> A general rule could be "tags are not only about translations",> and tags also depend on the context (document type + language).> FrankAgreed that will work! C. E. Whiteheadcewcathar at
-------------- next part --------------
An HTML attachment was scrubbed...

More information about the Ietf-languages mailing list