Your help is needed: localization

[GoogleCodeExporter]

Version 1.2 of openid-selector will be about localization. For this purpose we 
need your help in translating one (attached) file to your local language.

File that needs to be translated is attached (openid-jquery-en.js). Please 
translate "label" strings and attach your translated file in format 
openid-jquery-<2-char ISO language code>.js, i.e. openid-jquery-de.js for 
German, openid-jquery-fr.js for French, etc.

Russian and Ukrainian versions are already done.

Original issue reported on code.google.com by andriy.gerasika on 10 Oct 2010 at 7:18

Attachments:

• openid-jquery-en.js

[GoogleCodeExporter]

Original comment by andriy.gerasika on 10 Oct 2010 at 7:49

Attachments:

• openid-jquery-en.js

[GoogleCodeExporter]

Update:
you may change list of providers according to popularity in your country. For 
example, I guess in France AOL is not very popular, but Orange is -- you may 
change AOL to Orange in French version (don't forget to put correct OpenID 
url), etc.

Original comment by andriy.gerasika on 11 Oct 2010 at 7:11

[GoogleCodeExporter]

Think it is hard to find the local preference. A global solution would be 
better. What a about a guide to add an localized version. 

Original comment by b.wender...@gmail.com on 11 Oct 2010 at 10:29

[GoogleCodeExporter]

Localization is a good idea, but I'm not sure its necessary for this project - 
or at least not yet.

It's pretty easy for users to change the strings and OpenID providers to their 
own requirements. Perhaps it would be better to document how to localize the 
Javascript and leave it at that for now? We can always come back to this if 
more people request it.

Original comment by and...@gmail.com on 11 Oct 2010 at 6:26

[GoogleCodeExporter]

It is relatively easy to translate Javascript, but will be not easy to generate 
image map for Issue 20.

User can easily make a mistake, it is not trivial and will take a lot of time. 
Therefore localized versions should be pre-prepared.

Multi-site CMS setups, i.e. when one code base is shared for all websites, will 
also benefit from multi-language version. (I have multi-site)

Original comment by andriy.gerasika on 11 Oct 2010 at 7:33

[GoogleCodeExporter]

actually file to be translated can be downloaded via
http://code.google.com/p/openid-selector/source/browse/branches/1.2/js/openid-jq
uery-en.js

Original comment by andriy.gerasika on 17 Oct 2010 at 11:25

[GoogleCodeExporter]

Here's the German translation...However, I believe the English version isn't a 
good basis for the translation because:
- it contains odd phrases
- it's inconsistent, see Blogger vs. VeriSign vs. WordPress -> the version used 
by stackoverflow.com at http://sstatic.net/Js/third-party/openid-jquery.js?v=7 
is much cleaner

Original comment by marcel@frightanic.com on 18 Oct 2010 at 8:30

Attachments:

• openid-jquery-de.js

[GoogleCodeExporter]

what kind of odd phrases do you mean?

Original comment by andriy.gerasika on 18 Oct 2010 at 9:09

[GoogleCodeExporter]

openid.demo_text = 'In client demo mode. Normally would have submitted OpenID:';
openid.signin_text = 'Sign-In';

openid.demo_text should use "real" (as in 'complete') sentences.
The value for openid.signin_text is a little odd or inconsistent because it 
uses the term "sign in" when everywhere else "log in" is used. I think either 
is fine it should simple be consistent across the various labels.

If you guys are interested I can provide a Japanese translation, too. Which 
charset/encoding would you like me to use for the .js file in this case?

Original comment by marcel@frightanic.com on 18 Oct 2010 at 11:19

[GoogleCodeExporter]

about Sign-In text in submit button -- stackoverflow uses "Sign In" for its 
submit button
generally about wording -- these are exactly the same as in original v1.0 
release, I can't really judge on that since I am not native English speaker.

about Japanese -- yes, UTF-8.

Original comment by andriy.gerasika on 18 Oct 2010 at 11:43

[GoogleCodeExporter]

Original comment by andriy.gerasika on 21 Oct 2010 at 2:03

• Changed title: Your help is needed: localization

[GoogleCodeExporter]

Japanese translation attached. As for the charset issue, you might want to 
change

  <script type="text/javascript" src="js/openid-jquery-en.js"></script>

in demo.html to

  <script type="text/javascript" src="js/openid-jquery-en.js" charset="UTF-8"></script>

and make sure all .js files are UTF-8 encoded. Otherwise you'd have to write 
instructions for someone using the Japanese translation to add charset="UTF-8" 
manually.

Original comment by marcel@frightanic.com on 26 Oct 2010 at 5:59

Attachments:

• openid-jquery-jp.js

[GoogleCodeExporter]

Arigatou

about encoding: I added
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
to all HTML files and it works ok now on Windows IIS

Original comment by andriy.gerasika on 26 Oct 2010 at 8:38

[GoogleCodeExporter]

new URL for the file that needs to be translated:
http://code.google.com/p/openid-selector/source/browse/trunk/js/openid-en.js

Original comment by andriy.gerasika on 13 Nov 2010 at 7:56

[GoogleCodeExporter]

This is the Simplified Chinese translation.

Original comment by zhoushu...@gmail.com on 15 Apr 2011 at 6:11

Attachments:

• demo-zh_CN.html
• openid-zh_CN.js

[GoogleCodeExporter]

thanks, Chinese translation has been incorporated into SVN trunk

Original comment by andriy.gerasika on 2 May 2011 at 8:59

[GoogleCodeExporter]

Here is traditional Chinese translation

Original comment by kent.yeh...@gmail.com on 3 Jun 2011 at 3:10

Attachments:

• demo-zh_hant.html
• openid-zh_hant.js

[GoogleCodeExporter]

thanks, Traditional Chineese translation has been incorporated into trunk

Original comment by andriy.gerasika on 6 Jul 2011 at 12:15