Becoming a translator of AdoptOpenJDK.net

1. Request access to LocalizeJS.com for your specialist language(s). You can do this by raising an issue on this repository requesting access.
2. Follow the email instructions to create an account, then log in.
3. Go to https://localizejs.com/phrases
4. On the left menu bar, select your language, then use the following areas:
   • Published: phrases that have either been machine translated by Google or human-translated, and have been approved.
   • In Progress: phrases that have been marked as needing translation, but their translations have not yet been approved.
   • Pending: phrases that need to be reviewed - do they need translation, or are they universal terms, i.e. names?
   • Archive: phrases that have been marked as not needing translation.
5. Please make sure that the source phrase is in English as sometimes Localise is treating other languages as the canonical source (which is wrong).
6. To change the existing translated text, click on it in the phrase area on the right side, type your new translation, then click the green 'Propose' button, then the 'Publish' button that appears afterwards.

Alternatively, you can use the WYSIWYG editor here: http://localizejs.com/editor - this area displays the website visually, which some translators might prefer. Just click on a phrase to make it appear on the left-hand side, where you can edit the translation as before.

What to do if you see non English source material

The library should not be detecting translated phrases. We have noticed this happening before and our engineering team is focused on a fix. In the meantime, we created a saveNewPhrasesFromSource library option you can add and default to true in the initialization code. Once you add this configuration option, it will not be retroactive but moving forward should not pull in translated content. Here is an example:

Localize.initialize({    
     key: 'YOUR PROJECT KEY',    
     rememberLanguage: true,    
     saveNewPhrasesFromSource: true,  
});