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.......
I'm using an existing memory in a new project with mostly 100% matches. I change a segment and confirm it. The segment stays the same in the Translation Results panel and I see "Different target segment in Translation Memory" message if its a CM. If it's a percentage match, the segment appears as confirmed in Editor with the percentage, and the original segment is displayed in the Translation Results panel with the source text marked up to show the differences with the current segment; the newly confirmed segment is not added to the TM. I've never seen this before.
I have these settings:
Also:
All Language Pairs Translation Memory and Automated Translation MEMORY NAME -- Enabled, Lookup, Concordance, Update all checkedSpanish -> English Translation Memory and Automated Translation MEMORY NAME -- Enabled, Lookup, Concordance, Update all checked, in grayWarning message: "You have set up different translation memories or automated translation providers for certain language pairs." (Not a very helpful message, no information on exactly where the problem is or what to do about it, or if anything needs to be done.)
The template had another memory configured, unbeknownst to me. Perhaps this is the source of the "different translation memories" message.
Thanks in advance for any info on how to correct this.
I have stumbled on a solution by doing the following: opening the "ghost" memory that was specified in the template (not one I wanted to be or knew I was using) in Translation Memories. Suddenly that memory started appearing in All Language Pairs/Spanish>English Translation Memory and Automated Translation. My project memory (MEMORY NAME) had the Update box unchecked now. The "different translation memories or translation providers" message went away. Updating is now happening, and to the right memory.