great suggestion. would that mean that you are switching completely to new language in edit ui, or just creating new content in that language?
@Tomas! You can install and use Language Manager add-on. With LM, you can see all available languages of the content and easy to create, duplicate, translate and compare between language branches!
We would preferably like to keep the existing language in the edit ui (and page tree), and just create the new content in the specified language. I do, however, think that will be the hardest to implement without confusing the user.
We are (as I said) already using the languages gadget (EPiServer.Labs.LanguageManager), but it has some shortcomings. The gadget makes it easy to switch language and translate existing content. It does not help with creating sub pages in a new language.
To create a sub page in another language, we will have to first switch language and then create the new page from the episerver context menu. When the user switch language, the page tree is reloaded, all expanded state are lost and only the selected node are kept selected. For editors not familiar with the language (they are changing to), this could be confusing.
When creating new content it is often not clear to our editors what language the new content will have. Without looking at the language manager or the sites-tab there is no way to tell. Our suggestion with the language dropdown will also make it clearer what language new content are created in.
On several of our multi-lanuage sites, the editors have problems with creating new pages in different languages. Of course they should learn how to switch language with the sites-tab, and use the language gadget, but this feature has been requested many times.
One example: We have editors that are publising content in several languages they do not understand. They would like to browse the page tree in their own language, and be able to select language when they create the page. Like this:
The default value should be the current language.