Multi language TBX files

[nijel]

Hi, I still struggle to get TBX files imported.

When adding this testfile:
https://github.com/openSUSE/suse-terminology/blob/main/TBX/multilingual/for_Weblate/Export%20for%20Weblate.xml

To a repository I need to rename it to "Export for Weblate_en.xml" that it is found during scan.
Also the manual upload need to have a zip with the same file within.

BUT: in both ways nothing is parsed.

The file by Suse is "multilingual" because it contains all languages within one.
On the help page https://docs.weblate.org/en/latest/formats.html it is written as "biligual".

The sample document on https://docs.weblate.org/en/latest/formats/tbx.html cannot be used as well.

Can you give some hint on how to use TBX files now?

During the tests I could import this file successfully now:
https://github.com/WeblateOrg/weblate/blob/main/weblate/trans/tests/data/fr-extended-metadata.tbx

I will investigate further but we might want to update the TBX page for this.

Thanks a lot
Stephan

Originally posted by @snoerenberg in #12795

Multilingual files are not supported by Weblate, so that's expected. These files were linked only to show the syntax.

Originally posted by @nijel in #12795

Hi,

I digged a bit deeper into this. The document in the help section cannot be imported at all.
https://docs.weblate.org/en/latest/formats/tbx.html (not yet checked why).

I created a minimal sample: upload.zip

For easier replication I used the file upload.

The "en" file is monolingual:

            <termEntry id="e2">
                <descrip type="definition">3rd level maintenance resolves documented errors and malfunctions in software which is part of the maintenance contract and perform additional pre-determined maintenance tasks. Specialists from all areas are involved.</descrip>
                <langSet xml:lang="en">
                    <tig>
                        <term id="e2-en">3rd level maintenance</term>
                    </tig>
                    <tig>
                        <term>3rd Level Maintenance</term>
                    </tig>
                </langSet>
            </termEntry>

The "cs" file is bilingual:

            <termEntry id="e2">
                <descrip type="definition">Údržba 3. úrovně řeší zdokumentované chyby a závady softwaru, který je součástí smlouvy o údržbě, a provádí další předem stanovené úkoly údržby. Na údržbě se podílejí specialisté ze všech oblastí.</descrip>
                <langSet xml:lang="en">
                    <tig>
                        <term id="e2-en">3rd level maintenance</term>
                    </tig>
                    <tig>
                        <term>3rd Level Maintenance</term>
                    </tig>
                </langSet>
                <langSet xml:lang="cs">
                    <tig>
                        <term id="e2-cs">údržba 3. úrovně</term>
                    </tig>
                </langSet>
            </termEntry>

This leads to having the definition (source string explanation) in Czech on the English entry.

The Czech entry looks okish but I would expect it also at "Translation explanation" instead of "Explanation".

Can you give me some hint on how the files must be created to get not the languages mixed up in the explanation?

Thanks
Stephan

Originally posted by @snoerenberg in #12795

Hi,

I digged a bit deeper into this. The document in the help section cannot be imported at all.
https://docs.weblate.org/en/latest/formats/tbx.html (not yet checked why).

I created a minimal sample: upload.zip

For easier replication I used the file upload.

The "en" file is monolingual:

            <termEntry id="e2">
                <descrip type="definition">3rd level maintenance resolves documented errors and malfunctions in software which is part of the maintenance contract and perform additional pre-determined maintenance tasks. Specialists from all areas are involved.</descrip>
                <langSet xml:lang="en">
                    <tig>
                        <term id="e2-en">3rd level maintenance</term>
                    </tig>
                    <tig>
                        <term>3rd Level Maintenance</term>
                    </tig>
                </langSet>
            </termEntry>

The "cs" file is bilingual:

            <termEntry id="e2">
                <descrip type="definition">Údržba 3. úrovně řeší zdokumentované chyby a závady softwaru, který je součástí smlouvy o údržbě, a provádí další předem stanovené úkoly údržby. Na údržbě se podílejí specialisté ze všech oblastí.</descrip>
                <langSet xml:lang="en">
                    <tig>
                        <term id="e2-en">3rd level maintenance</term>
                    </tig>
                    <tig>
                        <term>3rd Level Maintenance</term>
                    </tig>
                </langSet>
                <langSet xml:lang="cs">
                    <tig>
                        <term id="e2-cs">údržba 3. úrovně</term>
                    </tig>
                </langSet>
            </termEntry>

This leads to having the definition (source string explanation) in Czech on the English entry.

The Czech entry looks okish but I would expect it also at "Translation explanation" instead of "Explanation".

Can you give me some hint on how the files must be created to get not the languages mixed up in the explanation?

Thanks
Stephan

Originally posted by @snoerenberg in #12795

[nijel]

The monolingual file is not parsed at all in bilingual setup.

If you want both, this should work:

<descrip type="definition">3rd level maintenance resolves documented errors and malfunctions in software which is part of the maintenance contract and perform additional pre-determined maintenance tasks. Specialists from all areas are involved.</descrip>
<note from="translator">Údržba 3. úrovně řeší zdokumentované chyby a závady softwaru, který je součástí smlouvy o údržbě, a provádí další předem stanovené úkoly údržby. Na údržbě se podílejí specialisté ze všech oblastí.</note>