Integrate Angular

with Localazy within minutes.

After upgrading to macOS Big Sur, there’s a chance you may run into an issue with executing Localazy CLI. This is usually caused by incorrect configuration of brew package manager. (Note that this doesn’t apply to binaries downloaded directly from our website, they should be working fine.)

The symptoms look like this, the process is killed without any further output.

To resolve the issue, go to App Store -> Updates and make sure, there’s no update available for Xcode. If yes, click “UPDATE” and wait for it to finish.

After the update, try to run brew doctor and read the output carefully. There could be a warning about outdated CLT and suggested fix.

Let’s run the commands in the specified order and confirm all dialogues that might appear.

• softwareupdate --all --install --force,
• sudo rm -rf /Library/Developer/CommandLineTools
• sudo xcode-select --install

Upgrade Localazy CLI to the latest version by running brew upgrade localazy/tools

And that’s all! You can now verify that Localazy CLI is working again with the localazy -h command.

There is no hard limit at the moment, but it’s recommended to keep the size of each individual item under 4kB. This corresponds to 4,000 characters encoded as UTF-8 and 2,000 characters encoded as UTF-16. Uploading longer texts won’t yield any errors, but might get refused by some external translation engines integrated in Localazy.

You might encounter a message such as:

Phrases 1dbb1f96d2b25755ec8ce882766596c150efecc7 and aaa97c82019600566b80fe5645341518337208ae in Czech cannot be exported correctly - malformed XML. Skipping.

This means that the translation cannot be exported into XML because the translator probably didn’t insert tags correctly, didn’t close them etc.

Please verify these translations and try again.

When you encounter this problem, it most likely means that you are running over your account’s source key limit. Please visit the Marketplace and upgrade your account or increase your source key limit from there.

When using Localazy CLI, setting up a comfortable POT/PO workflow requires some special settings, but is completely possible. Usually the source language file has a different format (POT) than files with translated strings in your project (PO).

We recommend setting two different rules for uploading:

1. Upload your messages.pot file with "type": "pot" and also provide the file attribute to be sure that the filename is, in ideal case, something like messages.po to properly link your POT file to a PO file that is used for your source language internally by Localazy.
2. To upload existing translations inside PO files, use "type": "po" and provide the same file attribute again.

Example configuration 🔗

Your upload configuration should then look like this:

"files": [
  {
    "type": "pot",
    "pattern": "source/messages.pot",
    "file": "message.po"
  },
  {
    "group": "existing-translations"
    "type": "po",
    "pattern": "translations/*/messages.pot",
    "file": "message.po"
  }
]

Localazy CLI is pretty complex, but there is a good reason for that - to help you fully automate uploads and downloads of your strings and translations. 😊

If the CLI doesn’t behave as you think it should, don’t worry, everyone can get stuck, and the documentation might not provide an answer to your specific case.

So, if you encounter a problem or make a mistake when configuring your CLI rules, send us a message via our chat, and we will do our best to help you quickly.

Or you can send an e-mail to [email protected] with your configuration and describe what you are trying to achieve. We will respond as soon as possible so you can continue using Localazy without any issue.