Problem: The client was unable to send content to a professional translation service because Northern Kurdish / Kurmanji, set as an LTR language with a Latin alphabet, is not natively supported in WPML.
Solution: We forwarded the issue to our translation service team to find a solution. After a few days, the team resolved the issue. We recommended the client to attempt sending the content for translation once more.
If you're experiencing a similar issue, we suggest trying to send your content for translation again. However, please note that this solution might be outdated or not applicable to your case. If the problem persists, we highly recommend checking the related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. Should you need further assistance, please do not hesitate to open a new support ticket in the WPML support forum.
Problem: The client is refactoring a custom theme on a WPML-powered nonprofit site with a substantial amount of content and is concerned about the risks of changing WPML settings. They are interested in using new WPML features, specifically the ACFML Addon, to handle custom fields and repeater fields better. The client also has issues with field labels appearing in the translation editor and is looking for a workflow to manage gettext strings efficiently without affecting site performance.
Solution:
1) For an options page, we recommend using "different fields across languages" to allow language switching.
2) For content that maintains the same structure across translations, use "same fields across languages". For the homepage with different content recommendations per language, duplicate the field group and apply "different fields across languages".
4) String Translation performance has improved since WPML version 4.4, as it now uses PO files instead of the database, which can be found in wp-content/languages/wpml.
