Home›Support›English Support›[Resolved] Kurmanji kmr (Latin alphabet, LTR) not supported in professional translation?
[Resolved] Kurmanji kmr (Latin alphabet, LTR) not supported in professional translation?
This thread is resolved. Here is a description of the problem and solution.
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.
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.
Hi, Northern Kurdish / Kurmanji as LTR with Latin alphabet is not supported in WPML out of the box.
However i've found forum posts, that suggested to create the language Kurmandji with the correct code kmr and define as ltr.
That worked so far.
Now we wanted to send our content to a professional translation service via wpml backend. But we got the error as depicted in the screenshot.
Thank you for getting in touch with us. Indeed, Northern Kurdish still isn't supported by WordPress.
Can you please share the exact steps you followed? That way I can test the solution on my side and verify if it actually works with WPML's current version.
I'm not so sure if it is (still) true that kurmanji is not supported by wp. There a kurmanji version of the official website (latin alphabet and ltr): hidden link
2: We marked some content for translation in translation management, then submitted the translation job to the professional translation service lingarium. (which are integrated into wpml).
That's when we got the error from the screenshot above.
After investigating your issue further, I've found out that this error happens probably due to the language code used and because of the support the professional translation service has. Take a look at this similar issue:
Maybe, in your case, using "ku" instead of "kmr" might solve the issue. If that's not the case, it might mean that this language is not supported by your translation service, unfortunately. You can translate your content manually, as a workaround.
Hi Lucas,
thanks for the link. Our case is slightly different though, kmr is the correct iso code for kurmanji. (Compare hidden link to hidden link)
Our translation service says they do support both ku and kmr. Do you know if they might need to adjust some parameters to allow the "custom language", maybe a documentation link that I can send them, so their technical staff can fix it?
Or is it impossible to use the WPML translation service api with custom added languages?
Using "ku" as the code is not really an option, it's used for kurdish with arabic letters (see above wp links) and is right-to-left. This was causing all sorts of problems in the backend and with translators in the beginning, which is why we had to create the Kurdish/Kurmanji language as kmr.
Our workaround would be downloading xliff files from the generated jobs manually, sending them in for translation and importing afterwards.
But, we have a lot of content and if there is an option to keep using the api by fixing something, that woud be very appreciated 🙂
Thank you for sharing the information. To answer your questions, I'll have to escalate your issue to our development team. To achieve that, I'll need to access your website and make a copy (with Duplicator or other similar plugin), please confirm if that's a possibility.
If so, you will find the needed fields for this below the comment area when you log in to leave your next reply. The information you will enter is private which means only you and I can see and have access to it.
IMPORTANT
- Please make a backup of site files and database before providing us access.
- If you do not see the wp-admin/FTP fields this means your post & website login details will be made PUBLIC. DO NOT post your website details unless you see the required wp-admin/FTP fields. If you do not, please ask me to enable the private box. The private box looks like this:
Thank you for sharing. I sent your ticket to our translation service team, which will look for a solution to your issue. That usually takes a few days. As soon as I have new information, I'll keep you posted.
Just to be sure: We will be trying again on the live site.
Do we need to carry over any changes your team made on the staging domain or has this been resolved on your side, e.g. at the API?
Hi, now we get a different error. (Please see screenshot)
Does this mean, that we need to check with the translation service if they really enabled kmr?
And if so, do you have any ressouces that I can point them to?
Small update:
While we did not get an error message this time when sending the translation job to the service, they replied that it did not work (sorry, nothing more specific).
But they're checking on their end now. Maybe they have contacted you as well (Service name: Linguarum).
We are expecting them to get back to us beginning next week.
