You are currently working on UAT 

Editing TB entries in Studio 2019 still doesn't work!

Hi,

One of the main reasons to buy me a new PC was that working with Trados was extremely slow and inefficient.

One of my problems was that when I tried to edit a TB entry in Studio by right-clicking I had the following phenomenon:

1) I do right click on the term I want to edit, then the window "Termbase Viewer" opens, with the text: "Loading termbases...". In this window, I see a rotating circle for about one minute, meanwhile Studio is frozen and I can't do anything, not even close this pop-up window.

2) After having passed one minute (sometimes even longer), the rotating circle disappears but the Termbase Viewer window remains empty.

3) I close this window, close the file being edited and re-open the file to edit.

4) I do the same as in point 1), but now the term list is being populated and I can edit the terms in "Default Layout". I close the little window where I edited the term hitting Enter or clicking on the checkmark and close the window "Termbase Viewer".

 

Now I have a BRANDNEW PC, a NEW OS (Win10), a NEW version of Studio (2019) - BUT THE OLD PROBLEMS!!!

Until the above point #3) everything is the same, only that in point 4) the following happens:

4) I make a right-click on the term to edit, the window "Termbase Viewer" opens, I edit the term in Default Layout and hit Enter.

5) I close the window "Termbase Viewer" but the edited term in the window "Term recognition" hasn't changed, it's still the un-edited version.

6) I close the file being edited again and re-open it, do right click on the term to edit and in the window "Termbase Viewer" there's still the version that I had edited before but in the window "Term recognition" there's still the un-edited version! THUS, IT'S WORSE THAN WITH 2017!

 

I DO have Studio and Multiterm up to date and my PC has almost nothing installed but Bitdefender, Chrome browser, Office 2019 and Trados.

 

WILL SDL EVER FIX THIS????

 

I had noticed a deterioration from Studio 2014 to 2017 in terms of speed and stability and it seems with 2019 it continues to worsen its versions...

 

A very desperate

Markus

 

 

Parents Reply
  • Hi  

    If this is only happening with just the one termbase then it's very possible that it's that termbase that is causing the problem.

    To find this out, export the termbase and reimport it.

    The Glossary Converter app is an easy way to export and import termbases and that process can be used to smooth out any corruptions:

    Glossary Converter

    It's very good at converting termbases to Excel. You can check visually for errors in Excel then convert back to .sdltb termbase format, at which point an error message may flag up anything that isn't as it should be. Then you can look it up in the error log and pinpoint where it is, correct it and convert the termbase again...

    To know how to use the Glossary Converter, click on 'Learn how to use this app' on the above page ...

    Screenshot of Glossary Converter app description highlighting its ability to convert between MultiTerm Termbases and other terminology formats with minimal user interaction.

    I hope this helps!

    All the best,

    Alison

    emoji


    Generated Image Alt-Text
    [edited by: Trados AI at 3:45 PM (GMT 0) on 28 Feb 2024]
Children