November Happy Hour will be moved to Thursday December 5th.
AI OnAI Off
November Happy Hour will be moved to Thursday December 5th.
CMS 12.21.4.0, using Language Manager 5.3.0.0 - seeing the same experience using the standard Cognative Services Service, and also using other third party translators (DeepL, Google, etc.)
Hi,
I came across that behavior also, so I had to figure out a solution for that. I ended up with creatin an own implementation of ILanguageBranchManager and altered the code in CopyDataFromMasterBranch to roughly do this:
Some notes:
So I've used advice over at article https://support.optimizely.com/hc/en-us/articles/115005062883-Enable-special-characters-in-URL-Segment to enable "special characters" in a URL and that works great for pages that are created in Frech, etc.
When I have a page that is created in English and then auto-translated using language manager however, the results are less good - you'll see below how é is convered to "_41" - where this number seems to be random (I'd assumed it may have been ascii or something, it's not).
So far as I understand language manager it deals with strings independently of where they come from and what they are - so Markets to Marchés will always happen whether it's the URL or body copy. And I can see in Language Manager that this is happening, that it is returning Marchés.
Any thoughts then on how we have Optimizely respect the special character and put it into the URL on translation, as well as on creation (as per the article at the top there).
Thanks.