Correct recognition of languages during import of XML

Question

I try to import Glossary from Excell with 30 langugages. First I convert the Excell-File with Multiterm 2022 Convert to an Multiterm XML File, then I try to import in Multitermbase. All languages are imported correct, only the languages Bosnian, Croatian and Serbian are imported to one of them with 3 entries. I want to have the terms in TDB with correct languages, but I didn´t find the way, how to do it.

Screenshot showing language entries for Czech, Bosnian (Latin, Bosnia and Herzegovina), and Bulgarian with the term 'Terminus Hinzufugen' and a placeholder '%s mesic' for Czech and three '%s mesec' entries for Bosnian. Screenshot of a language selection list including Bosnian (Latin, Bosnia and Herzegovina), Bulgarian, Croatian (Croatia), Czech, and other languages in alphabetical order. Close-up screenshot of a language code list showing SH-B2 for Bosnian (Latin, Bosnia and Herzegovina), SH-HR for Croatian (Croatia), and SH-LATN-RS for Serbian (Latin, Serbia).

Generated Image Alt-Text
[edited by: RWS Community AI at 1:22 PM (GMT 1) on 23 May 2024]

Eugen Drgoň · Accepted Answer

Hi Paul, 
 thanks for advice, with Glossary Converter it&acute;s ok, I create local termbase, the language recognition is correct. 
 Then I create an termbase on server, with the same definition and try in Multiterm to export the local termbase to xml and then import in server termbase, and the language recognition was incorrect and the items from hr-HR and sr-Latn-RS are merge under bs-Latn-BA. 
 I want continuously update the local termbase and then in an easy way - export-import - periodically update the server termbase, but this way in Multiterm is therefore impassable :-(

Paul · Answer

Eugen Drgoň 
 It sounds as though you need to map them to the appropriate sub-languages as opposed to simply mapping to Bosnian. So always show the fields in the UI settings so you get the list of languages when you convert. Then you can set the specific variants you want:

Paul · Answer

Eugen Drgoň 
 I see what you mean. I misread your original post and actually showed you a screenshot from the Glossary Converter, So I just tested with MultiTerm Convert and see your problem now. I checked and this is already a logged bug under our reference CRQ-30837 (you can't access that but it's helpful for following up if I note it here). 
 I then tested with the Glossary Converter and this handles things correctly, so I believe the developer has most likely fixed this issue in the code for the Glossary Converter. See video:

Trados Studio > 4. MultiTerm

Correct recognition of languages during import of XML

Top Replies