Trados Studio
Trados Enterprise
Trados Team
Trados GroupShare
Trados Business Manager
Passolo
MultiTerm
RWS AppStore
Connectors
Beta Groups
Managed Translation
MultiTrans
TMS
WorldServer
Language Weaver
Language Weaver Connectors
Language Weaver Edge
Tridion Docs
Tridion Sites
LiveContent S1000D
XPP
Language Developers
Tridion Docs Developers
Community Help
RWS User Experience
Internal Trados Ideas Community
Mercury
RWS Community Internal Group
RWS Training & Certification
Style Guides
RWS Campus
RWS Enterprise Technology Partners
Trados Approved Trainers
ETUG (European Trados User Group) Public Information
Nordic Tridion Docs User Group
Tridion West Coast User Group
Trados Studio Ideas
Trados GroupShare Ideas
Trados Team Ideas
Trados Team Terminology Ideas
Trados Enterprise Ideas
Trados Business Manager Ideas
MultiTerm Ideas
Passolo Ideas
RWS Appstore Ideas
Tridion Docs Ideas
Tridion Sites Ideas
Language Weaver Ideas
Language Weaver Edge Ideas
Managed Translation - Enterprise Ideas
TMS Ideas
WorldServer Ideas
LiveContent S1000D Ideas
Contenta S1000D
XPP Ideas
Events & Webinars
To RWS Support
Detecting language please wait for.......
Trados Studio 2021 SR2 - 16.2.9.9198を使用しております。
フィールド入力されているExcel翻訳メモリをtmxへ変換する方法が分かりましたら、ご教示お願いいたします。
経緯
フィールドが入力されている翻訳メモリをAppStoreの「Glossary Converter」でExcelに書き出しました。書き出されたExcelを元の翻訳メモリ(tmx)に戻したいです。フィールドが入力されていなければ、tmxに戻るのですが、フィールドがある場合はtmxに戻すことは難しいでしょうか。何か方法があるようでしたら、ご教示いただけないでしょうか。よろしくお願いいたします。
M Tori
The Glossary Converter has a simple approach to TMX conversion so if you are using it with field values you need to pay careful attention to the information in the product help for the app. The English version says this:
Translation Memory eXchange is, as the name suggests, not a terminology, but a translation format. I only added this for one specific customer workflow. It did turn out to be used, so the created files are now following the full TMX standard (I hope...). Support, though, is rudimentary. Anything beyond the most basic tmx could cause problems converting into anything else. tags and entities are only handled in a brute force way (<b> becomes <b>, instead of the correct <bpt i="1"><b></bpt>, and so on.
Termbase fields are mapped to prop elements. There are some qiurks, since tmx is an open format, and the content of props can have any format. The converter recognises two formats, distinguished by the o-tmf attribute in the header.:
The tuid attribute is converted into an entry field. On import, an entry field called "tuid" is interpreted as the tuid, not a field. If there is no tuid in the import, a unique number is created. Note: if your import file has only a tuid in some entries, and uses ordinal numbers like 1, 2, 3,..., there may be number clashes. You should have a tuid for all or no entries.
I'm sure you can find multiple ways of breaking things with tmx, but at the moment it has low priority. If you want to do proper TMX processing, try Olifant.
Hope that helps you answer your question?
Paulさま
お世話になっております。
お忙しいところ、ご回答ありがとうございました。