[Resolved] Translation of Product Category (Taxonomy) with DeepL
This thread is resolved. Here is a description of the problem and solution.
Problem: You are trying to translate a product category from English to Portuguese using WPML and DeepL. You encountered issues where specific words were not translated, phrases were duplicated, and updates to translations did not reflect changes. Solution: 1. The issue with the word 'reduced' not translating and the duplication of 'Os nossos' is due to a specific glossary combination issue with DeepL. This is a known issue and is currently being addressed by our development team. 2. We have made adjustments to how the glossary functions by removing the type of glossary, which should resolve the problem. Please check if the translation issues are resolved now.
If these steps do not resolve your issue or if the solution seems outdated or irrelevant to your case, we highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If problems persist, please open a new support ticket at WPML support forum for further assistance.
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.
Background of the issue:
I am trying to translate a product category from English to Portuguese (Portugal) using WPML and DeepL. I followed the instructions on: https://wpml.org/faq/how-to-translate-all-taxonomy-terms-at-once/ and it initially worked. However, I encountered issues with the translation of specific words and the update process. Link to a page where the issue can be seen: hidden link
Symptoms:
1. The word 'reduced' was not translated from English when the content is in plain text. 2. The phrase 'Os nossos' was added twice in some paragraphs when the content is not in plain text. 3. After removing the entire product category description in English and translating it again, the Portuguese version was not updated to reflect the changes; it retained the original content from the first translation.
Questions:
Why was the word 'reduced' not translated when the content is in plain text?
Why is the phrase 'Os nossos' repeated in some paragraphs when the content is not in plain text?
Why did the Portuguese version not update after re-translating the product category description?
The initial issue is still there (The word *reduced* is still displayed in Portugese, even after updating the glossary and clicking on Update existing translations).
The product used for the translation job was hidden link
Additionally, existing translated content does not get translated the 2nd time around when I send the product for translation.
New threads created by Dražen and linked to this one are listed below:
Unfortunately, we cannot use WPML AI engine as the we are obligated to use DeepL as per the client request.
You may want to advise DeepL as to why this phrase works when translated to Portuguese:
1. "Our Laser Cladding consumables provide superior wear protection and durability in demanding applications. Our range includes wires compatible with both coaxial and lateral supply systems, supporting single and multiple wire configurations for high and low power applications."
Whereas this phrase translates incorrectly:
2. "Our Cladding consumables provide increased resistance to wear resulting from abrasion, temperature, corrosion, and erosion. Our range includes wires for stainless steels, nickel-based alloys, and cobalt based alloys, offering excellent weldability and outstanding mechanical properties."
The first phrase does not repeat "Our"> "Os nossos Laser Cladding consumíveis proporcionam..."
The second phrase repeats "Our" > "Os nossos Cladding Os nossos consumíveis proporcionam ..."
So I don't think this is a glossary issue. It is more likely a DeepL translation issue.
it is an specific glossary combination with links issue with DEEPL, and we will be fixing it in the future, it is already confirmed issue and escalated, but it will take time before it gets fixed.
For now, other then what I shared we do not have other workaround to suggest.
Thank you,
We will await the fix and for now, work with the client on tweaking the glossary terms were affected to see if that resolves the issue for now.
