• State Verified Answer
  • Replies 4 replies
  • Subscribers 191 subscribers
  • Views 1011 views
  • Users 0 members are here
Options
Related

Importing only some languages into an empty MultiTerm from a MTF-XML with many languages

Victor Linnemann

Hi there

I try to split a very large termbase with many languages in it into smaller ones containing only a few languages:

Firts, modified the term definition of an existing, empty termbase by deleting all indexes/languages not needed and then  imported the xml.

I found out that MT only imports the full number of entries containing terms in the selected languages if I choose the option "Allow over-complete entries" (as Anna had observed as well).

But if I do so MT will import all languages and terms contained in the XML  It seems that MT can only import and filter on the entry level.

The desired result would be a termbase containing exactly the full number of terms in the selected languages. 

As a first solution I use an XSL transformation on the XML to get rid of the unwanted languageGrp elements.

Is there a simpler solution to the desired result by using MT Desktop without having to manipulate the XML before importing it?

PS: Using the Glossary Converter (which is a very good tool and would do the job exactly in the way I want it) is not an option in my case. 

Thank you for your help.

WIth kind regards

Victor
emoji
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • +1

     

    I think, if you can't use the Glossary Converter which is definitely the preferred and most reliable method, then you may be able to do this by exporting the MultiTerm XML for the languages you need from MultiTerm.  Then you only have what you need from the start.

    Otherwise, if you need to do a lot of this stuff and don't have access to the Glossary Converter, then perhaps look at tools like Excelling MultiTerm from Kaleidoscope:

    https://appstore.rws.com/Plugin/185

    It may not be the process you want to use but it could be more reliable than manipulating the XML.  There are challenges associated with file manipulation using MultiTerm and MultiTerm Convert, so I would always recommend alternative methods to ensure a smoother user experience.

    Why can't you use the Glossary Converter?

    Paul Filkin | RWS Group

    ________________________
    Design your own training!
    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

    emoji
Reply
  • +1

     

    I think, if you can't use the Glossary Converter which is definitely the preferred and most reliable method, then you may be able to do this by exporting the MultiTerm XML for the languages you need from MultiTerm.  Then you only have what you need from the start.

    Otherwise, if you need to do a lot of this stuff and don't have access to the Glossary Converter, then perhaps look at tools like Excelling MultiTerm from Kaleidoscope:

    https://appstore.rws.com/Plugin/185

    It may not be the process you want to use but it could be more reliable than manipulating the XML.  There are challenges associated with file manipulation using MultiTerm and MultiTerm Convert, so I would always recommend alternative methods to ensure a smoother user experience.

    Why can't you use the Glossary Converter?

    Paul Filkin | RWS Group

    ________________________
    Design your own training!
    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

    emoji
Children