<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body class='hmmessage'>
Hi.<BR><BR>
I agree that [mis] is not appropriate. I'm not sure that [zxx] is appropriate either (I'd have to see the strings). Regarding [und], that is for when you "can't be reasonably sure what the language is" () and the text it is embedded in is tagged for language (<A href="http://www.w3.org/International/questions/qa-no-language">http://www.w3.org/International/questions/qa-no-language</A>) (I'd have to see the strings again to form an opionion on the appropriateness of [und]).<BR>
<BR>
Regarding [i-default],<BR>
section 4.5 of RFC 2277 ( <A href="http://www.iana.org/assignments/lang-tags/i-default">http://www.iana.org/assignments/lang-tags/i-default</A> ) begins<BR>
"When human-readable text must be presented in a context where the<BR> sender has no knowledge of the recipient's language preferences (such<BR> as login failures or E-mailed warnings, or prior to language<BR> negotiation), text SHOULD be presented in Default Language."<BR>
<BR>
<BR>
Michael Everson suggested you send us the text in question, and, if you don't think [i-default] is appropriate, then you might send it and explain why, I guess.<BR><BR>
--C. E. Whitehead<BR>
<A href="mailto:cewcathar@hotmail.com">cewcathar@hotmail.com</A> <BR><BR>
> From: Peter Constable <petercon@microsoft.com><BR>> Subject: ID for language-invariant strings<BR>> To: "ietf-languages@iana.org" <ietf-languages@iana.org><BR>> Message-ID:<BR>> <DDB6DE6E9D27DD478AE6D1BBBB83579562DEA50201@NA-EXMSG-C117.redmond.corp.microsoft.com><BR>> <BR>> Content-Type: text/plain; charset="us-ascii"<BR>> <BR>> What are people's thoughts about language tagging for language-invariant strings?<BR>> <BR>> I'm working with a group on an application scenario in which we have a table of strings in various languages that name entities, but we also need to support entries that have a reference name that is considered a language-neutral form of a name for a given entity.<BR>> <BR>> Strictly speaking, these would be strings intended for programmatic operation and not human <BR>
> consumption, and so, some might argue, are not in scope for IETF language tags. However,<BR>
> these are exceptional: almost all of the strings in the same table are intended for human<BR>
> consumption, and RFC 4646 is the spec being applied for identifying the language of strings in > the table. Moreover, the strings in question *are* (in general) in a human language; they are > just the values that are adopted to be used for language-neutral referencing.<BR>> <BR>> The "i-default" tag is not appropriate for this: these are not default display strings. <BR>
??? I'd like to see the strings.<BR>
<BR>
> And "zxx" is > not appropriate since, in fact, there is linguistic content. The "mis" tag doesn't <BR>
> seem like the <BR>
> right choice: we do not want an ambiguous ID that could be applied to other entries intended <BR>
> for a different purpose (strings intended for human consumption that happen to be in an <BR>
> uncoded language.) The "und" tag might be usable, though that doesn't seem quite right to <BR>
> me: we're not intending to say that the language is (as yet) undetermined (and might be > determined later); rather, we want a value indicating 'this is special content used as a<BR>
> referential key - the language of the content is irrelevant'.<BR>> <BR>
<BR>> <BR><BR>> From: Michael Everson <everson@evertype.com><BR>> Subject: Re: ID for language-invariant strings<BR>> To: "ietf-languages@iana.org" <ietf-languages@iana.org><BR>> Message-ID: <p06240815c3fe881766a4@[86.43.5.15]><BR>> Content-Type: text/plain; charset="us-ascii" ; format="flowed"<BR>> <BR>> Peter,<BR>> <BR>> I can't even begin to understand what "language-invariant" is meant <BR>> to mean. You say you are talking about some group of language names. <BR>> Favour us please with the actual language and or names, please, or <BR>> this idea should just fade away into the vagueness you have given us <BR>> about it.<BR>> <BR>+1<BR>> <BR>><BR></body>
</html>