AI OnAI Off
Auto translations creating unpredictable results in Page URL
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.)
Nov 13, 2024 9:04
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:
- Check if it is a page that is in for a translation
- Set the property data PageURLSegment on the destination content to empty, leaving the publishing job to do it´s standard stuff.
Some notes:
- CopyDataFromMasterBranch contains calls to private methods that (depending on how you implement that) also needs to be created.
- I also ended up with creating code to avoi properties of SelectOneAttribute and SelectManyAttribute to be translated, since we only use those values settings.
Nov 28, 2024 7:01
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.