Hi Joe,

there are currently two different approaches to implement multilingual (ML) sites:

• Apollo PageLocalization, DSLocalizator and EALO perform translation of a page name, title, description and keywords.
  They require use of multilingual modules for ML content, like Apollo MLHTML, Locopon MMLinks or dnnWerk Nuntio Content
• Language Specific Pages (LSP) had been added in DNN 5.5.0 as "Content Localization" solution by DNN Corp. It supports use of monolingual modules, but does not support any ML modules or modules with content not identified by moduleID (like DNN Blog 5.x)

None of both solution is perfect, both have a number of constaints, i.e. the more suitable solution depends on your needs:

• LSP enforces a strict workflow: you need to start with portal default language and use page settings to claim modules to be ready for translation, while Apollo/DSL/EALO are easier to use, as there is just a language switch inside the modules.
• There are still a couple of issues known with LSP, e.g. do not use "show on all pages" module setting.
• if using Apollo/DSL/EALO, it depends on the module, whether to hide it for specific language, otherwise all modules are need to provided for all languages (while Apollo and DSL support suppressing specific pages per language)
• If using LSP, module settings are not synchronized across languages, i.e. if you want to move a module from one pane to another, you'll have to repeat this for every language - same for all other page related settings.

I am not satisfied with the current situation, where LSP does not suit most of my requirements while development of the other solutions has been slowed down or terminated. Hopefully, we will see improvements in DNN 7.