Affects Version/s: None
Fix Version/s: 3.0.3
We encounter a configuration issue in the Content Translation Ext. module for the integration of Magnolia CMS with translations.com Project Director.
The customer request we received from Goudsmit does not match the Content Translation Ext. module documentation and the site configuration options in Magnolia.
They are looking for the following language translations steps:
source -> target
The website is a multilanguage site supporting 7 languages. The base content is authored by content authors in Dutch. However the base language of translations.com PD is English, not Dutch.
So the first translation batch in Magnolia for Project Director is:
- nl-NL -> en-GB
Once the en-GB translation of the NL-NL source texts are available in Magnolia, the second translation PD batch is done ny translating the en-GB texts into 6 other languages:
- en-GB -> de-DE
- en-GB -> fr-FR
- en-GB -> cs-CZ
- en-GB -> pl-PL
- en-GB -> ru-RU
As can be seen in these requests due to these translation flows there are 2 source languages (nl-NL & en-GB) used for different target language translations.
The problem is that in the module documentation it clearly states that the source language may be the language that is set as default language (= the fallback language of the website) in the site configuration. In the website configuration EN is set to be the default/fallback language, not Dutch. This should be kept, as we do not want to mix DE/FR/CZ/PL/RU text with (incomprehensible!) Dutch in the website in case of missing translations
So, we want to know if there is a way to solve this problem of having the website fallback language EN by default as the module source language with the current module version 3.0.1?
Or maybe this problem can simply be fixed (By Magnolia) by allowing the content author to choose the source language of a translation batch from a list of all configured site languages in the same way as it is currently implemented for the target language of a translation batch? This would require an update of the module, of course.
Please advice how to proceed and want we can communicate back to Goudsmit on how this issue can/will be resolved.
Thanks in advance
Ljubica Dimtrovska/Ronald Kerstens