Tanja Hampf

They are possible.  I hadn't done this before but I just tested creating in Excel, converting to MultiTerm and back again using the Glossary Converter from the appstore. The breaks were maintained throughout.

I also tried merging two termbases, each with line breaks in every term, and this also worked successfully using the Glossary Converter.

So maybe it's worth giving this a go?

appstore.sdl.com/.../

Thank you for tesing! Did you use the same key combination I did, i.e. shift + return?

I used the same process: From Excel via the Glossary Converter into MultiTerm.

I just checked the first termbase again and noticed that the line breaks were already gone before the entries were exported for mgration to the new termbase .... That's strange. So, I can't really tell for sure at what point they were lost and why. Too bad!

Tanja Hampf

I used Alt+Return in Excel as Shift+Return doesn't do this for me in Excel.

I didn't test the process I think you are going through... 

1. add terms in MultiTerm with the Shift+Return
2. export to Excel
3. then import into new termbase

I'll test that if this is what you did, but why not try this:

1. select both SDLTB files
2. merge them in the Glossary Converter

No need to go to Excel first.

Actually, it's the other way round. I receive the terms in an Excel list, convert this to an XML file using MultiTerm Convert (sorry, not the Glossary Converter as I said before, always mix the two up!!) ... and beam them up to MultiTerm.

Migrating the terms from one termbase to the other was necessary only once when I had to change the general set-up.

So, once I have restored all of linebreaks (manually, grrr) in the current termbase, I'll keep a very watchful eye on the linebreak issue when importing data next time. And next time it happens I'll be able to tell you how and when, if you're interested? 

Thank you & have a good week-end!

Actually, it's the other way round. I receive the terms in an Excel list, convert this to an XML file using MultiTerm Convert (sorry, not the Glossary Converter as I said before, always mix the two up!!) ... and beam them up to MultiTerm.

Migrating the terms from one termbase to the other was necessary only once when I had to change the general set-up.

So, once I have restored all of linebreaks (manually, grrr) in the current termbase, I'll keep a very watchful eye on the linebreak issue when importing data next time. And next time it happens I'll be able to tell you how and when, if you're interested? 

Thank you & have a good week-end!

Tanja Hampf

Thank you... so maybe try it this way. 

First I have my termbase... looks like this:

I export it to Excel (Glossary Converter) and then add a few more entries. So I have what you might get with new entries and maybe even some duplicates:

Now I just convert the spreadsheet into a termbase (drag and drop the Excel into the Glossary Converter) to create a new one and then set up to use these settings:

Now I have this in the front page:

Next I select the two SDLTB files together and drag them into the interface.  I get prompted twice with this same screen (yours may be different, but expect two prompts):

Then I'm asked which field I want to synchronise on:

That's it.  Now I have a new termbase that looks like this:

I do think I should be able to merge the Excel and the SDLTB which would save an operation, but this seems to cause duplicates for me and I can't find a way to prevent this Gerhard Kordmann

But working like this with SDLTB files and the Glossary Converter does seem to do the trick.  Give it a try.

I'll give it a go later on today to insert the line breaks again and remove the duplicates in excel. Is there any way to drag and drop server-based termbases on the Glossary converter start screen?

Tanja Hampf

Tanja Hampf said:

Is there any way to drag and drop server-based termbases on the Glossary converter start screen?

No.  You'd need to download and convert to a local file-based format first.

The duplicates are caused by different ways of handling line breaks in different formats (\n or \r\n) This might affect other formats, but for now, the very latest beta (6.0.7535.21007) should fix it for spreadsheets. http://www.cerebus.de/glossaryconverter/beta 

Gerhard Kordmann

Nice!  Both issues we reported over the weekend are resolved in this Beta.:

1. merging Excel and SDLTB as they are and where the entries contain line breaks

2. the SDLTM conversion is back

Thanks Gerhard.

Sorry, I have to admit that I don't really get it.

So, there's no way I could add new terms (containing line breaks) from Excel to MultiTerm without killing the line breaks or producing duplicates unless I merge the Excel and the termbase contents in the Glossary Converter, correct?   

Tanja Hampf

Tanja Hampf said:

So, there's no way I could add new terms (containing line breaks) from Excel to MultiTerm without killing the line breaks or producing duplicates unless I merge the Excel and the termbase contents in the Glossary Converter, correct?   

Incorrect :-)

This is probably a process many users are not aware of in this brilliant application, so maybe this will help.

Thank you for the video, that was really helpful - I think I've got it now. .... But I'm still not sure whether I could use this process for my own purposes?

I could export my server-based termbase to xml format and open the xml export file in Excel, where I would add all the new terms. So far, so good. But how could I merge the contents from my server-based termbase with the Excel file then?

 By exporting the data from my server-based master termbase to a local termbase first (i. e. making a true local copy of my termbase each time)? That would be quite an effort. And even if I did that, at the end of the merging process I would have a completely new and local termbase ... which would not work in my case.

In our case, all the data would need to be in my master server-based termbase again at the end of the day unless I want to reconfigure the whole set-up every time, i. e. create the users, define their roles etc.  There will be other users accessing it too, you see?

Can you think of any alternative maybe?