[Resolved] Norwegian should be translatable with DeepL
This thread is resolved. Here is a description of the problem and solution.
Problem: The client was unable to add Norwegian under language mapping for translation with DeepL, despite documentation suggesting it should be possible.
After further communication and the client's patience, we escalated the issue and were informed by our ATE department that Norwegian has been enabled with DeepL. We asked the client to check if the issue was resolved.
For account-related requests, such as resetting the year to start from a different date, we directed the client to contact our Accounts department via email at hello[at]wpml.org, as we handle only technical issues on the Support Forum.
If this solution doesn't look relevant to your issue, please open a new support ticket at 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.
I now understand that the issue lies in the integration between WPML and DeepL rather than DeepL's capability to translate Norwegian. Our initial choice of WPML was predicated on the understanding that we could utilise DeepL for Norwegian translation, and it's disappointing to discover that this isn't feasible in practice due to integration issues.
I want to request your assistance in finding a solution. Can you provide any technical guidance or specific steps we might take to enable Norwegian translation via DeepL in WPML? If there are any planned updates or ongoing work to address this issue, it would be helpful to be informed.
Furthermore, as our selection of WPML was based on these functionalities, we must understand what you can offer to compensate for this shortfall. Are there alternative solutions, or are you working on integrating Norwegian language support shortly?
I look forward to a concrete response and a resolution to this issue.
I got a response in regards to this request - in the holidays period, there won't be any changes made to the production environments, so this will be escalated forward, with your approval, and will receive a response somewhere close to the beginning of the year (the beginning of January 2024 - I estimate in the second, maximum third week; it could happen in the first week but I would prefer not to "advertise" it as I don't know for sure the current tasks and priorities the ATE team has on the list).
I also asked about why we don't have all the supported languages that show up on the DeepL site available for WPML when people are using the DeepL translation engine together with WPML: it seems that DeepL doesn't have support for HTML for all the languages, so proper testing has to be conducted before enabling a language for a specific translation engine.
Otherwise, we would risk that bad translation will be served while we would charge people money so that would not be professional, that is why this is not happening at the moment with Norwegian for example.
Please let me know if it is ok with you to have me escalate this and I will then do this and will get back to you at the beginning of January when I have updates.
Your solution appears to no longer trigger any warnings, leading us to believe it's now correct. Given our waiting period, we're considering the possibility of resetting our year to start from the 1st of February.
I am not sure how that goes and if that is possible but we don't handle account-related requests here as we don't have access to that kind of information or decisions.
Please write to hello[at]wpml.org so that you can get in touch with someone from the "Accounts" department.
Here, on the Support Forum, we can handle only technically-related issues.