Skip Navigation

This is the technical support forum for WPML - the multilingual WordPress plugin.

Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.

Tagged: 

This topic contains 5 replies, has 2 voices.

Last updated by Bruno Kos 1 year, 3 months ago.

Assisted by: Bruno Kos.

Author Posts
October 26, 2023 at 12:44 pm #14670567
berntE

Hello,

1. We use this character (») a lot across our website. But when we translate pages using automatic translation it changes » to "
We're spend way too much time correcting this on all pages.
We save the translation memory every time and even added the symbol to our glossary as a noun, but nothing helps.
Any solution to this?

2. We notice that when using ATE image links are marked with orange and even though we save it, the next time we open ATE, it's registered as missing translation again. And we save the translation memory every time. Is this a bug?

3. After the initial review of a translated page we don't see all those pages in the "translations" tab in the WPML plugin. Seems to be a bit random how many or which of the pages it lists. This makes it a bit more difficult if we want to access the ATE again later.

4. If a page has been translated previously and later more content is added in the original page in the default language, how can we make sure that it updates the content (or at least show as review needed) on the translated pages. We had an example where an image and a themify layout part were added, but it wasn't reflected on the translated page. We had to translate the page all over again.

Hope you can address each question.
Thank you

October 27, 2023 at 12:33 pm #14678875

Bruno Kos
Supporter

Languages: English (English ) German (Deutsch ) French (Français )

Timezone: Europe/Zagreb (GMT+01:00)

Hi,

Thank you for contacting WPML support!

For support rules we can cover only one issue per ticket as otherwise tickets can easily end up very long and difficult to manage.

Let me split the ticket.

I checked the first one and can confirm the issue - I am checking this with our team and will keep you posted.

Regards,
Bruno Kos

glossary.jpg
even after glossary.jpg
October 30, 2023 at 7:05 am #14688417

Bruno Kos
Supporter

Languages: English (English ) German (Deutsch ) French (Français )

Timezone: Europe/Zagreb (GMT+01:00)

This is escalated to our 2nd tier team and may take some debugging time, I'll get back to you as soon as I have any news or questions for you.

October 30, 2023 at 4:38 pm #14693871

berntE

Very well. Thanks.
I've found out that it's actually from the Deepl engine. If you go to the Deepl translator website and enter the character you'll see it's not supported.

October 31, 2023 at 9:57 am #14698101

Bruno Kos
Supporter

Languages: English (English ) German (Deutsch ) French (Français )

Timezone: Europe/Zagreb (GMT+01:00)

We are still checking with our ATE team on whether we can get glossary to override translation engine specifics, in my opinion it should work his way. I still have no other information to share.

November 2, 2023 at 10:53 am #14715509

Bruno Kos
Supporter

Languages: English (English ) German (Deutsch ) French (Français )

Timezone: Europe/Zagreb (GMT+01:00)

I have a confirmation from our ATE team that this is definitely an issue with Deepl, for some reason they translate these characters in the way they do.

Given that we use their translation engine, perhaps you can report this to them and get clarification on why are they doing it this way?

November 3, 2023 at 5:54 am #14722429

berntE

Thanks Bruno. Yes, I found out as well that this is an issue with the DeepL engine. I will report the issue.
In the mean time we hired a developer that has made a workaround.
Thank you