Hi Almudena,

Don't let that stop you using the Glossary Converter.  It can create your definition files too!  However, let's look at MultiTerm Convert.  Can you share a small sample spreadsheet with just a dozen lines perhaps?  Makes it easier to provide a better answer if we're working with the same starting point as you.

You can put the spreadsheet in here if you like (instructions are in this article).

sample-language_variants.xlsx

Hi Paul,

I'll try with Glossary Converter indeed... Anyway I'm attaching a sample of my spreadsheet. Some languages are empty but problematic ones have some examples for you to test.

Many thanks in advance!

Almudena

Hi Almudena,

I have done this using the Glossary Converter (just like this tool better), but had to structure your spreadsheet a little differently to achieve it.  So I get this now for example:

I have attached the spreadsheet I used and the converted termbase.  maybe this will help you as you could also use the termbase to edit the definition to suit what you really wanted and then base your proper termbase on that.

gc_no_picklists.xlsx

https://community.rws.com/cfs-file/__key/communityserver-discussions-components-files/91/gc_5F00_no_5F00_picklists.sdltb

Hope this helps... also hope it's right!!

Regards

Paul

Hi Paul,

Many thanks for this solution. I see that you only leave one cell for each language whereas I keep three: a cell for main term, a cell for a synonym and another cell for a special form of term, which I also categorise with a field (cat).

I know that your option, all terms in one cell separated through "|" is an easier way but I like to keep translations separate so I can add info for each translation variant. For example, it is a forbidden translation, it is an acronym, it is preferred... If I don't do this way, my cat field goes under an (unique) term level and categorises terms wrongly like here:

It should read under term form DELE. I do this to warn my translators in case a special project or document doesn't allow a particular translation, etc.

Also I'd like to show language names in .sdltb with full original name and not with those codes I use in excel for practical reasons...

So, what about Multiterm Convert? Is there really a bug with language variants or am I doing something wrong...? I will give a try to Glossary Converter and re-build my termbase the way you did, but I'd really like to know if I need to discard my old method if termbase involves language variants.

Many thanks again,

Almudena

Hi Almudena,

It's starting to look like a bug to me too... so I have asked the team to take a look in case I'm doing something silly.  I can get the structure you want in MultiTerm using the Glossary Converter but only if I fill all the spreadsheet so there are no gaps (that's the bug that needs fixing).  So at least I was able to try two ways of doing it to make sure I understood what you wanted.

I attach them both here just for interest, but will respond again after the team have had a look... how I love working with MultiTerm Convert ;-)

https://community.rws.com/cfs-file/__key/communityserver-discussions-components-files/91/gc_5F00_no_5F00_picklists_5F00_full.sdltb

https://community.rws.com/cfs-file/__key/communityserver-discussions-components-files/91/gc_5F00_picklists.sdltb

I don't think either of these will help you right now but you never know.

Regards

Paul

Hi Almudena,

ok the only bug here is in my head!  At least as far as MT Convert goes.,.. was a good exercise to find the problem with the Glossary Converter!!

What you have to do is make sure you uncheck the option to ignore sublanguages in the import definition.  Obvious really!!  So the advice I had, that works for me was this:

1. Make a copy of the default definition
2. Edit it to ensure this is unchecked:
   
3. Save it, activate it and process the import

When I do this I get exactly what you need.

Hope this helps and many apologies for my messing around... I'm not sure who's teaching who here!!!

Regards

Paul 

Hi Almudena,

ok the only bug here is in my head!  At least as far as MT Convert goes.,.. was a good exercise to find the problem with the Glossary Converter!!

What you have to do is make sure you uncheck the option to ignore sublanguages in the import definition.  Obvious really!!  So the advice I had, that works for me was this:

1. Make a copy of the default definition
2. Edit it to ensure this is unchecked:
   
3. Save it, activate it and process the import

When I do this I get exactly what you need.

Hope this helps and many apologies for my messing around... I'm not sure who's teaching who here!!!

Regards

Paul