<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.apple-style-span
{mso-style-name:apple-style-span;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>And if all else fails, even using AX to manage your language
preference.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>The RP will surely be in your language anyway, so as long as
they localize the “log in” part then the OpenID they enter can surely be used
as a hint as to the language things should be presented in to the user (even prior
to them actually being authenticated).<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Steven<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>http://livz.org<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
general-bounces@openid.net [mailto:general-bounces@openid.net] <b>On Behalf Of </b>Andrew
Arnott<br>
<b>Sent:</b> 29 October 2008 19:12<br>
<b>To:</b> Deron Meranda<br>
<b>Cc:</b> OpenID List<br>
<b>Subject:</b> Re: [OpenID] Google OpenID IDP is now live<o:p></o:p></span></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<blockquote style='margin-left:30.0pt;margin-right:0cm'>
<p class=MsoNormal>I'm not really sure of the whole point to the proposal
anyway; isn't that<br>
what the HTTP Accept-Language header is for?<br>
--<br>
<span class=apple-style-span><span style='color:#888888'>Deron Meranda</span></span><o:p></o:p></p>
</blockquote>
<p class=MsoNormal><o:p> </o:p></p>
<div>
<p class=MsoNormal style='margin-bottom:12.0pt'>I agree. We already have
a standard for languages. Why do these protocols need to tack another one
on at this layer? If browsers don't expose a language preference for easy
enough access for public kiosks, etc., let's get the browsers to fix it.<o:p></o:p></p>
<div>
<p class=MsoNormal>On Wed, Oct 29, 2008 at 12:10 PM, Deron Meranda <<a
href="mailto:deron.meranda@gmail.com">deron.meranda@gmail.com</a>> wrote:<o:p></o:p></p>
<div>
<p class=MsoNormal style='margin-bottom:12.0pt'>On Wed, Oct 29, 2008 at 3:03
PM, Allen Tom <<a href="mailto:atom@yahoo-inc.com">atom@yahoo-inc.com</a>>
wrote:<br>
> Eric Sachs wrote:<br>
>> including on validating the translation of our UI into 40+ languages)<br>
><br>
> How does the RP pass the language preference to the Google OP?<br>
><br>
> The Yahoo OP uses a language preference parameter modeled after the<br>
> OAuth Language Pref extension.<br>
><br>
> <a href="http://wiki.openid.net/OpenIDLanguagePreference" target="_blank">http://wiki.openid.net/OpenIDLanguagePreference</a><o:p></o:p></p>
</div>
<p class=MsoNormal>The language prefs is just a proposal at this point.<br>
<br>
I'm not really sure of the whole point to the proposal anyway; isn't that<br>
what the HTTP Accept-Language header is for?<br>
--<br>
<span style='color:#888888'>Deron Meranda</span><o:p></o:p></p>
<div>
<div>
<p class=MsoNormal>_______________________________________________<br>
general mailing list<br>
<a href="mailto:general@openid.net">general@openid.net</a><br>
<a href="http://openid.net/mailman/listinfo/general" target="_blank">http://openid.net/mailman/listinfo/general</a><o:p></o:p></p>
</div>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</div>
</body>
</html>