Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Internationalization submission system #80

neocotic opened this issue Mar 6, 2012 · 3 comments

Internationalization submission system #80

neocotic opened this issue Mar 6, 2012 · 3 comments


Copy link

neocotic commented Mar 6, 2012

Create a system that will allow anyone to submit translations of the i18n messages.

To simplify the translation for potential authors, descriptions should be added to messages and examples should be added to placeholders (where appropriate).

Key points;

  • Any technology and/or service can be used to achieve this
  • Preferably, create a framework that could be used for other extensions
  • Will probably need an area for authors (translate and submit), users (review), and developers (review and manage)
  • Could possibly implement voting/veto system to allow collaboration

Information to be captured:

  • Author name & email address (which should be added to list of contributors and used when updates are required)
    • Both should be validated
  • Locale code (selected from a dropdown containing all support languages.
  • Version of the extension that the translation is based on
  • JSON generated for all of the translated messages
    • Invalid messages (i.e. blank) are excluded from results
    • Message descriptions and all placeholders are taken from the source translation and thus should always be in the original language
    • Messages and placeholders are sorted alphabetically

Additionally, another system (or feature of this system) is recommended to diff' translations in order to detect what - if any -messages are missing from a submission and that any placeholders that are omitted are highlighted.

A recommended final step for the process is to roughly translate (e.g. using Google Translate) for quick-scan checks for malicious submissions. If a single malicious is found the whole translation is rejected and the author is then informed.

Finally, the CSS for the options page and desktop notifications will need to be changed to support different text directions. For example;

body {
  direction: __MSG_@@bidi_dir__;
@ghost ghost assigned neocotic Mar 6, 2012
Copy link
Member Author

neocotic commented Mar 6, 2012

Brainstorming use cases for a possible web flow solution...


  1. Display Dashboard


The dashboard displays different in the following contexts;

  • Authenticated:
    • Extension: Display versions with a link to Version Registration
    • Version: Display version overview (messages etc.) and submissions with a link to Translation
    • Translation: Display expanded version overview, edit fields for each message and reviews
    • None: Display stat widgets for owned and other extensions and translations with a link to Extension Registration
  • Unauthenticated:
    • Display stat widgets with a link to User Registration

User Registration

  1. Authenticate user
  2. Display links to Dashboard and Extension Registration

Extension Registration

  1. Authenticate user
  2. Request and validate extension ID
  3. Check if extension ID exists and that user email matches that on the web store (using logic similar to MyExtensions)
  4. Store extension
  5. Display Dashboard in extension context

Version Registration

  1. Authenticate user (must be owner of extension in context)
  2. Display Dashboard in version context
  3. Request and validate contents of messages.json for that version
  4. Parse contents as JSON and continue validation
  5. Store contents along with current timestamp (used for versioning)
  6. Display Dashboard in version context


  1. Authenticate user
  2. Display Dashboard in translation context
  3. Request and validate target locale
  4. Request and validate message translations
    • Perform visual progress updates throughout the translation process (e.g progress bars and ticks)
  5. Store translation for review

Copy link
Member Author

neocotic commented Mar 6, 2012

Another alternative is to check out crowdin as it might already suit my needs. Open source projects are free but I need to complete their moderation form.

Copy link
Member Author

neocotic commented Mar 6, 2012

After all that it seems crowdin is the perfect solution! They don't charge open source projects and support Google Chrome Extensions off the shelf.

I'll keep this open as I need to update the FAQ to document this but anyone can now submit a translation using at

Also, I want to add descriptions and examples to all messages and placeholders respectively as well as add new messages to cover the web store text. API keys and OAuth client ID and secret should be moved back in to the code from the i18n bundles to simplify translations.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet

No branches or pull requests

1 participant