<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=iso-8859-1"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.StileMessaggioDiPostaElettronica17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.StileMessaggioDiPostaElettronica18
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.StileMessaggioDiPostaElettronica19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 2.0cm 2.0cm 2.0cm;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=IT link="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoNormal><a name="_MailEndCompose"><span lang=EN-GB style='color:#1F497D'>Hi Kai,<o:p></o:p></span></a></p><p class=MsoNormal><span lang=EN-GB style='color:#1F497D'>unfortunately this seems not possible in example 1. Since the content items are in the root .content folder, only the container pages which resides in /it and /de folder are affected by locales-available property. The content items still show all the locales.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB style='color:#1F497D'>If this would be possible, could be a reasonable solution in fact.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB style='color:#1F497D'>Bye, Lisa<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB style='color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span style='mso-fareast-language:IT'>Da:</span></b><span style='mso-fareast-language:IT'> opencms-dev-bounces@opencms.org [mailto:opencms-dev-bounces@opencms.org] <b>Per conto di </b>Schliemann, Kai<br><b>Inviato:</b> giovedì 13 marzo 2014 11.34<br><b>A:</b> The OpenCms mailing list<br><b>Oggetto:</b> Re: [opencms-dev] ade and multilanguage best practices<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'>Hi Lisa,<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'>you can set the property „locales-available“ on the language folder as a comma separated list. In the editor only the in this way configured locales are shown.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'>So considering your example 1 you could set “locales-available” on the “it” folder to “it” and on the “de” folder to “de”.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'>There is no permission check, doing it that way. But the editor cannot choose another language in the editor.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'>HTH<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'>Regards<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'>Kai<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=DE style='font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-language:DE'>Von:</span></b><span lang=DE style='font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-language:DE'> <a href="mailto:opencms-dev-bounces@opencms.org">opencms-dev-bounces@opencms.org</a> [<a href="mailto:opencms-dev-bounces@opencms.org">mailto:opencms-dev-bounces@opencms.org</a>] <b>Im Auftrag von </b><a href="mailto:lruggeri@maticad.it">lruggeri@maticad.it</a><br><b>Gesendet:</b> Mittwoch, 12. März 2014 17:59<br><b>An:</b> 'The OpenCms mailing list'<br><b>Betreff:</b> [opencms-dev] ade and multilanguage best practices<o:p></o:p></span></p></div></div><p class=MsoNormal><span lang=DE><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB>Hello to everyone.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>I’m trying to extend an old opencms based website with ade functionality.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>Which is the best approach of handling multiple languages with ade, and grant translator permissions to edit just their language?<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB>Example 1: <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>/.content<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>/it<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>/de<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB>I create a containerpage for inside /it folder and populate it. This will create content items inside .content root folder.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>I can then copy the container page to /de folder. The references to content items will remain valid.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>With this approach I can set language based permission just on the container pages, not the content items. Is it right?<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB>Example 2:<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>/it<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB> .content/<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>/de<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB> .content/<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>With this approach the containerpages cannot be easily copied because they reference content inside the language folder.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>So each content editor is responsible for maintaining a completely independent version of the site. This allows to grant permission on each language but can be very hard to maintain.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB>I don’t need extreme flexibility, but would like to understand how to set up a configuration that is easy to maintain.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>Do you have any suggestions or previous experience with this topic?<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB>Thank you,<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>Lisa<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p></div></body></html>