[Resolved] DeepL translation from secondary to primary content
This thread is resolved. Here is a description of the problem and solution.
Problem: The client needs to use DeepL to translate content from German to English on a website where German is the primary content language but wants English as the root language (domain.com) and German in a subdirectory (domain.com/de). They are unsure how to set up WPML for this scenario and how to handle automatic translations when the default language is not the primary content language. Solution: 1. Initially, set German as the default language in WPML and translate pages to English using the WPML translation editor or automatic translation features. This can be configured under WPML > Settings. 2. After translating, change the default language to English from WPML > Languages to have English at domain.com and German at domain.com/de. 3. For automatic translations, use one of the following methods: - Enable 'Translate everything automatically' in the background from WPML > Settings > Translation Mode. - Use 'Translate What You Choose' to control specific content translations, creating jobs in WPML > Translation Management > Dashboard. - Utilize the Advanced Translation Editor for automatic translations by accessing jobs through WPML > Translations. 4. Note that automatic translations from a non-default language (German) to the default language (English) will be fully supported in the upcoming WPML 4.7 update, allowing easier management of translations from the Translation Management Dashboard. 5. If setting German as the default language, enable a language directory for the default language to have German at domain.com/de and English at domain.com. 6. For detailed guidance on setting up language directories, visit WPML language setup guide.
If this solution does not fully address your issue or seems outdated, please check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. We highly recommend opening a new support ticket for further assistance 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.
Background of the issue:
We have built a website with English as the default language and German as the secondary language. All content has been added to German pages because site editors are German. We want to use the DeepL translation service to translate content from German to English, ideally for the whole site at once. If that is not possible, we need a way to manually add translations by selecting multiple pages and adding them to a translation function. We also want English to be the language in root (domain.com) and German and other languages in country folders (domain.com/de). We have used WPML for many years but have never used it to automatically translate content with DeepL.
Symptoms:
Confusion about how to get started with automatic translation using DeepL, especially with the setup where the default language is not the language we have content in.
Questions:
How can we use DeepL to translate content from German to English?
While you wait for my colleague to take over the ticket, let me try to help you with the issue quickly.
If you have not yet started, I would advise setting up and using WPML with German as the default language, and then translating your pages to English. You can set the translation engine and automatic translation mode from WPML > Settings.
Then when all of the translations are done, you can change WPML default language from WPML > Languages (it affects only the front) and have en on domain.com and de on domain.com/de.
That is the best I can suggest since it is not possible to use an automatic translation from non default language to another / default language.
The website is going live next week, so for now I can make German default language, translate everything to English and then switch back. But this won't work when we need to translate new pages later, or when we add more languages (as German will still be "authority").
I don't mind defining German as default language (this would actually be best), but I don't understand if this forces German to be in domain.com and English in domain.com/en? If I can set German as default language but in domain.com/de and English as non-default but domain.com, that would be fine - but I guess that's not possible?
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: America/Lima (GMT-05:00)
Hello,
About automatic translations:
There are practically three ways to translate automatically with WPML.
- Translate everything automatically in the background
- Translated selected content automatically by sending it to automatic translation from the Translation Management Dashboard
- Translate automatically by using automatic translation inside the Advanced Translation Editor.
Until now, you can only translate automatically from site default language into other languages.
If you let WPML create the translation in the background, this means, you are using the mode "Translate everything automatically" at WPML > Settings > Translation Mode.
If you switch the setting to "Translate What You Choose" you will be able to control what will be translated and when.
This way you can create jobs at WPML > Translation Management > Dashboard, even by changing the source language of the content that you would like to translate. You could this way create jobs, assign them to a local translator.
The translator will then access the job at WPML > Translations and can use the automatic translation when creating the translation on the Advanced Translation Editor.
The problem is, you can only translate yourself, means you can not direclty send it to automatic translation, but you can create a job, then access it a WPML > Translations and use the automatic translation feature inside the Advanced Translation Editor.
This will change in the upcoming update for WPML 4.7, which would then allow to translate German content automatically simply by sending it to translation from the Translation Management Dashboard. This will work even if the site default language is English, but WPML will not translate the German content automatically in the background without your interaction.
Only content in created in site default language will be automatically translated in the background.
---
About the site URL format:
If you set the site default language to German, then German will be at domain.com and English would be at domain.com/en.
You could in this case enable a language direcotry for the site default language and German would be at domain.com/de while English remains at domain.com/en.
We have now managed to translate a lot of the content by opening pages and clicking through to the WPML translation editor. It seems to be working ok, but is of course not very quick due to the manual process.
Is there a timeframe for when version 4.7 will be released? It sounds like it would speed up the process translating from a second language to other new languages.
Unfortunately making German default and running all languages in language folders is not an option for us; English needs to be in the domain root.
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: America/Lima (GMT-05:00)
The WPML 4.7 Beta is currently available for testing. I suggest you take a backup of your site before procceding.
Go to Plugins > Add new > Commercial and click "Search for WPML Updates".
Now use the dropdown and switch from "Production" to "Beta" channel.
You should now be able to install and activate the WPML Multilingual 4.7 Beta and also install the available addon (String Translation, WCML, ACFML, etc.)
Manage Cookie Consent
We use cookies to optimize our website and services. Your consent allows us to process data such as browsing behavior. Not consenting may affect some features.
Functional
Always active
Required for our website to operate and communicate correctly.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
We use these to analyze the statistics of our site. Collected information is completely anonymous.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
These cookies track your browsing to provide ads relevant to you.