I'm Peter Holzer, I'm from Zurich. I'm doing Plone since 2004. I'm doing Plone since 2004 and I'm part of the Blue Dynamics Alliance, maybe you've heard of that.

So I live in Switzerland and from the nature of the country we have several languages to cater to. How many of you have used Lingua Plone? How many languages do you produce content for?

Two? Five? Wow. So, Plone multilingual has a kind of new concept. The languages are in their own folders. They're not in the kind of mixed up same root structure anymore.

We don't have a canonical object where you translate from. You can translate from any content object to the other. You can also link existing content items as you could before with a Lingua Plone.

Maybe, let's just dive in. We create a nice CMI by the way.

Down here, Plone multilingual is part of Plone 5 but it's not installed by default.

So you have to install it. Then you have the Plone 5 site.

To configure the languages you go to the language control panel. There you select the languages that you want to use. For me it's German and let's say French.

Here you can choose to show flags instead of the language names. The second checkbox shows the language selector at any time. Even if the content is not translated it will show up and you will be able to switch between the languages.

Then this also moved from the CMI to Plone control panel. The basic language setup and negotiation stuff.

That detail, that's the content translation help. When I save here, it created my language root folders. If I go to the start page again, I had French before.

You see the empty language root folders. What it did, if you go to contents, it added the language root folders for you.

The default content is still there. If you need that, you can just copy it or cut it out. Go to your English folder and paste it and then you have it again.

We want to create content and translate it. Maybe create a news item, get a picture as well.

Then what you get is the translate menu from Plone app multilingual. You have several options here. Basically, if you have not translated your content yet, it says create and the language name. If the content already exists, it will be just edit and translation.

We have the Babel view as we know it from Ringo Plone before. We add our content and also we add the image again because it's a separate content object.

We switch to German. Now it's called Ubersetzens instead of translate.

I can edit the English version from the menu here. We want to do another translation.

Now we can switch between the languages which are linked.

The portlet shows up because it's the default setting from the news folder. What you see is within the languages, we didn't have the news folder set up. We just translated those pages and it took the nearest location that made sense.

So because we don't have the news folder or a not translated news folder, it put it up in the root of the language. Let's start with translating the news folder as well.

I'm translating the collection, sorry. The collection would have been created in the root again. What I try to do is set up my basic structure first. Because after you edit all the content, it's quite hard to get the overview of what is there and what is in the correct location.

Let's translate the folder first.

I get it right. Something like this. What I can do now is I go up to my language folder, got my content and put it in here.

Same for German and I'm also at again within the folders.

English isn't displaying because this is a collection that has a review state published.

Just if you ran into that. So let's go to the translation menu again. Now you see you have the edit item. I could also add more translations, but it doesn't make sense here because we already have those translations.

So what I do is I move a translation and it isn't deleted, it's just removed.

And say add translation again, French. And then I can go through my contents. Did I delete it now?

Sorry. Yes, I deleted it. So let's do it the other way. I create the news item, get my content again and I'll try to add the French version here.

And now I got my French version again.

In LinguaPlone we had a thing that you could have a folder that is universal or not language dependent in that way. We don't have this in Plone or multilingual, not anymore.

But we have a universal folder which is called media. It's possible to rename it if media is already kind of blocked with another folder.

And this folder is just mapped into the other languages. So here you can upload all your standard images that won't change or maybe documents. And you can also create a collection that pulls content from there.

So my French is not that good. So these are the contents from the universal folder.

And they will be available in every language. If you have documents that you want to display from another language, you could also do a collection. If you put an absolute path in there from the site route to your other language, you can also display other stuff here.

Any questions? To be clear, Plone app multilingual is available but just not installed?

Is it available in the stock Plone? No, you just have to activate. It'd be not hard to retrofit a site for multiple languages, right? No, it's quite easy. The only thing is that you have to reorganize your content if you didn't set it up from the beginning. Yeah, sure. I just have to add the behavior that is translatable here.

It's different. So instead of beep-beep at night.

Exactly. So what we did for a project of mine was for a Swiss company and they produced lots of documents. And they had the requirement to display all content, like the missing contents that were untranslated within the language.

And that was kind of hard for the amount of documents. You don't want to put them all in the universal folder.

Because that's just universal, it's not language. So the request was German was the main language, then they had translations to English, maybe French or French, maybe Italian. And they wanted to display just the missing documents from another language.

So instead of showing all documents, they wanted to add the missing ones. That wasn't possible so far. We made an add-on, it's a separate index, we released it these days.

It allows you to define a fallback. So I have a control panel, it's a simple JSON format where you define your language fallbacks for each language. So for example German, English, French in that order. And for English it's maybe French and Italian and then German.

And what it does, if you create the content item, it checks what languages are already translated. And indexes the missing language versions from your fallback.

So the content, if it's translated, is in the correct folder. But it is displayed within the collection for example, like for the documents. And if you click on that document, you get transferred to the original place where it's created.

So it allows you to kind of summarize or simulate contents. So to show a most complete collection of information.

And what we also did for the project was a package that was called LinguaTags. Because they used keywords a lot within the project. And what we did there is we defined a canonical language for the keywords.

So in this case German. And we made a control panel overview where it could translate the title of the keyword. And within the views we overwritten the keywords widget or the viewlet. And the search tag is still the German one or the canonical somehow.

And for display we use the translated one.