when I translate my posts with the ATE from German > English there is a problem with the special character "&".
The original German title of the blog post is:
Harz - Hanging rope bridge Titan-RT & the Hermannshöhle (Germany)
The ATE translate this in:
Harz - Suspension rope bridge Titan-RT & ; the Hermannshöhle (Germany)
1) So the "&" character is translated into the Unicode "& ;" (there is no blank after amp, I just added this to show you the unicode). This is generally ok of course, but it did not have to be. Is it possible to turn it off, so that the "&" remains?
2) new is the translation of the "&" character in the URL. This will now be:
germany/harz-suspension-rope-bridge-titanium-rt-amp-the-hermannshoehle-germany
ATE never did that with the "amp" in the URL before, but that came with one of the last updates. I think "amp" is not the right word for the URL. Either this should not be translated at all (because of filler word) or if then with the word "and".
While you are waiting for one of my colleagues to take this ticket and work on it, let me provide you with the first debugging steps or if I can perhaps help with the issue quickly.
We used to have similar issue in the past, but they should be solved now. So I'd ask you to check that WPML and the addon are updated to the latest version (4.3.18)
I would also need your WPML debug information. You can find it in:
WPML -> Support -> click on debug information link
Then you can copy/paste the text you see in the Debug box I'll enable for the next answer.
More information here: http://wpml.org/faq/provide-debug-information-faster-support/
If this doesn't help, please provide the job ID - it's the number you can see in the URL when you open the post in the Advanced Editor - and also the .xliff file for the affected page.
So we can reproduce and eventually escalate the issue.
We have known issues while translating the ampersand sign with ATE and our compatibility team is looking for a permanent fix now. Therefore most probably this ticket will be related to the following ones.
Therefore as a workaround for the time being please add code of the following link in your theme functions.php after a full site backup and make sure the issue is existing or not.
