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.......
We have deprecated the XML/XHTML v1 File filters used by Trados Enterprise. This means that creation of v1 based filters is disabled.
We recommend all users and customers to use the XML v2 File filter which supports all v1 functionality, provides higher performance and has bugs resolved.
Existing v1 configurations can still be used and modified. Existing projects will also not be affected.
Instructions on how to migrate from v1 to v2 can be found here: https://docs.rws.com/791595/981251/trados-enterprise/migrating-xml-v1-based-file-type-configurations-in-------------trados-studio
Hi Frank, this was indeed a key change in v2. In v1, all this content tended to bloat the resulting bilingual file beyond what was required for healthy and performant processing, not least when it comes to the cloud, but also in local and server scenarios. So we now take this content out of the translatable document, making it much leaner, but you should still be able to see such content in the raw prewiew (XML nodes), so this would now be the recommended way to consult such content where needed. Thanks, Daniel
Hi Luis, as far as I am aware of, there is one tiny feature (others might call it "inconvenient") in XML v2 compared to XML v1: XML v2 does not allow a translator to switch to the All-Content view in Studio and see all the non-translatable text nodes in addition to the translatable ones, correct? Otherwise, I also think that XML v2 covers all functionality covered by both XML v1.2 and XML v1.3. Regards Frank