Urgent Issue with CLI and Localization Service

CLI
#1

Hi,

We’ve hit a dead end while using your service and its CLI. Here’s the problem:

We use Directus along with an extension to sync locales with your platform. It appears that Directus (or your extension) imports the source locale incorrectly. As a result, when we run npx localazy download, the default fallback value from the source locale is applied to ALL “Missing translations” across all languages.

This is EXTREMELY inconvenient. From what we can tell, your CLI does not provide an option to exclude untranslated languages.

We urgently need a solution - specifically, a way to download ONLY translated keys without default fallback values. What options can you offer to resolve this ASAP?

Looking forward to your prompt response.

#2

Hello, can you please send me your CLI configuration (including keys, they are safe with me and you can later regenerate them) to vaclav@localazy.com?

#3

Hi,
I would like to second this request. We have a project that handles translations for multiple services, some use JSON format and others use PO format for the translation files.
In all cases the services themselves handle the fallback languages and thus there is never a need for the translation files to already have a fallback applied to them.

To make matters worse, we don’t ever want to fall back to the source as this is english as invented by developers, not the wording the business wants to use. So if a fallback were to be applied it should be the preferred source, not the source.

We use the following configuration (sample json):

{
  "upload": {
    "deprecate": "file",
    "features": [
      "filter_untranslated"
    ],
    "files": [
      {
        "type": "json",
        "pattern": "**/*.json",
        "lang": "en"
      }
    ]
  },
  "download": {
    "folder": "locale",
    "files": "${lang}/${file}"
  },
  "conversion": {
    "folder": "locale",
    "actions": [
      {
        "changeExtension": "po",
        "type": "po",
        "output": "${lang}/LC_MESSAGES/django.po"
      }
    ]
  }
}

This is as far as I was able to get it to work, except the converted po file still falls back to the source. So the downloaded JSON is good, the converted download into PO is not. I’m running out of options to fix this with the CLI and unfortunately that would mean I have to run a manual post Download script to convert the JSON to PO. Something I was hoping to avoid as I would like to keep the sync elegant.

I guess the unfortunate thing is that because Localazy does too much work, I have to do more work to undo it…
So I second the request for more control over the omitting empty / untranslated values from the downloads or converted files. This feels like a very strange default as I cannot imagine a case in which I would ever want this behaviour.