Handling of nested .ini-files, structural integrity

[translation-creative-graphics]

Dear community

We are new to Weblate, installed it some days ago and try to achieve the following:

• Component language-files in nested subfolders should be integrated into one translation project (locally or via git, it doesn't matter).
• the files for i.e. plugins, modules, the main component etc. are all in .ini-format, which must be preserved
• the main folder-hierarchy should not be changed: when users download the .zip-file, the structure must be exactly as it was in the original
• we need more placeholders for the language-strings of the subfolders, without Weblate thinking that there are double-files (example: language/*/*.plg_whatever.ini must be possible)
• it must be possible to batch-import and -associate all the files at once. if we have to import them one-by-one and everytime a new "component" must be created, this will be time-consuming for our extensions, as some of them come with up to 120 plugins... the presence of so many components would also clutter the user interface.

Does someone of you experienced users have good idea on how to achieve the above and could point us into "the right direction"?

Thank you very much in advance for your answers.

Have a nice day.
Best regards,

[nijel]

Use component discovery add-on to import a lot of files from the repository: https://docs.weblate.org/en/latest/admin/addons.html#component-discovery

[translation-creative-graphics]

Thank you so much for your help. It works!