Trados Business Manager
Speech to Text
Managed Translation - Enterprise
Translation Management Connectors
Language Weaver Connectors
Language Weaver Edge
Tridion Docs Developers
RWS User Experience
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.......
Hi there. I'm using Studio 2021.
Based on the picture above, I would like to take ID 215 in source segment and put it into ID 214 as a blue color - but it turned black instead. I do understand that this happened because the difference between the formatting between those two. So I would usually add a 'cf tags'.
However, if there is a repeating sentences, it wont save along with the 'cf' tags. Like this.
The reason I want to do it like is because, whenever the same Japanese sentences came up in future, I want it to translate in the target segment with both Japanese and English at the same time (in the same ID).
Any solution on this? Thank you!
Hi Afiqah Umairah Mohd AzniThank you for your clear explanation.If I were to summaries your scenario it would be:Regardless of how a user chooses to format their target translation, why is the font being…
Hi Afiqah Umairah Mohd AzniThank you for your clear explanation.If I were to summaries your scenario it would be:Regardless of how a user chooses to format their target translation, why is the font being applied not always protected when it comes to auto-propagation. I say the word always very sensitively, on the bases that if you see my mock example at segment 4 when I applied "trickery" to insert the CF tags segment 4 displays correctly.However segment 5, which would be populated using auto-propagate the tags are not applied. Yet... if one where to apply bold text which is supported via the QuickInsert, segment 5 keeps the bold tags which were originated from segment 4Ideally we should enhance how auto-propagate works, based on the fact that if additional font is placed on target side using the supported QuickInsert it replicates correctly across all instances throughout the document. By extension it should behave exactly the same regardless of how one apply tags. Which in your case I suspect was across segments using copy/paste?