Quick entry - MultiTerm Initiator des Themas: Marcos Zattar
|
|---|
Marcos Zattar
Deutschland
Local time: 06:52
Mitglied (2007)
Deutsch > Portugiesisch
+ ...
Hello,
I have a MultiTerm databank with 3 languages: English, German and Portuguese. The terms exist in English and German and my task is to enter the translations in Portuguese.
Is there a way (preferably with keyboard shortcuts) to open the corresponding field for Portuguese as I go through the list of terms?
My procedure until now:
1. Alt+down arrow: to go to the next entry in the list
2. F2: to open the entry for editing
3. Doub... See more Hello,
I have a MultiTerm databank with 3 languages: English, German and Portuguese. The terms exist in English and German and my task is to enter the translations in Portuguese.
Is there a way (preferably with keyboard shortcuts) to open the corresponding field for Portuguese as I go through the list of terms?
My procedure until now:
1. Alt+down arrow: to go to the next entry in the list
2. F2: to open the entry for editing
3. Double click on the Portuguese field
What I wanted to avoid is step 3. Ideally I would use a keyboard shortcut that it would allow to open the field directly for entry.
I use MultiTerm 2009, version 8.
Thanks! ▲ Collapse
| | | | pcovs
Dänemark
Local time: 06:52
Englisch > Dänisch
Marcos Zattar wrote:
Hello,
I have a MultiTerm databank with 3 languages: English, German and Portuguese. The terms exist in English and German and my task is to enter the translations in Portuguese.
Is there a way (preferably with keyboard shortcuts) to open the corresponding field for Portuguese as I go through the list of terms?
My procedure until now:
1. Alt+down arrow: to go to the next entry in the list
2. F2: to open the entry for editing
3. Double click on the Portuguese field
What I wanted to avoid is step 3. Ideally I would use a keyboard shortcut that it would allow to open the field directly for entry.
I use MultiTerm 2009, version 8.
Thanks!
| | | | Marcos Zattar
Deutschland
Local time: 06:52
Mitglied (2007)
Deutsch > Portugiesisch
+ ...
THEMENSTARTER | Does not work | Jul 3, 2010 |
Tab does not work.
| | | | | Why in Multiterm? | Jul 3, 2010 |
If this is a large job, you may be better off doing it in some other environment.
At the very least, you can export the termbase to XML and do the translation in that. I'm not sure the tags for each Portuguese entry will be there... Probably not, I guess.
If this was my job, I'd probably export to XML, insert the Portuguese tags with search and replace and work in the XML. You could try tageditor (mark everything except Portuguese untranslatable) or some manual method.
<... See more If this is a large job, you may be better off doing it in some other environment.
At the very least, you can export the termbase to XML and do the translation in that. I'm not sure the tags for each Portuguese entry will be there... Probably not, I guess.
If this was my job, I'd probably export to XML, insert the Portuguese tags with search and replace and work in the XML. You could try tageditor (mark everything except Portuguese untranslatable) or some manual method.
If you're so inclined, you could also try converting the termbase to a tab separated file (which is what the client should have given you in the first place). Then you can just insert your terms in Excel and import to MT when you're done, which is obviously the best, most convenient way to do it. Write term, hit enter, write next term, hit enter... no fooling around with mouse clicks and all that rubbish. Also a lot easier to review, you can see any accidentally missed terms right away, you have spell check at your disposal etc.
Of course this is easiest to do if the termbase is simple. If all the entries contain both En and De terms and there are no other fields, Multiterm's own tab delimited export option should work.
If the built-in export option fails (which it will if there are missing entires in any language), you can use my MultiTerm XML to tab separated converter: https://sourceforge.net/projects/aligner/files/MT_XML_converter_1.2.zip/download
If you decide to edit the XML, use a tab delimited export (either direct or converted from XML), the terms you've already done will be in there so you can continue from where you left off. ▲ Collapse
| | |
|
|
|
If you're going for the tab delimited option, keep an eye on everything. No solution is foolproof, especially not MultiTerm's own export.
Say, it puts the English terms in the first column and German in the second.
If one entry has no English term, then the German will be shifted over to the first and whatever should have been in the third column will be moved to the second etc. Horrible, I know.
If the termbase has no fields other than the 3 languages, my script should ... See more If you're going for the tab delimited option, keep an eye on everything. No solution is foolproof, especially not MultiTerm's own export.
Say, it puts the English terms in the first column and German in the second.
If one entry has no English term, then the German will be shifted over to the first and whatever should have been in the third column will be moved to the second etc. Horrible, I know.
If the termbase has no fields other than the 3 languages, my script should be fine (it should also be fine if there are, but that could possibly complicate things). In any case, do check the number of entries in the output and make sure everything's kosher.
Synonyms will require a bit of attention, too.
Ask here if you have some trouble. ▲ Collapse
| | | | Marcos Zattar
Deutschland
Local time: 06:52
Mitglied (2007)
Deutsch > Portugiesisch
+ ...
THEMENSTARTER
Hello Farkas,
you've got a point: if the databank structure is simple, then it can be processed elsewhere. It is the first time I am using MultiTerm, though. I wanted to learn as much of it as possible and thought that it would be suitable for my needs.
Why MultiTerm? Well, I extracted the terms from a TMX using Term Extractor - the next natural step would be to export it to MultiTerm, right?
The translation job is big, but the terms themselves are not so many, ar... See more Hello Farkas,
you've got a point: if the databank structure is simple, then it can be processed elsewhere. It is the first time I am using MultiTerm, though. I wanted to learn as much of it as possible and thought that it would be suitable for my needs.
Why MultiTerm? Well, I extracted the terms from a TMX using Term Extractor - the next natural step would be to export it to MultiTerm, right?
The translation job is big, but the terms themselves are not so many, around 400.
I am going to process the file in MemoQ, my favorite tool. I thought its term bank functionality could import MultiTerm easily and fully, that is also a reason why I chose MultiTerm. But then after the work was already in progress I noticed that MemoQ cannot import the MultiTerm format natively, it needs workarounds.
BTW, the terminology I will insert in Promt, with which I will pretranslate the file and import the rough translation to the TM. ▲ Collapse
| | | |
Marcos Zattar wrote:
Hello Farkas,
you've got a point: if the databank structure is simple, then it can be processed elsewhere. It is the first time I am using MultiTerm, though. I wanted to learn as much of it as possible and thought that it would be suitable for my needs.
Why MultiTerm? Well, I extracted the terms from a TMX using Term Extractor - the next natural step would be to export it to MultiTerm, right?
The translation job is big, but the terms themselves are not so many, around 400.
I am going to process the file in MemoQ, my favorite tool. I thought its term bank functionality could import MultiTerm easily and fully, that is also a reason why I chose MultiTerm. But then after the work was already in progress I noticed that MemoQ cannot import the MultiTerm format natively, it needs workarounds.
BTW, the terminology I will insert in Promt, with which I will pretranslate the file and import the rough translation to the TM.
That's one complicated workflow.
So you're essentially just creating a glossary for a project you'll do in memoq? Whatever format the term extractor gave you should be some sort of spreadsheet... I would insert the new terms in that and then import to memoq. All Multiterm does here is complicate your life... It's a good tool if you're translating with Trados, it's also pretty useful for terminology research (fuzzy search in many termbases at once) but it's pretty bad for compiling a termbase.
| | | | To report site rules violations or get help, contact a site moderator: You can also contact site staff by submitting a support request » Quick entry - MultiTerm | Trados Studio 2022 Freelance | The leading translation software used by over 270,000 translators.
Designed with your feedback in mind, Trados Studio 2022 delivers an unrivalled, powerful desktop
and cloud solution, empowering you to work in the most efficient and cost-effective way.
More info » |
| | Anycount & Translation Office 3000 | Translation Office 3000
Translation Office 3000 is an advanced accounting tool for freelance translators and small agencies. TO3000 easily and seamlessly integrates with the business life of professional freelance translators.
More info » |
|
| | | | X Sign in to your ProZ.com account... | | | | | |
Login to reply/comment 
Translation news related to SDL Trados
