Content multilingual is for the moment only an abstract notion to help understand better the various multilingual features of a cms.
"Content" is here meant as the opposite of Container Multilingual. It refers specifically not to the decisions of the webmaster as to the architecture of modules, structures... but to the translation of texts published within the website.
For instance, you can have the text of a wiki page translated (Content), without translating the relevant module (Container).
The decision of the webmaster to allow German or not as one of the languages of the site is a Container multilingual decision. The activity of translating various pages of the same site into German is a Content multilingual business.
Generally it is to be assumed that few translators will be able to understand webmaster activities, and enticing them to site architecture decisions will only confuse them and prevent them to produce text. It is generally advisable to separate the two quite clearly in the user interface, so as to let the translators concentrate fully on Content.
Because Content is separable from the Container, it would be highly useful to be able to export Content into an OpenOffice file, and send it to translators by mail, as an attachment. Even better, translators should be provided with a link in the same mail, with the address to click on in order to send back the resulting translation.