If the language is entirely different and not covered by WPML, we advised that the client would need to manually translate the content. We provided a link to our documentation on using different translation editors for different pages at https://wpml.org/documentation/translating-your-contents/using-different-translation-editors-for-different-pages/. We also suggested that the client could duplicate content from the default language to the new language and then manually edit the duplicated page.
If the provided solution is not relevant due to being outdated or not applicable to your case, we recommend opening a new support ticket. We also 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.
Problem: The client was trying to set up automatic translation for their site but encountered issues where translations were not being processed as expected. They initially opted to translate all content but then decided to translate only specific pages to conserve credits. The client was also unsure how to handle languages not included in WPML's default 65 languages.
Finally, since the client had additional questions about adding custom languages not available in WPML's default set, we created a separate ticket to focus on that specific issue and provided a link to the new support ticket.
Please note that the solution provided might be irrelevant due to being outdated or not applicable to your case. If the issue persists, we recommend opening a new support ticket. We also 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 you need further assistance, please visit our support forum: https://wpml.org/forums/forum/english-support/.
