We want to report four issues we identified using glossary entries with German translations. See the links below and the uploaded document for screenshots of these issues.
1. ISSUE 1 - Words next to glossary entries are DROPPED/MISSED in the translation (see examples below) hidden link
1. ‘Toilet’ and ‘Tasks’ are missing from the translation of the H2 block. The URL below appears to be correct.
2. ‘Tasks’ missing from the translation.
3. ‘Toilet’ is missing from the translation.
2. ISSUE 2 – Next to glossary entries, incorrect words are ADDED to the translation. See the example below. hidden link
‘Maintain Menu’ translated correctly. Maintenance was INCORRECTLY added to the translation.
3. ISSUE 3 – Translation of glossary entry correct in Editor. However, it is INCORRECT in the article. See the example below. hidden link
‘ITypes’ is in the glossary, and the correct translation is ‘Rechnungstypen’.
4. ISSUE 4 – A glossary entry appears to be used incorrectly. See the example below. hidden link
‘Bin’ is in the glossary with the translation of ‘Lager’. It appears this is used in the translation of ‘Bing’ Maps.
Please let us know if you need additional information. If Marcel is available, we would appreciate it if he could review the issues.
If the issue persists, I would need to take a closer look at your site. So I would need to request temporary access (WP-Admin and FTP), preferably to a test site where the problem has been replicated. Also please let me know which pages should I try to translate to see the issue.
Your next answer will be private, which means only you and I have access to it.
IMPORTANT: Please take a complete backup of the site to avoid data loss.
memory
After further troubleshooting it looks like the translation are such as they are now because of translation memory or because you translated those text segments in such way before. More details on Translation Memory in the next link:
I also test this on a test site at my end to verify and that seems to be the case.
Please note Glossary Items are sent to automatic translation if a new text/segment is to be translated but if there is translation memory for those text/segments the translation memory returns the translation without any charges.
If you want, I can reset the translation memory for the site hidden link completely and you can start translating again fresh and automatically translating contents should then make proper use of glossary items.
However please note that due to translation memory you are not charged for texts/segments in automatic translation that were already translated and completed before, so resetting translation memory will reset this as well.
If you don't want to reset Translation memory the only workaround is to fix those broken translations manually for now and complete the translations. The Glossary items and phrases should then work fine in new translations or pages.
The translation examples I sent you are not related to the translation memory. They were done for the first time as a test when we set up a new German site. Therefore, there were NO translations available in the German translation memory.
We previously reported glossary issues for French translations. The Supporter initially also said they were translation memory issues until he did further research. He confirmed that two of the issues were WPML errors, and the issues were escalated to WPML Development. The ticket number is 12721499.
I created a short new article, as you requested. hidden link
It demonstrates three out of the four issues that I reported to you occurred again. A new issue was also identified. See the screenshot for the summary of the issues. hidden link
1. Issue 1 – Words next to glossary entries are dropped/missed in the translation.
2. Issue 3 - ‘ITypes’ is in the glossary; the correct translation is ‘Rechnungstypen’. However, it is not translated correctly.
3. Issue 4 - ‘Bin’ is in the glossary with the translation of ‘Lager’. It appears this is used incorrectly in the translation of ‘Bing’ Maps.
4. New Issue – URL translated correctly; H2 block not translated correctly.
You can also reference the previous document I sent you, where more details are provided on these issues.
Please can you research these issues again. I am concerned that we are not getting satisfactory responses on the issues with the WPML glossary.
Our company’s efforts to use WPML as a translation solution are on hold until we know the glossary can be used reliably.
The issues reported in this thread seems to be a mix of the old issues that you reported and the Translation Memory.
The original issues your reported at https://wpml.org/forums/topic/ate-server-issues/ are currently being worked upon by our developers. There should be a fix release soon ( Although we don't have an exact ETA ), the fix is most likely to fix all the related issues. In this case lets wait for a fix/update in the original issue https://wpml.org/forums/topic/ate-server-issues/ and if the issue still persist, please feel free to let us know and we can look into the issues further.
The four issues I reported using the German glossary are DIFFERENT from the ones we reported for the French glossary. I am concerned about your response that they will "most likely" be fixed if they are not replicated by your Support organisation.
Please can you escalate these issues to your second-tier support and/or developers to ensure they are addressed and resolved in the next release?
Also, can you clarify why this support ticket is tagged as "ATE" and not "Glossary"?
The fix for your previous reported issues has now actually been released a few hours ago.
Can you please:
- Create new pages to test the newly reported issues, make sure you don't create new pages with exact same name and text so as to avoid translation memory.
- Try translating the texts on the new text pages and see if the new issues are resolved or not?
- If some or all issues still persists, please let me know the URLs of the new pages with the issues for these new reported issues and I can then further escalate the issues to our 2'nd tier team.
