Creating a MultiTerm termbase - List of available languages

Hi to all,

I have an unusual and “strange” request concerning creation of a MultiTerm termbase.

Suppose you have an Excel file like this one, where the first column contains a list of terms (no matter the language, in this example I used Italian AND English and the font Arial Unicode to see all extended characters):

Well, now I want to create a MultiTerm termbase to use when clients ask the International Phonetic Alphabet (IPA) phonetic transcription of terms.

Of course, I will be able to create a common MultiTerm file, defining the first column e.g. as English and the second one e.g. as Italian (or whatever other language pair I prefer) and the work is done:

Granted that MultiTerm doesn’t allow to create a termbase with a single language (e.g. English as source and target), now, my question is:

  • is it possible, when creating a new MultiTerm termbase, to foresee in the languages list a sort of “generic” source language (i.e. different from English, German, Italian, etc.) and a “customizable” or new target language (e.g. “International Phonetic Alphabet”)?

In fact, I’m not a programmer or a developer, and I do not know if this may be considered as an unfeasible and really “idealistic” solution.

Thank you.

Regards,

Claudio

  • Unknown said:
    Granted that MultiTerm doesn’t allow to create a termbase with a single language

    Hi Claudio,

    Actually MultiTerm does allow you to create a termbase with a single language:

    When I've seen this sort of thing done before, and the languages are mixed in a single index (as you have here), or even if the terminologist wants to use an index field for something other than a language then I have seen this sort of approach where a lesser used language is used.  You could rename the language with a custom value to say "Term" as I have done here.

    Regards

    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