This thread is resolved. Here is a description of the problem and solution.
Problem:
The client has an ecommerce project named Glare, and they encountered an issue where the project name 'Glare' was incorrectly translated into other languages in their multilingual site setup using WPML. The client created a glossary entry to prevent this but was concerned about updating existing translations without incurring additional costs.
Solution:
We recommended the client to utilize the WPML glossary feature to manage how specific terms are translated, ensuring names like 'Glare' are not mistakenly translated in future content. For detailed steps on creating and managing glossary entries, visit How to Create and Manage Glossary Entries.
Additionally, to address the concern about updating existing translations without extra costs, we informed the client about WPML's translation memory feature, which prevents charges for re-translating the same content. The client can resend the pages for translation via WPML > Translation Management without being charged again for the same translations. For more information, visit How WPML Keeps Track of Your Translations.
If this solution does not apply to your case, or if it seems outdated, 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 issues persist, please open a new support ticket at WPML support forum.
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.
This topic contains 3 replies, has 1 voice.
Last updated by 2 months, 3 weeks ago.
Assisted by: Mihai Apetrei.