Alide Folz

The easiest way to "adjust it" would be to use the Glossary Converter.

1. drop the TBX file into the Glossary Converter
2. convert to XTD and XML

Now you have the XDT.  So either create a new termbase in Trads Live or MultiTerm and then edit it as you see fit in there before you import any data into it.

Keep in mind that if you change the XDT you may not be able to import the associated XML anymore unless you edit the content as well to suit the new definition.

Perhaps it might be helpful if you explain what you are trying to achieve?  Is the problem just that you have a TBX that doesn't match the definition of your Trados Live termbase?  If this is the problem it might make more sense to convert the TBX to Excel and then change the structure to match the termbase you want to import into.  Then create a new XML export to import into Trados Live.  All of that can be done easily using the Glossary Converter.

Alide Folz

The easiest way to "adjust it" would be to use the Glossary Converter.

1. drop the TBX file into the Glossary Converter
2. convert to XTD and XML

Now you have the XDT.  So either create a new termbase in Trads Live or MultiTerm and then edit it as you see fit in there before you import any data into it.

Keep in mind that if you change the XDT you may not be able to import the associated XML anymore unless you edit the content as well to suit the new definition.

Perhaps it might be helpful if you explain what you are trying to achieve?  Is the problem just that you have a TBX that doesn't match the definition of your Trados Live termbase?  If this is the problem it might make more sense to convert the TBX to Excel and then change the structure to match the termbase you want to import into.  Then create a new XML export to import into Trados Live.  All of that can be done easily using the Glossary Converter.

Hallo,

so weit so gut. Das war verständlich. Da ich meine Daten aus TBX beabsichtige zu nutzen, habe ich nun folgende Frage: Wie kann ich das Feld "Definition" in "Kontext" unbenennen? Ist das in Multiterm möglich, ohne dass die Daten verloren gehen? Oder muss ich die XML-Datei in Notepad++ bearbeiten?

Wie gehe ich richtig vor?

Alide Folz

The easiest way is to create a new termbase in MultiTerm using the definition (xdt) file, but DO NOT import your data.  Then edit the definition in MultiTerm so the field is called whatever you prefer.

Once done you should be able to import your data to the new termbase.  Perhaps rename the field in the XML, or convert to Excel and rename the header containing the data for the field you want changed, and then convert the Excel to XML and import it.

Hört sich einfach an, der Automatisierungsprozess für Änderungen ist komplex. 

Alide Folz

Yes it is!  Once you start using a database it becomes harder to change the table names so it's probably better to always recreate.

Ich komme damit nicht klar:

Hier ist die aktuelle Felderliste aus TBLive

diese (meine Felder) soll wie folgt aussehen: 

Wie soll ich die obige XDT in die meinige umwandeln. Daten werden doch verloren gehen. 

Weniger Automatisierung und mehr an die Praxis der Übersetzer denken.

Was schlagen Sie vor?

Alide Folz

I guess you do this step by step.  I'd do this:

1. map the fields to see what's missing (this is my guess because I have no idea what you use these for, or what is in the data you have in Trados Live)
   
   Definition => Definition
   Image => Bild
   Usage Example => Kontext
   Gender => Genus
   Number => Boolescher Wert
   Note => Kommentar
   Forbidden Term => Status
   Subject => Subject
   
   So "Quelle" seems to be missing in Trados Live, and you seem to have 5 additional fields in Trados Live that you don't make use of yourself.
   
   
2. Next I'd export the Trados Live data to Excel and see which of the fields are populated with data.  If they are empty then I can ignore them, if they are not empty I need to decide whether I want to use the data or not.  If the data is interesting and I wanted to use it then I would have to add the fields into an export of my own termbase so that I have a new definition for my own.  If they are not interesting then I'd just delete and hopefully I would now have a mapping between the termbases of the data I wanted to retain.
   
   
3. Once I'd sorted that out I'd either create a new definition if I was adding fields to my own database and then recreate with data from Trados Live and also my own termbase; or I'd import the cleaned export from Trados Live into my own database.
   
   
4. Finally, I'd create a new termbase in Trados Live using an XDT created from my new termbase and import the XML data into it.

I hope this is clear enough for you.  I probably jumped some detail but hopefully wrote enough for you to understand?

Sehr komplexiert:

Manche Schritte konnte ich umgehen, ABER es gibt folgendes Problem: Meine geänderte XDT-Datei wird zwar eingelesen, aber nicht mit dem geänderten Feld.

Somit werden mir meine Definitionsrechte für eine neue Datenbank einfach weggewischt.

Und warum muss sich der Übersetzer mit solchen Fehler beschäftigen, wenn diese nicht von ihm kommen?

Warum wird in Trados Live mein Feld "Kontext" angezeigt aber nicht aufgenommen?

Alide Folz

Alide Folz said:

Manche Schritte konnte ich umgehen, ABER es gibt folgendes Problem: Meine geänderte XDT-Datei wird zwar eingelesen, aber nicht mit dem geänderten Feld.

Can you share how you changed the XDT?  Did you do this with notepad or did you do it in a controlled manner as I explained?

Alide Folz said:

Und warum muss sich der Übersetzer mit solchen Fehler beschäftigen, wenn diese nicht von ihm kommen?

It's hard to answer this question because the error might have come from you.  How do we know what you did?  Can you share the original XDT before the change, and then the xdt after the change so I can test it?

Could it be that the field "Kontext" is part of the termbase, but that it hasn't been assigned to a level? I am not that familiar with terminology management in Trados Live (I have been working with MultiTerm for more than thirty years), but it seems to me a disadvantage that you can't create your own custom export definitions (which could be perfect for partial export of entries to an xml file). But maybe I got things wrong when talking about Trados Live terminology management.