Hi Simon,

that is a difficult question. The developers would say yes, users may have a different perception.

I am known not to be a fan of its base concept using pages per languages and would have preferred one page with localized attributes and tabmodules (module links to pages) per language - though the core approach provides more flexibility, it is much more work for editors to provide cosistent look of the page in all languages. Another problem is current implementation, which tends to have flaws, like vanishing modules or moving between pages, as reported by a number of users and incompatibility with other features (do not use "set as default module settings" or "show on all pages").

Core content localization does not support modules not requiring content translation (like a feedback form) or use of multilingual modules. In my opinion there is a need for multilingual modules for most structured content - e.g. announcements, shopping pages, product catalogues etc. Handling those in multiple language specific modules would become a nightmare.

The current UI implements a workflow for a page editor in portal default langauge and translators, who take care of localization of whole pages after the original one has been finished. From my experience this is not the most common use case, many sites are maintained by one person for all languages, who has to translate himself or copy & paste translations from external sources.