<HTML>
<HEAD>
<TITLE>Re: [opencms-dev] OpenCMS website localization</TITLE>
</HEAD>
<BODY>
<FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:12pt'>Hi Steve, <BR>
<BR>
Yes, that’s the way we have it set up – one folder per locale, which is not a sibling. We use properties, because there are forms and things like that on the site that pull in labels from properties. <BR>
<BR>
Cheers, <BR>
<BR>
Martin<BR>
<BR>
<BR>
On 16/09/2008 12:40, "Steve Bryan" <<a href="steve@bright-interactive.com">steve@bright-interactive.com</a>> wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:12pt'>Hi Martin, Carl<BR>
<BR>
That's right - I have separate folders en, de etc, and each has the locale<BR>
property set on it. This value propogates down to all files and folders<BR>
underneath. The site structure is replicated in each locale folder using<BR>
folders, page siblings and the corresponding properties on them. Folders<BR>
don't have siblings as such.<BR>
<BR>
Content is stored in the page elements - there are copies of each element<BR>
for each language in the page XML structure. No need to use properties files<BR>
- we don't use them for multilanguage functionality at all, I can't see why<BR>
you would need to unless you wanted to localize the workplace itself, and<BR>
XML structured content creation dialogs.<BR>
<BR>
The benefit of using siblings (with the content for each language all in the<BR>
same page), is that when an editor edits the page, they can use a dropdown<BR>
to flip between the different languages on the same page. To be honest there<BR>
isn't a huge amount of benefit that I can see.<BR>
<BR>
The issue I was pointing out is that if translatable stuff is put in<BR>
folder/page properties (eg the Title property), then this is hard for<BR>
unskilled editors to deal with, since they have to go and change them in<BR>
each language using the workplace explorer (rather than the page editor<BR>
language dropdown).<BR>
<BR>
Beware, using siblings also has a couple of disadvantages - eg when a page<BR>
is edited in one language, it shows up as edited in all the other languages<BR>
in the workplace and in the Project Management summary, which is quite<BR>
confusing.<BR>
<BR>
It sounds like you're not using siblings, and have entirely separate folder<BR>
branches for the different locales, which is another valid way of doing it.<BR>
<BR>
Steve<BR>
<BR>
----------------------------------------------------------------------<BR>
<BR>
Date: Mon, 15 Sep 2008 12:16:44 +0200<BR>
From: "Carl Alex Friis Nielsen" <<a href="cfn@kb.dk">cfn@kb.dk</a>><BR>
Subject: Re: [opencms-dev] OpenCMS website localization<BR>
To: "The OpenCms mailing list" <<a href="opencms-dev@opencms.org">opencms-dev@opencms.org</a>><BR>
Message-ID: <<a href="8CBCCEE2D9CECF4CAFFF17DE494047A8BEC66E@exchange-2.kb.dk">8CBCCEE2D9CECF4CAFFF17DE494047A8BEC66E@exchange-2.kb.dk</a>><BR>
Content-Type: text/plain; charset="iso-8859-1"<BR>
<BR>
No - the content resides in the resource.<BR>
The locale property can be set by simply having all material that shall be<BR>
available for a given<BR>
locale under a folder with its locale property set to the desired locale.<BR>
It really is quite simple to set up and use.<BR>
<BR>
-----Original Message-----<BR>
From: <a href="opencms-dev-bounces@opencms.org">opencms-dev-bounces@opencms.org</a><BR>
[<a href="mailto:opencms-dev-bounces@opencms.org]On">mailto:opencms-dev-bounces@opencms.org]On</a> Behalf Of Martin Wunderlich<BR>
Sent: Monday, September 15, 2008 11:57 AM<BR>
To: The OpenCms mailing list<BR>
Subject: Re: [opencms-dev] OpenCMS website localization<BR>
<BR>
<BR>
OK, but that means the content needs to be externalised to properties files,<BR>
right? In our case, we non-technical people creating the original English<BR>
content and they wouldn't necessarily know how to work with properties<BR>
files.<BR>
<BR>
Cheers,<BR>
<BR>
Martin<BR>
<BR>
<BR>
On 15/09/2008 10:35, "Carl Alex Friis Nielsen" <<a href="cfn@kb.dk">cfn@kb.dk</a>> wrote:<BR>
<BR>
<BR>
<BR>
You have multiple locales in the same resource.<BR>
Which locale is displayed depends on the locale property of the resource.<BR>
Different siblings can have different locale properties.<BR>
The properties can be inherited from the folder hierachy in the VFS.<BR>
<BR>
AFAIK this is a very widely used way to handle multilingual content in<BR>
OpenCms.<BR>
<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: <a href="opencms-dev-bounces@opencms.org">opencms-dev-bounces@opencms.org</a> [<BR>
<a href="mailto:opencms-dev-bounces@opencms.org]On">mailto:opencms-dev-bounces@opencms.org]On</a> Behalf Of Martin Wunderlich<BR>
Sent: Monday, September 15, 2008 11:11 AM<BR>
To: The OpenCms mailing list<BR>
Subject: Re: [opencms-dev] OpenCMS website localization<BR>
<BR>
Hi Steve,<BR>
<BR>
Are you saying that you're using the siblings mechanism for content in<BR>
different languages? How would that work? AFAIK, siblings are basically<BR>
pointers to the exact same content.<BR>
<BR>
About the web services interface, does OpenCms somehow support SOAP calls<BR>
at the moment?<BR>
<BR>
Kind regards,<BR>
<BR>
Martin<BR>
<BR>
<BR>
On 15/09/2008 10:01, "Steve Bryan" <<a href="steve@bright-interactive.com">steve@bright-interactive.com</a>> wrote:<BR>
<BR>
<BR>
<BR>
<BR>
Hi<BR>
<BR>
One usability problem we found is that when an editor creates a page in one<BR>
language folder (eg under en), the siblings do not get created<BR>
automatically<BR>
in the other language folders (which for us is generally required except<BR>
for<BR>
the odd case that the pages are only in one of the locales).<BR>
<BR>
One solution to this would be to customize OpenCms to add a<BR>
'copy-to-all-locales' function, either on the create dialog or (more<BR>
easily)<BR>
as a separate context menu function. The latter can be done by adapting the<BR>
regular copy function to copy out siblings to the other locale folders.<BR>
<BR>
An associated problem (which I think Martin is referring to), is that title<BR>
& navtext properties etc would normally need to be translated as well as<BR>
elements of pages and structured types. One work-around for this, is to add<BR>
title and nav-text page elements, and use them instead of the properties in<BR>
the template navigation. The ideal is to ensure that all properties are<BR>
locale independent (and hence a straight sibling copy does the job). Any<BR>
locale dependent stuff should go in page elements. Then only the page<BR>
bodies<BR>
need translation.<BR>
<BR>
After that, we have a batch translation system that sounds like a much less<BR>
advanced version of Martin's :-) - ie exporting pages, getting the<BR>
translation company to fill in the control code, then re-importing. The web<BR>
services idea sounds good.<BR>
<BR>
Steve<BR>
<BR>
<BR>
<BR>
<BR>
_______________________________________________<BR>
This mail is sent to you from the opencms-dev mailing list<BR>
To change your list options, or to unsubscribe from the list, please visit<BR>
<a href="http://lists.opencms.org/mailman/listinfo/opencms-dev">http://lists.opencms.org/mailman/listinfo/opencms-dev</a><BR>
<BR>
</SPAN></FONT></BLOCKQUOTE>
</BODY>
</HTML>