<HTML>
<HEAD>
<TITLE>Re: [opencms-dev] OpenCMS website localization</TITLE>
</HEAD>
<BODY>
<FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:12pt'>OK, but that means the content needs to be externalised to properties files, right? In our case, we non-technical people creating the original English content and they wouldn’t necessarily know how to work with properties 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>
</SPAN></FONT><BLOCKQUOTE><SPAN STYLE='font-size:12pt'><FONT FACE="Arial">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>
</FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial"> <BR>
</FONT><FONT FACE="Arial">AFAIK this is a very widely used way to handle multilingual content in OpenCms.<BR>
</FONT></SPAN><BLOCKQUOTE><SPAN STYLE='font-size:12pt'><FONT FACE="Calibri, Verdana, Helvetica, Arial"> <BR>
</FONT><FONT FACE="Tahoma, Verdana, Helvetica, Arial">-----Original Message-----<BR>
<B>From:</B> <a href="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>On Behalf Of </B>Martin Wunderlich<BR>
<B>Sent:</B> Monday, September 15, 2008 11:11 AM<BR>
<B>To:</B> The OpenCms mailing list<BR>
<B>Subject:</B> Re: [opencms-dev] OpenCMS website localization<BR>
<BR>
</FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial">Hi Steve, <BR>
<BR>
Are you saying that you’re using the siblings mechanism for content in different languages? How would that work? AFAIK, siblings are basically pointers to the exact same content. <BR>
<BR>
About the web services interface, does OpenCms somehow support SOAP calls 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>
</FONT></SPAN><BLOCKQUOTE><SPAN STYLE='font-size:12pt'><FONT FACE="Calibri, Verdana, Helvetica, Arial">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 automatically<BR>
in the other language folders (which for us is generally required except 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 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 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>
Date: Fri, 12 Sep 2008 11:23:52 +0100<BR>
From: "Martin Wunderlich" <<a href="mwunderlich@salesforce.com">mwunderlich@salesforce.com</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="C4F001C8.2D0D%mwunderlich@salesforce.com">C4F001C8.2D0D%mwunderlich@salesforce.com</a>><BR>
Content-Type: text/plain; charset="iso-8859-1"<BR>
<BR>
Hi David,<BR>
<BR>
We currently have 17 different locales on our website (5 of them English<BR>
language) and it works somehow like this:<BR>
<BR>
* The localised sites are located under sub folders of the main domain,<BR>
whereby the subfolder name consists of the ISO country ID, e.g.<BR>
www.salesforce.com/es for Spanish.<BR>
* Some locale specific content is externalised to properties files, but<BR>
not the main body text of the pages.<BR>
* Translation is generally a one way street from en-US to all the other<BR>
locales.<BR>
* To get a web page translated, we run an export that picks up the<BR>
respective pages, based on a custom property that we have included in the<BR>
templates. The export file then gets dumped to an FTP server, from where it<BR>
is picked up every so often by the translation management system (feels a<BR>
bit ancient, IMHO; this should happen in real time through a web services<BR>
interface). We do some automated tweaks to the manifest file of the export<BR>
file (replace locales IDs and such) and then import back into OpenCms.<BR>
<BR>
Some things that I really miss are better support for image localisation,<BR>
the web services interface mentioned above, and a better OpenCms interface<BR>
for sending files for translation. Also, it would be great to have a WYSIWYG<BR>
interface for externalising information to properties files, so that<BR>
non-technical content editors can create properties on the fly.<BR>
<BR>
Cheers,<BR>
<BR>
Martin<BR>
<BR>
<BR>
On 01/09/2008 11:41, "David Valls roure" <<a href="david.valls@sogeti.com">david.valls@sogeti.com</a>> wrote:<BR>
<BR>
Hi All,<BR>
<BR>
i'm having some issues regarding web site localization and I want to<BR>
review if i'm doing well...<BR>
<BR>
This are my steps:<BR>
1.- new folder www at /sites/default<BR>
1.1.- properties-advanced-locale: en<BR>
2.- some content-> pages with free text<BR>
3.- new folder news at www<BR>
4.- add some news inside<BR>
<BR>
ok, now i have my website in english<BR>
<BR>
How to localize?<BR>
<BR>
1.- copy all, even siblings from www to www_es<BR>
2.- Administration-> Merge pages -> from www 2 www_es<BR>
3.- Change locale-> www_es (include subfolders) from en 2 es<BR>
4.- Open website and traduce all...<BR>
That's what i've done.<BR>
<BR>
repeat this steps for other languages...<BR>
<BR>
The first thing i want to know if i'm doing well... because now i have<BR>
a problem: when i add content like pages with free text i can merge<BR>
and goon, but with news i cannot localize them... i can't copy them to<BR>
corresponding language folder...<BR>
<BR>
How do i create localized (multilanguage) sites?<BR>
How do i mantain localized (multilanguage) sites?<BR>
<BR>
Thanks in advice,<BR>
<BR>
David.<BR>
<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>
</FONT></SPAN></BLOCKQUOTE></BLOCKQUOTE><SPAN STYLE='font-size:12pt'><FONT FACE="Calibri, Verdana, Helvetica, Arial"><BR>
</FONT></SPAN></BLOCKQUOTE>
</BODY>
</HTML>