Hello,

Please, advice what is the best way to do a content localization with DNN giving pros/cons.

Known to me are 3 ways to achieve content localization. I'll give names for easier recognizing them:
1. DNN natural way 1 - set default language, enable content localization and add aditional languages. Use DNN not multilanguage aware modules. You have 1 portal with "X" module numbers per language (this means 2 languages = 2 menues = 2 modules - each for the specific language).
2. DNN natural way 2 - DNN natural way 1 + multilanguage modules - the same as above, but if you have multilanguage modules - you have only 1 module nevertheless how many languages you have in your portal.
3. DNN unnatural way - having DNN portal for each language you need. For example - 3 languages = 3 DNN portals. Each portal will have a default 1 language. In the flags links you'll have the link to the portal of the language.

What would affect your decision to go one or another way?
What are the pros/cons of each of the above?

Please, give your opinion nevertheless you tried or didn't try multilanguage DNN website.

Please, put your opinion under pros/cons way, not in long mixed explanations for pros & cons in one long paragraph.

My opinion:
DNN natural way 1:
 - pros:
   - 1 administrative/host account to admin portal;  
   - chance to DNN team to improve it in late releases and remove all cons. if that chance happen easy update will solve it;
   - if the structure of the site is small and simple maybe it's the better way;
 - cons:
   - there are problems exporting and importing templates with content localization, so if you work on a local machine and try to move into production you have great problems to solve if you have content localization
   - if you have many pages with many different modules and complex structure, the many problem may arise with DNN content localization;

DNN natural way 2:
 - pros:
  - if you need only a few pages, or a few modules to be localized maybe it's better to use multi-language modules;
  - if you need quick and easy method to do some multi language support;
 - cons:
  - if you use mixes not multi-language and multi-language modules and your site goes bigger and more complex, the problem may arise quickly and impossibly to support and maintain; The best solution is to change generally you strategy;
   - there are problems exporting and importing templates with content localization, so if you work on a local machine and try to move into production you have great problems to solve if you have content localization
   - if you have many pages with many different modules and complex structure, the many problem may arise with DNN content localization;

DNN unnatural way:
 - pros
  - no problems with exporting and importing templates;
  - no problems or errors or bugs concerning localization;
  - very flexible if the structure of your site for different language is different;
  - more flexible for exporting / importing only 1 language, if you need not necessary export and work for all languages;
  - maybe better / more efficient work for DNN database having more portals then multi-language portals;
 - cons:
  - harder to maintain more portals;

------

 

That's it from me.
I really need to know more cons for "DNN unnatural way" for content localization.