Trados Business Manager
Speech to Text
Managed Translation - Enterprise
Translation Management Connectors
Language Weaver Connectors
Language Weaver Edge
Tridion Docs Developers
RWS User Experience
Internal Trados Studio Ideas
RWS Community Internal Group
RWS Access Customer Portal
RWS Professional Services
RWS Training & Certification
RWS Enterprise Technology Partners
Trados Academic Partners
Trados Approved Trainers
ETUG (European Trados User Group) Public Information
Machine Translation User Group
Nordic Tridion Docs User Group
Tridion Docs Europe & APAC User Group
Tridion UK Meetup
Tridion User Group Benelux
Tridion User Group New England
Tridion User Group Ohio Valley
Tridion West Coast User Group
WorldServer User Group
Trados GroupShare Ideas
Trados Studio Ideas
Language Weaver Ideas
Language Weaver Edge Ideas
RWS Language Cloud TMS Ideas
RWS Language Cloud Terminology Ideas
RWS Language Cloud Online Editor Ideas
Managed Translation - Enterprise Ideas
Tridion Docs Ideas
Tridion Sites Ideas
LiveContent S1000D Ideas
Events & Webinars
To RWS Documentation
To RWS Support
Detecting language please wait for.......
When I try to import my cloud TB into a newly created local TB. I get HTML code instead of plain text in some custom fields (note, contexte, see screenshot).
I exported my Cloud TB using the XML format, created my new TB using similar definition and imported the XML into the new TB. Almost everything is fine, except this problem (I tried both the default import and the one below (I don't remember the name)...
Thanks for your help
Try copying as text, or unicode, as opposed to copying and subsequently pasting all the underlying code. I use this small and handy utility all the time:
Malick Mbengue Support Case Id : 00611275. Support case has been logged for your assistance. Please check your SDL Community email address for updates.
Steven Whale: Thank you.
I'm still waiting for a solution. The support team wasn't helpful at all. I really need this termbase out of the cloud and don't wanna waste hours editing these fields.
Did you try to export using a different format?
Yes of course. Support told me yesterday that it was because I used copy/paste with the source text formatting. Thus, this code is exported to the respective fields where I used copy/paste.
Malick Mbengue said:Support told me yesterday that it was because I used copy/paste with the source text formatting. Thus, this code is exported to the respective fields where I used copy/paste.
So your problem is resolved?
No! If the formatting in those fields can create export problems, I think it should not be allowed or at least it should be said before. I would have understood if the export was done without formatting, but exporting coded text!
My understanding of this is that you have simply copied the code and pasted it in. As far as MultiTerm is concerned this is just text. How should it know you actually don't want this? At what point does code copied in automatically become something we should disallow?
I think the solution here is that you copy the text you need after understanding exactly what you are copying from. Perhaps you can share the file you copied, or at least a small sample file, and then we can try to suggest how you could have handled this?
I copied fragments of text from a word document. I pasted these texts in multiterm online fields. On multiterm online, it is text that is displayed. The code only appears when I try to export the data to create a local termbase. And even on the local termbase, there is no problem with the text of some fields while I have also pasted the text of these fields (all texts in the term fields display correctly).
When I paste I just use Ctrl+Alt+V as a matter of course (the shortcut is customisable) and this strips any formatting that the windows clipboard may be holding. In the absence of a smarter solution this might help you.