Generate i18n credits file when bumping translations

The i18n credits file was previously generated at build time, but doing
this when bumping translations makes more sense because this way
translators are added to the credits file when their translations are
added to the git repo (and not before that).

This change also removes the i18n credits file from .gitignore so it is
checked in the repo, and it is persisted. This will also make it easier
to track changes in the list of translators.

Also, an added benefit is that now everyone can build the extension.
This is because previously it was necessary to have a private API token
in order to generate the i18n credits file at build time (otherwise the
build failed).

Change-Id: Iecfd7ffd409aedc875f9d84cff0549f8d102d330
5 files changed
tree: 6f8604c3b5318805404edde1c203112cfd39b707
  1. docs/
  2. src/
  3. templates/
  4. tools/
  5. .clang-format
  6. .editorconfig
  7. .gitignore
  8. .gitreview
  9. .jsbeautifyrc
  10. .zuul.yaml
  11. generateManifest.bash
  13. Makefile
  14. OWNERS
  16. release.bash
  17. tagRelease.bash


The source code of the Chrome "Translate Selected Text" extension.

Do you want to help to translate this extension's UI?

If you want to help bring this extension into your native language, you can, and I would really appreciate it! Just go to the following website and start translating :)



Please, report any bugs or feature sugestions at GitHub:

Beta version

As this extension has so many users, I've decided to upload a Beta version of the extension to the Chrome Web Store so I can test it before uploading any update to the stable version! This way I can make sure that the stable version of the extension is 100% bug-free.

If you want to test the bleeding edge of this extension before everybody else, join the Google Group and download the extension (there may be bugs, you've been warned):

Special thanks

Special thanks to:

  • All the users who use the extension every day and who trust the model of developing simple extensions which do not request any privacy-breaking permissions.
  • All the users who have contributed translations. You rock!
  • BrowserStack for allowing me to use their awesome services in order to test the extension in multiple versions of Chrome and in different operating systems.

More documents