Transifex

  • Documentation
  • CLI Client
  • FAQs About the Client

FAQs About the Client

Can I use the client behind a proxy?

To use tx behind a proxy to connect to Transifex, you must export your proxy info into an local environment variable with the following commands:

$ export http_proxy="proxy:port"
$ export https_proxy="proxy:port"
$ export http_proxy="user:passwd@proxy:port"
$ export https_proxy="user:passwd@proxy:port"

I got an HttpNotAuthorized error. What does it mean?

If you get an "HttpNotAuthorized: Authorization Required" error message after running a tx command, this means the Transifex client cannot access the projects needed. In this case, check for two things:

  1. Whether the credentials in your ~/.transifexrc file are correct. If needed, edit the file directly and update your credentials.
  2. Whether the account associated with the credentials in your config file has permission to access the project. You can verify this by logging in to Transifex and checking whether the project shows up in the dashboard. If you're trying to push files to a project, then you must also be a Maintainer of the project.

CLI Client vs Direct Integration

Why use Transifex CLI client?

  • The Transifex CLI client works with any version control system, and can be easily plugged into existing CI tools as an extra step in your workflow.
  • The transfer of (source and translated) content between Transifex and your repository is completely controlled by you. Transifex does not need (read/write) access to any internal infrastructure for these actions to be performed.
  • It can be installed by developers in their local development environments for early testing.
  • Translated content can be pulled directly from Transifex based on your localization needs instead of being stored in your version control repository. Developers can decide which translations will be pulled, when, how often and where they will be stored. To store translations in your repository, some configuration or scripts are needed. The configuration depends on the CI tool used (e.g. Jenkins, Travis CI, CircleCI etc.). An illustrative example can be found here.
  • Maintenance of this integration is in your developers’ hands.
  • Developers can work with feature branches and push their work to Transifex without having to merge their work to the master branch first.

Why integrate directly with GitHub or Bitbucket?

  • Transifex’s direct integrations with GitHub or Bitbucket is easily set up through a set-up wizard and requires little configuration.
  • It enables translations to be stored directly in your GitHub or Bitbucket repository.
  • Pushing content into Transifex and pulling translations from Transifex is performed automatically through simple commits and pull requests.
  • Transifex will handle any maintenance and updates of the integration.