Translating the Badíʿ Calendar Web Extension

Translating the Extension into Your Language!

To help translate the project, please send an email to glen.little@gmail.com and mention which language(s) you want to help with!

He'll do the initial translation using AI, and you can then make fixes and adjustments as needed and put in your fixes in this github repo.

Tips

• See this Style Guide for some more tips.

• When working on a phrase to be translated, the "Key" and "Developer's note" may provide clues to the context. 

If you have any questions, please do not hesitate to send an email to Glen!

Translating the entire web extension is a significant undertaking. To get started, here is a suggested list of phrases to work on first: 

Testing your Translation

To make an effective translation, you will sometimes need to see the words in context. The context may not be obvious when editing the list of words and phrases.

At a minimum, you should have the English extension installed on your computer and view it as you edit the file. Most of the messages in the file can be seen on the screen when viewing the extension.

In most cases, the translated messages will work fine. However, if the text is much longer or shorter than the English message, the layout of the screen may need to be adjusted. You will need to collaborate with Glen Little to do this.

You can also view your translation in the extension on your own computer! 

This is more technical, so recommended only if the instructions below are easy for you to follow.

To view the extension in your language as a developer:

• If your computer does not normally show in the language you are translating into, you can create a new icon for each language you want to view in Chrome.  If you are translating into your computer's normal language, you can skip this step.

  • Create a new, empty folder for each language.  For instance, after making a folder called "ChromeLanguageFolders", add a folder in it for your target language:

• • • In this copy, add to the end of the "Target" field:   --lang=locale  --user-data-dir=c:\locale_profile_dir

    • For example, the "locale" for Spanish is "es", so to have a Spanish browser, the Target should look like this:

      •    "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe"      --lang=es      --user-data-dir=D:\ChromeLanguageFolders\es

• Download the "Extension......zip" file (download from the link at the bottom of this page)

  • Choose a new location on your computer to store the ZIP file. (Do not use the locale_profile_dir from the previous step!)

  • Expand the ZIP file to a new folder on your computer.  If you are getting a newer version of the Extension, you can re-use the same folder and overwrite what was there.

  • In the "_locales" subfolder there, find the folder with the locale code for the language you are translating for.

• Download your translation file from the PhraseApp website using the "Download" button on the "Locales" page:

• • Rename the downloaded file to be "messages.json" and put it in the locale folder you identified before, replacing what is already there.

• Set your browser to "Developer Mode"

  • Go to the "Manage Extension" settings page in Chrome Browser and check the Developer Mode checkbox.

  • The use the "Load unpacked extension..." button, and select the folder where you expanded the ZIP file to.

• • • If you have created a special version of the browser to test this language, you will likely only have one copy of the extension.

• If you make local changes in the "messages.json" file, you need to click the "Reload" link visible in the image above, in step 4.2.