This site uses cookies.
Some of these cookies are essential to the operation of the site,
while others help to improve your experience by providing insights into how the site is being used.
For more information, please see the ProZ.com privacy policy.
I would like to create a multilingual glossary in five languages but I do not have a term entry for each language. When I execute Multiterm html export the terms are mixed and not in that column the term is dedicated to. Multiterm is just filling in the fields from left to right when a target term of one or more languages is missing.
Does somebody faces the same problem?
Thanks!
Subject:
Comment:
The contents of this post will automatically be included in the ticket generated. Please add any additional comments or explanation (optional)
Grzegorz Gryc Local time: 14:44 فرنسي إلى بولندي + ...
A bug...
Mar 9, 2009
Mosor wrote:
I would like to create a multilingual glossary in five languages but I do not have a term entry for each language. When I execute Multiterm html export the terms are mixed and not in that column the term is dedicated to. Multiterm is just filling in the fields from left to right when a target term of one or more languages is missing.
Does somebody faces the same problem?
Yes, it's a flagrant bug.
The same bug is in the CSV export filter.
You have two workarounds:
- export as xml, then import the xml in Across, then export as CSV (if your termbase definition is complex, you must modify the import definition in Across, a standard termbase will work OK) .
- export as Multiterm 5 using a definition created manually (the default definition exports only the active source and target languages), then you can convert it to XLS using a well known macro from the TW_users yahoo group.
Hereby, I put a virtual red-hot iron rod in the arses of the Multiterm programmers...
Cheers
GG
Subject:
Comment:
The contents of this post will automatically be included in the ticket generated. Please add any additional comments or explanation (optional)
Vito Smolej ألمانيا Local time: 14:44 عضو (2004) أنجليزي إلى سلوفيني + ...
مترجم الموقع
"Hereby, I put a virtual red-hot iron rod ..."
Mar 9, 2009
I think they've stopped long ago to feel the pain ...
Subject:
Comment:
The contents of this post will automatically be included in the ticket generated. Please add any additional comments or explanation (optional)
FarkasAndras Local time: 14:44 أنجليزي إلى مجري + ...
macro
Mar 9, 2009
Grzegorz Gryc wrote:
- export as Multiterm 5 using a definition created manually (the default definition exports only the active source and target languages), then you can convert it to XLS using a well known macro from the TW_users yahoo group.
Hereby, I put a virtual red-hot iron rod in the arses of the Multiterm programmers...
Cheers
GG
Could you link to or upload said macro?
Subject:
Comment:
The contents of this post will automatically be included in the ticket generated. Please add any additional comments or explanation (optional)
Grzegorz Gryc Local time: 14:44 فرنسي إلى بولندي + ...
MT5-XLS converter...
Mar 9, 2009
FarkasAndras wrote:
Grzegorz Gryc wrote:
- export as Multiterm 5 using a definition created manually (the default definition exports only the active source and target languages), then you can convert it to XLS using a well known macro from the TW_users yahoo group.
Hereby, I put a virtual red-hot iron rod in the arses of the Multiterm programmers...
- export as Multiterm 5 using a definition created manually (the default definition exports only the active source and target languages).
Do you have this definition in a file form? I tried to modify the default definition but I did not obtain the expected results.
Miran
Subject:
Comment:
The contents of this post will automatically be included in the ticket generated. Please add any additional comments or explanation (optional)
Grzegorz Gryc Local time: 14:44 فرنسي إلى بولندي + ...
Termbase dependent definitions :(
Sep 28, 2009
miran wrote:
Grzegorz Gryc wrote:
- export as Multiterm 5 using a definition created manually (the default definition exports only the active source and target languages).
Do you have this definition in a file form? I tried to modify the default definition but I did not obtain the expected results.
The definition should be made separately for every termbase.
Even if I send you some defintion, it will not work on your termbases.
IMHO the fact that Multiterm is unable to export multilingual termbases by default is a pain in the arse.
Probably the best approach is to export as Trados XML and use an external tool.
Cheers
GG
Michael Beijer
Subject:
Comment:
The contents of this post will automatically be included in the ticket generated. Please add any additional comments or explanation (optional)
Michael Beijer المملكة المتحدة Local time: 13:44 عضو (2009) هولندي إلى أنجليزي + ...
Pastey is an innovative desktop application that bridges the gap between human expertise and artificial intelligence. With intuitive keyboard shortcuts, Pastey transforms your source text into AI-powered draft translations.
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.