File structure in Dashboard > Translation is different than in GitHub integration branch configuration

Crowdin Issues
1

Hello,

I am facing an issue where the Crowdin dashboard displays the incorrect file name for translated files. Specifically, for the Lithuanian language, the file is displayed as en.json in the dashboard, even though the correct file in my repository i
s named lt.json.

crowdin3
crowdin31520×559 39.4 KB

Here’s my configuration:

  • Source Files Path: /locales/en/*.json
  • Translated Files Path: /locales/%two_letters_code%/%two_letters_code%.json
  • Expected Output: For Lithuanian, the file should appear as locales/lt/lt.json.
  • Issue: The translation file appears correctly in my repository, but the Crowdin dashboard misleadingly shows it as en.json under the en folder.

Steps I’ve Taken:

  1. Verified the repository structure, where the file is correctly named lt.json.
  2. Checked the language mapping, ensuring that Lithuanian is mapped to lt.
  3. Re-synced the repository with Crowdin to apply the configuration.

Despite this, the issue persists, and I’m not sure if this is a configuration problem or a bug. Has anyone else encountered a similar issue? If so, how did you resolve it?

Best regards,

2

Hello @kacper.zabielski

In the Crowdin dashboard files are shown with source name, i.e. if your source is named “en-US.json” for all languages it will be shown as en-US.json.

The translated files section of the integration configuration is just a preview of the structure/names you receive when exporting translations.

The dest parameter will allow you to specify a file name for Translators (Configuration File | Developer Portal), but it still will be 1 for all languages (you can remove en-US for example and have just “Master_file.json”

1 Like