How does Weblate choose the language name (folder)?

[juliancoffee]

I'm not sure how to ask this question, but the problem we're facing is the following.
We have language variants in our projects, like Spanish (Latin America), which we specify as es-419.
But it seems that Weblate first discovered this language, but then, when adding a new component, it has created the folder es_419.
Which results in us having two folders per language, while only one of them is valid and recognised by our application (we require _manifest.ron file for language-specific metadata).
The resulting tree looks like that.

assets/voxygen/i18n
├── README.md
├── ar
├── ar-SA
├── be
├── bg
├── ca
├── cs
├── de
├── en
├── eo
├── es
├── es-419
├── es_419
├── eu
├── fr
├── hu
├── it
├── ja
├── ko
├── nb
├── nb-NO
├── nb_NO
├── nl
├── pl
├── pt
├── pt-BR
├── pt_BR
├── ro
├── ru
├── sr
├── sv
├── th
├── tr
├── uk
├── vi
├── zh-Hans
├── zh-Hant
├── zh-Hant-TW
├── zh_Hans
└── zh_Hant

40 directories, 1 file

What would be the steps to fixing it and making sure it doesn't happen again?

[nijel]

What file format do you use? Was the translation file present before, or only the folder with the metadata which is not processed by Weblate?

[juliancoffee]

As fnetX said, yes, we're using Fluent, but the _manifest.ron file is our thing.
Weblate does process both the folder with metadata and without (I think).

We're using multiple components per language, so the translation folder was present before, but then we've added more components to English, and new components (that were missing in other languages) were created and went into the new folder (without the metadata file).

[fnetX]

The variants with hyphen have existed first. The variants with underscore have appeared later.

Language code is set to "Default, based on the file format". Veloren is using Fluent.

[nijel]

Okay, it existed but for a different component.

• You can fix it right now by configuring BCP language code style in the component configuration.
• I think it makes sense to change to BCP as default for Fluent, I've done that in fix(formats): use BCP for naming of Fluent files #15149.
• In the long term, Weblate should handle that more gracefully, I've created Reuse existing folder when creating translations #15148 to track this.

[fnetX]

If we change the format in the component configuration, will Weblate move / merge the files? Or does it require further action?

[nijel]

No, it only affects newly created files. You have to rename them in the repository.