Exporting Multiterm 7 termbases to DVX... Thread poster: Grzegorz Gryc
|
|---|
Hi
We often complain Multiterm is a one way ticket solution.
Although I translate mainly in DVX and feed my MT termbases after the translation is done, I imagine some of us receive MT glossaries and experience a lot of problems trying to import them to DVX as the default MT export filters are a piece of shit and the creation of personalized export filters in MT is a pain in the neck.
Take a look on my posts... See more Hi
We often complain Multiterm is a one way ticket solution.
Although I translate mainly in DVX and feed my MT termbases after the translation is done, I imagine some of us receive MT glossaries and experience a lot of problems trying to import them to DVX as the default MT export filters are a piece of shit and the creation of personalized export filters in MT is a pain in the neck.
Take a look on my posts on:
http://www.proz.com/forum/sdl_trados_support/116611-multiterm_workbench_dont_recognize_terms-page2.html
Enjoy
Cheers
GG ▲ Collapse
| | | | Spiros Doikas 
Local time: 02:09
Member (2002)
English to Greek
+ ...
| This would not be a problem... | Oct 12, 2008 |
If MT7 provided a csv export option...
But I still believe that creating an application/macro etc that would convert a typical MT7 xml file to csv would not be that difficult. So, you can suggest that at http://ideas.sdltrados.com/
| | | | Grzegorz Gryc
Local time: 01:09
French to Polish
+ ...
TOPIC STARTER | Hell will freeze... | Oct 12, 2008 |
Spiros Doikas wrote:
If MT7 provided a csv export option...
Indeed, MT 7.5 provides a csv option (Tab delimited) but it's completely unusable.
Just try to export and import the Sample termbase provided with MT.
LOL.
I don't know they're kidding or they're so stupid.
But I still believe that creating an application/macro etc that would convert a typical MT7 xml file to csv would not be that difficult. So, you can suggest that at http://ideas.sdltrados.com/
Hell will freeze before SDL provides a decent CSV export.
As you can see, a simple feature like "go back to the previous segment" waits 450+ days to be developped in SDL... I did it in 5 minutes for Word...
The CSV export case is worse 'cause it encourages the CAT hopping.
PS.
I'm too stupid (and too lazy) to develop this kind of converter.
But the Across conversion works as a charm.
At least for small files I tested.
And, in fact, Across still seems to be a free tool but the page is rather difficult to find
http://www.my-across.net/en/fdb_intro.aspx
Cheers
GG
| | | | Spiros Doikas
Local time: 02:09
Member (2002)
English to Greek
+ ...
Going back to the previous segment is such a basic thing... Which macro do you use? In Trados 8 and Word 2003 I cannot get Yves macro to work (http://www.proz.com/howto/61)
Yes, you have a point. A decent csv functionality would encourage CAT hopping.
Edit: just tried the export option to a tab delimited file and it seems to work just fine to me (MT 7.5.0.444):
1 spiro... See more Going back to the previous segment is such a basic thing... Which macro do you use? In Trados 8 and Word 2003 I cannot get Yves macro to work (http://www.proz.com/howto/61)
Yes, you have a point. A decent csv functionality would encourage CAT hopping.
Edit: just tried the export option to a tab delimited file and it seems to work just fine to me (MT 7.5.0.444):
1 spiros 2008-05-06T21:25:52 spiros 2008-05-06T21:25:52 Afghanistan Αφγανιστάν
2 spiros 2008-05-06T21:25:52 spiros 2008-05-06T21:25:52 Albania Αλβανία
You can even paste it in excel, keep only source and target columns, and easily import to DVX.
[Edited at 2008-10-12 19:35]
[Edited at 2008-10-12 19:35] ▲ Collapse
| | |
|
|
|
Grzegorz Gryc
Local time: 01:09
French to Polish
+ ...
TOPIC STARTER | Spiros Doikas
Local time: 02:09
Member (2002)
English to Greek
+ ...
| Macro did not work | Oct 12, 2008 |
Tried that too, does not work either. Which Trados version you use?
So why we'll never get a correct CSV/TBX export in Trados.
Tab delimited is a type of csv format and it works perfectly fine for your purposes, following the procedure I described. No need to download a 0.6 GB application for such a simple operation!
[Edited at 2008-10-12 20:37]
| | | | Grzegorz Gryc
Local time: 01:09
French to Polish
+ ...
TOPIC STARTER | Shame on Trados programmers... | Oct 12, 2008 |
Spiros Doikas wrote: Tried that too, does not work either. Which Trados version you use?
2007 SP2 fully patched + Word 2003.
Your macro security settings are set to medium or low?
You have an open TU?
It'a a prerequisite for my macro.
So why we'll never get a correct CSV/TBX export in Trados.
Tab delimited is a type of csv format and it works perfectly fine for your purposes, following the procedure I described.
You're wrong
You have a simple, bilingual 1:1 termbase, no comments, no definitions, no examples etc.
In this case, it works.
As I said, try it with the "Sample" termbase provided with Trados.
E.g. when you have a EN-PL-EL termbase with entries:
Afghanistan-Afganistan-Αφγανιστάν
Albania-empty-Αλβανία
you'll have the CSV output:
Afghanistan[tab]Afganistan[tab]Αφγανιστάν
Albania[tab]Αλβανία
More empty fields you have, more mess you get.
Sorry, it's a shame.
I can't believe a database programmer can be so stupid.
In this case, if the stupidity could be like helium, the MT development team would fly over Stuttgart like little Zeppelins.
I'm sure the output was never tested thoroughly (just like a lot of MT features) or was messed up intentionally.
All the MT export filters are unusable for complex data.
Except the proprietary XML, of course.
No need to download a 0.6 GB application for such a simple operation!
It'a damn good converter
Trust me
It seems too slow as a CAT but the data handling seems really good.
PS.
When DVX goes SQL, we'll have too 0,5-0,6 GB to download
Or 0,3-0,4 GB if Atril chooses Oracle instead of MS.
Cheers
GG
[Edited at 2008-10-12 23:02]
| | | | Spiros Doikas
Local time: 02:09
Member (2002)
English to Greek
+ ...
| The macro... | Oct 13, 2008 |
Opens the next segment! (Of course I had an open segment when I tried).
I had medium secutiry, tried with low. Same result.
As far as empty fields in multiple language export with comments, I think this can be easily sorted too by deleting extra columns. In most cases, translators have a source-target glossary, in which case, it is fine.
As far as DVX going big, I only wish it did not have to produce such huge projects, many times the size of the files it c... See more Opens the next segment! (Of course I had an open segment when I tried).
I had medium secutiry, tried with low. Same result.
As far as empty fields in multiple language export with comments, I think this can be easily sorted too by deleting extra columns. In most cases, translators have a source-target glossary, in which case, it is fine.
As far as DVX going big, I only wish it did not have to produce such huge projects, many times the size of the files it consists of. ▲ Collapse
| | |
|
|
|
Grzegorz Gryc
Local time: 01:09
French to Polish
+ ...
TOPIC STARTER | Macro, MT export, TTX-DVX-TTX workflow... | Oct 13, 2008 |
Spiros Doikas wrote:
Opens the next segment! (Of course I had an open segment when I tried).
I had medium secutiry, tried with low. Same result.
Try to assign another shortcut.
As far as empty fields in multiple language export with comments, I think this can be easily sorted too by deleting extra columns.
No
Let's take a look on your example.
In MT, you have EN-PL-EL:
Afghanistan-Afganistan-Αφγανιστάν
Albania-empty-Αλβανία
The CSV output is:
Afghanistan[tab]Afganistan[tab]Αφγανιστάν
Albania[tab]Αλβανία
In this case Αλβανία is interpreted as POLISH, not Greek.
Excel (or similar) expects:
Albania[tab][tab]Αλβανία
If you delete the PL column, Αλβανία si deleted and the Greek field is empty.
So, e.g, when you have columns like EN (term), EN (abbrev), EN (def), EN (example) etc. and some of these fields are empty, you may have PL (term) instead of EN (def).
It's completely unpredictable.
If you have a small export, you can fix it manually and add the missing tabs.
Imagine a 7 language glossary with 1000 entries with comments, definitions etc. and a lot of empty fields.
This export filter is a crap.
In most cases, translators have a source-target glossary, in which case, it is fine.
I work in a multilingual environment
When you have a localization project for 5-10-15 languages, this kind of conversions must work out of the box.
As far as DVX going big, I only wish it did not have to produce such huge projects, many times the size of the files it consists of.
As you have Trados, use the TTX-DVX-TTX workflow.
All the images, embedded objects etc. are not imported to the DVX project.
Cheers
GG
| | | | To report site rules violations or get help, contact a site moderator: You can also contact site staff by submitting a support request » Exporting Multiterm 7 termbases to DVX... | 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 » |
| | Wordfast Pro | Translation Memory Software for Any Platform
Exclusive discount for ProZ.com users!
Save over 13% when purchasing Wordfast Pro through ProZ.com. Wordfast is the world's #1 provider of platform-independent Translation Memory software. Consistently ranked the most user-friendly and highest value
Buy now! » |
|
| | | | X Sign in to your ProZ.com account... | | | | | |
Login to reply/comment 
