• State Suggested Answer
  • Replies 8 replies
  • Answers 2 answers
  • Subscribers 190 subscribers
  • Views 3163 views
  • Users 0 members are here
Options
Related

import into termbase with sublanguages

Stephen Waller

Hi, I'm trying to import data into a termbase with sublanguages (ES-ES>EN-US/EN-GB).

I uncheck the "Ignore sublanguages" checkbox, but the import fails with the error: "Does not conform to the target termbase definition. Reason: Source: <language type="ES" lang="ES-ES"></language>"

My termbase definition has 3 languages: English (United Kingdom), English (United States) and Spanish (Spain).

My import file has terms tagged either <language type="ES" lang="ES-ES" />, <language type="EN" lang="EN-US" /> or <language type="EN" lang="EN-GB" />. No entry has all three languages, they all have ES and either GB or US (is that the problem?).

If I leave the Ignore sublanguage box checked, the data imports but the sublanguages are not recognised (all EN are terms imported as EN-GB).

What am I doing wrong? Thank you!
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents Reply Children
  • 0 in reply to Paul

    Thank you for your reply, Paul. I'm sure you're right.

    I get the same error when I try to import your data into my termbase (my testfile is pretty much identical to yours, except for ES-ES as source).

    I'm attaching my empty termbase.

    I see there's a difference in the structure: yours consists of Entry / Index / Term level, whereas mine has Entry / Language / Term level.  I created the termbase in the Multiterm wizard, creating a definition from scratch.

    test_termbase.zip

    Fullscreen ES-EN_mini-test.mtf.xml Download 
    <?xml version="1.0" encoding="UTF-16"?>

<mtf>

<conceptGrp><languageGrp><language type="ES-ES" lang="ES-ES" /><termGrp><term>favor</term></termGrp></languageGrp><languageGrp><language type="EN-GB" lang="EN-GB" /><termGrp><term>favour</term></termGrp></languageGrp></conceptGrp>

<conceptGrp><languageGrp><language type="ES-ES" lang="ES-ES" /><termGrp><term>favor</term></termGrp></languageGrp><languageGrp><language type="EN-US" lang="EN-US" /><termGrp><term>favor</term></termGrp></languageGrp></conceptGrp>

<conceptGrp><languageGrp><language type="ES-ES" lang="ES-ES" /><termGrp><term>vecino</term></termGrp></languageGrp><languageGrp><language type="EN-GB" lang="EN-GB" /><termGrp><term>neighbour</term></termGrp></languageGrp></conceptGrp>

<conceptGrp><languageGrp><language type="ES-ES" lang="ES-ES" /><termGrp><term>vecino</term></termGrp></languageGrp><languageGrp><language type="EN-US" lang="EN-US" /><termGrp><term>neighbor</term></termGrp></languageGrp></conceptGrp></mtf>

  • 0 in reply to Stephen Waller

    Hi

    My guess is you have an encoding error here.  Try importing this one:

    sw.zip

    All I did was remove the declaration at the beginning and it imported correctly into your termbase.

    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

  • 0 in reply to Paul
    Again, thank you, Paul. It does seem to have to do with the encoding. The file you sent gave me the same "Does not conform to the target termbase definition" error, but when I resaved it, converting to UTF-16, I no longer got the error, although no data was imported. Kind of a step in the right direction, I suppose.
    Can you tell me where I can learn out about the encoding of the termbase? The Wizard seemed to output UTF-16 by default, although the original Excel file was imported from text as UTF-8. Or should I forget the Wizard and use the Glossary Converter?
    Thank you for your help!
  • 0 in reply to Paul
    I've just tested it and the Glossary Converter does produce the desired output, so clearly I should stick to the Converter. Thank you!
  • 0 in reply to Stephen Waller


    Yes, the Glossary Converter is a wonderful tool and it overcomes many of the technical difficulties and bugs that are inherent in MultiTerm.

    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

  • 0 in reply to Paul
    Just one last thing, although it's only half on-topic – it might help someone. If when converting an xml file using the Glossary Converter you get the error "hexadecimal value 0x0B is an invalid character", try scanning the xml file in a text editor for the characters &#xB; and deleting them.
  • 0 in reply to Paul
    Hi Paul,

    I have exactly the same problem, only with German instead of Spanish. I tried every option there is, but I get the same error messages as Stephen Waller. So what am I doing wrong here? I'm using MultiTerm 2019 under Windows 10.