p3p policy in languages other than english

[Ben]

Has anyone done this on their site?

I'm trying to support a french version of a p3p policy.

http://www.w3.org/TR/P3P/#multiple suggests this should be easy, but
I've now added xml:lang="fr" to all the elements it listed AND return
the Content-Language header "fr" AND set up my language preference with
French on top and I'm still getting alot of English. I see some
French, complete with correct accent marks (this is text that it's
pulling out of the backend policy) but mostly what I see is in english.


That stuff (90+% of the policy), I assume it is generating from the
compact policy. There was actually a time when I got rid of the whole
compact policy and I still saw this content, and in english, but that
doesn't make a lot of sense and may have been a caching issue. Is
there anything to put on compact policies themselves so the browser
knows to generate content in a particular language from it? Haven't
had success googling for that.

I've been watching the requests with ieHTTPHeaders, everything makes
sense, the Content-Language header is definitely coming back as "fr".
I just don't know where to go on this anymore.

 

[Rob ^_^]

Hi Ben,

Are you using the French version of IE?

From this reference

http://msdn.microsoft.com/library/d...rity/privacy/overview/createprivacypolicy.asp

it appears that the xml policy statements are fed to the browser and
rendered in a built-in dialog (probably res://shdocvw.dll/something.html)

You could also try changing you language preferences in the Internet Options
Languages dialog.

I think the logic of this is that your p3p statement will have a link to a
html version of your privacy statement that can display the policy in the
users language settings.

Regards.

 

[Ben]

Hey Rob,

Thanks for your quick response.
A couple more questions.

I had tried reordering then finally dropping english entirely in the
language preference in IE in favor of french. I didn't go to the point
of uninstalling IE and reinstalling in french for fear of what might
break in windows.

I found the dll you were talking about, but am not really a windows
guy, so I don't know how to find the html packaged within to confirm
what you're saying. (This also explains why I (1. Dislike IE 2. Am
concerned of what might break if muck with IE much))

What do you think would be the easiest, most productive next couple of
things for me to try?

Thanks,
Ben