Track this topic | Пользователь | Автор темы: Grzegorz Gryc Multiterm 2009 and TBX import | Grzegorz Gryc Польша Local time: 16:03
Член ProZ.com c 2005 французский => польский + ... | | Laurent KRAULAND Франция Local time: 16:03
Член ProZ.com c 2007 немецкий => французский + ... |
Grzegorz Gryc wrote:
I have a set of TBX files exported from Idiom Worldserver 9 (a SDL brand now), MT Convert stops because it can't find the DTD file (TBXcdv04.dtd).
It's rather easy to find this standard file (e.g. it's provided with Swordfish) and continue but I don't understand why the Multiterm team is unable to include the basic TBX related files in their distro while Rodolfo does it easily in Swordfish.
|
|
Want to know my best guess, Grzegorz?
No offence to the SDL developers teams here (I'd just love to run a SDL product which would work in the same fashion as e.g. Swordfish/Heartsome)...
There it is: because SDL Trados have not developed their .SDLTBX format, which would be compatible with standard .TBX? (This being said because Studio uses .sdlxliff instead of the standard, open-source .XLF format).
[Edited at 2009-11-04 21:16 GMT] | | | | Grzegorz Gryc Польша Local time: 16:03
Член ProZ.com c 2005 французский => польский + ... Автор темы | | Total cost of bug ownership... | Nov 7 |
Laurent KRAULAND wrote:
Grzegorz Gryc wrote:
I have a set of TBX files exported from Idiom Worldserver 9 (a SDL brand now), MT Convert stops because it can't find the DTD file (TBXcdv04.dtd).
It's rather easy to find this standard file (e.g. it's provided with Swordfish) and continue but I don't understand why the Multiterm team is unable to include the basic TBX related files in their distro while Rodolfo does it easily in Swordfish. |
|
Want to know my best guess, Grzegorz?
No offence to the SDL developers teams here (I'd just love to run a SDL product which would work in the same fashion as e.g. Swordfish/Heartsome)...
There it is: because SDL Trados have not developed their .SDLTBX format, which would be compatible with standard .TBX? (This being said because Studio uses .sdlxliff instead of the standard, open-source .XLF format). |
|
IMHO you're right.
And probably their current internal data structures were not designed correctly and the entire software should be rewritten.
E.g., you have a similar problem with CSV, Multiterm is simply unable to produce correct CSV files by default if your termbase is not a simple 1:1 term list.
According to all the Time-to-Market related books, it's cheaper to maintain this bug than to make the software work well.
It's a pity because it's one of few terminology management tools which theoretically meets my expectations but I simply can't use it because of it's unreliable import/export filters which are crucial for me.
BTW.
Try to convert a 1000000 (one million) software string list from MT5 to MT7.
Hell will freeze.
In MT, I killed the conversion after 5 days.
DVX does in one night, AFAIR.
Cheers
GG
[Edited at 2009-11-08 10:18 GMT] | | | | Laurent KRAULAND Франция Local time: 16:03
Член ProZ.com c 2007 немецкий => французский + ... | | Curiosity killed the CAT... | Nov 7 |
but while we speak about basic / open-source formats, have you ever tried importing an .sdlxliff file to Heartsome or Swordfish? I am curious to know whether this would work smoothly... As per the .csv files, I am now warned and will not do any attempt in that direction .
[Edited at 2009-11-07 17:49 GMT] | | | | Grzegorz Gryc Польша Local time: 16:03
Член ProZ.com c 2005 французский => польский + ... Автор темы |
Laurent KRAULAND wrote:
but while we speak about basic / open-source formats, have you ever tried importing an .sdlxliff file to Heartsome or Swordfish? I am curious to know whether this would work smoothly... |
|
Yes, some time ago (in June?).
Swordfish deleted all the SDL specific extensions and the file became unusable.
But the Swordfish world is rapidly changing
Now, I have no time to test it but I suppose the solution already exist or will be published shortly.
PS.
SDLX does almost perfectly.
With some additional processing it's a decent alternative 
I never tested it thoroughly but I received some confirmation it works even for very complex documents.
When you have an ITD, you have TTX.
When you have TTX, the door is wide open 
Cheers
GG
[Edited at 2009-11-07 21:48 GMT] | | | | Grzegorz Gryc Польша Local time: 16:03
Член ProZ.com c 2005 французский => польский + ... Автор темы | | CSV case explanation | Nov 7 |
Laurent KRAULAND wrote:
[...]As per the .csv files, I am now warned and will not do any attempt in that direction . |
|
For the explanation, see my posts in the thread:
http://www.proz.com/forum/déjà_vu_support/117860-exporting_multiterm_7_termbases_to_dvx.html
In Multiterm 2009 SP1, it's still the same.
BTW.
The tab delimited file definition according to Multiterm guys is just beautiful.
You put a tab somewhere, you have a correct tab delimited file.
Hereby, I post my "a" delimited file definition.
You put an "a" char anywhere, you have a correct "a" delimited file.
Both definitions are true/absurd at (almost) the same level.
Use the default CSV export definition and export the "Sample" termbase provided with Multiterm.
Before you take a look on the results, finish your coffee/drink etc., you may harm your screen or keyboard.
^-^
[Edited at 2009-11-07 21:49 GMT] | | | | To report site rules violations or get help, contact a site moderator | Multiterm 2009 and TBX import |