On multilingual web sites it's a really time consuming process to add the translations for the N additional languages.
The actual model assumes that the translator connects and uses directly DNN , in the specific the translator has to EDIT and SAVE the HTML in the modules in every page.
This is more critical if the translation needs to be done on pages with N modules, the complexity and time raises by a factor directly related to the modules number and the number of languages.
Imagine a standard company web site with 20 pages, every pages has 5 unique HTML modules :
we don't consider moules shared on all pages like header and footer.
The content that need to be translated in 4 additional languages : IT,ES,DE and FR, the default is EN.
This is a REAL scenario, not far from the need of a multinational company.
The marketing people with the help of web developers will create and design the english version, and this is a really long process.
When the english master version is ready what is the next step?
In the actual configuration a web master needs to give at least 4 access to 4 translators that connects directly to the DNN web site, edit the HTML and do a job that is not really well suited fot the translators.
The translators need to translate the text, understand the nuances of of language, find the correct way to express the same concepts in a total different language. He doesn't need to bother with an HTML editor with the risk to delete CSS classes or to modify the HTML structure of the module.
In this scenario we have 20 pages X 5 modules X 4 additional languages = 400 modules that need to be edited. Online.
A nicer approach should be preparing a master version in the default language (i.e. EN) of all the pages and export it in a ZIP file.
The exported content should be in a format that a modern translating agency can manage, an HTML file for every page should work. Translation agencies have software that finds text string inside HTML and replaces it with the translating string.
Without modifying the outer HTML code.
Next step will be send the files to the translation agency(ies) and wait for the translations.
When the files come back (not at the same time since different people translates them) the dnn administrator should choose a target language and import the translation in ONE single step reading a folder on DNN or uploading a ZIP file.
Since every page is composed by modules, and every module has a unique ID, the import process will import the translated MODULES based on their IDs.
If in the meantime a module is deleted its translation will be not loaded.
With this mechanism it will also possible to export an entire web site in one language, change it offline and reload it in the same language or in a different language.
We are decoupling the translation process from the editing process, editing is done in the first step by Web developer and in the second step by marketing department in one language.
After this we can prepare one export and send it to 20 translation agencies. No direct connection will be needed. No external access will be required.
Here is a web format I used for exporting and importing the pages on my company's web site, just to give an idea since it targets a thirdy party HTML module, but the concept is really similar also using the default DNN html module:
<!-- DNN Module Export -->
<!-- TABID=618 -->
<META http-equiv="content-type" content="text/html; charset=utf-8">
<a href='http://mydnnwebsite/testpage' target='_blank'>Reference URL for live check (when available):http://mydnnwebsite/testpage</a>
<!-- MODULE START -->
<!-- MODULEID=2750|LOCALE=en-US|VERSION=19 -->
<!-- ORIGINAL MODULE -->
<h1 class="titCol paratop" style="text-align: center;">That's one small step for man, one giant leap for mankind.</h1>
<!-- END ORIGINAL MODULE -->
<!-- TRANSLATE START-->
<h1 class="titCol paratop" style="text-align: center;">Questo è un piccolo passo per un uomo, ma un grande balzo per l'umanità</h1>
<!-- TRANSLATE STOP-->
<!-- MODULE END -->
<!-- MODULE START -->
<!-- MODULEID=2751|LOCALE=en-US|VERSION=9 -->
<!-- ORIGINAL MODULE -->
This scenario could be applied also on custom modules, if they implement a translation export/import interface it will be possible to translate offline also the pages with third party modules.
I hope I was clear despite on my poor written english language, this is a huge problem when dealing with big web sites with N additional languages, and it's also a model that may work in parallel with the actual DNN nationalization mechanism.