[Openid-specs-ab] [openid/connect] All clarify that language tag values used need not be unnecessarily specific (issue #812)
issues-reply at bitbucket.org
Mon Mar 18 18:41:47 UTC 2013
--- you can reply above this line ---
New issue 812: All clarify that language tag values used need not be unnecessarily specific
I believe that we should clarify for Connect that langauge tag values should only be as specific as necessary. For instance"en" may be used rather than "en-US". This was explained well in this message to the webfinger list.
From: webfinger-bounces at ietf.org [mailto:webfinger-bounces at ietf.org] On Behalf Of Stephane Bortzmeyer
Sent: Friday, March 15, 2013 8:19 AM
To: webfinger at ietf.org
Cc: ietf-languages at alvestrand.no
Subject: [webfinger] Language tag too specific (Was: Last Call: <draft-ietf-appsawg-webfinger-10.txt> (WebFinger) to Proposed Standard
Another issue with language tags in draft-ietf-appsawg-webfinger-11.txt:
> "titles" :
> "en-us" : "The Magical World of Bob",
> "fr" : "Le Monde Magique de Bob"
I understand that the purpose of the example is to show that you are not limited to the primary langauge subtag, you can add other subtags (here, the region "us"). But the example is not well chosen. RFC 5646 says:
> Use as precise a tag as possible, but no more specific than is
> justified. Avoid using subtags that are not important for
> distinguishing content in an application.
> * For example, 'de' might suffice for tagging an email written
> in German, while "de-CH-1996" is probably unnecessarily
> precise for such a task.
Which seems to apply exactly here (there is nothing US-specific in the sentence). May be, instead:
"en-us" : "The Magical Theater of Bob",
"en-gb" : "The Magical Theatre of Bob",
"fr" : "Le Théâtre Magique de Bob"
webfinger mailing list
webfinger at ietf.org
This is an issue notification from bitbucket.org. You are receiving
this either because you are the owner of the issue, or you are
following the issue.
More information about the Openid-specs-ab