wcmqs multilingual

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

rmorant

I'm thinking the best way to do a multilingual site based in wcmqs.
Firstable i translated the alfresco/messages/common.properties to I10n named files, and was okay.
But for the documents… i was reading http://wiki.alfresco.com/wiki/Multilingual_Document_Support and i'm not sure to understand it.
Are there any examples available?
Anyway, may be more useful handle a site by language, each with his own documents and publication workflow.
In this case the locale should be part of WebSite data handled by WebSite Service in order to select the right site.
For now, I can only instantiate a webapp for each language and play with his context (/wcmqs, /wcmqs_es, /wcmqs_fr, …)

What is the best way to approach this problem?

Any suggestions are welcome.

thanks

bremmington

Funnily enough, this is a topic that we're talking about at Alfresco now with a view to providing an out-of-the-box solution in a future release. There is always a slight problem with multi-lingual sites, in that different people want to manage them in different ways. Some want to manage the content for each language as a separate site (different site structure), while others prefer to have a single site structure and have the appropriate translation selected at request time. As you say, in the first case you'd want to include the locale in the site-selection logic. In the second case you'd want to use the locale in the asset-selection logic.

The simplest approach if you wish to tackle this yourself is the one where you have a different website structure in the repo for each language. In this case you could perhaps use sub-domains to select the site you want:

  es.example.com
  fr.example.com
  en.example.com
‍‍‍‍‍

Another possibility worth considering is replacing the ApplicationDataInterceptor with your own implementation that takes the first segment of the requested path (the bit after "wcmqs" in the default installation) and appends it to the contextPath before calling websiteService.getWebSite(…). Just to clarify that a little, if a request comes in for:

    http://www.example.com/wcmqs/fr/news/global/article1
‍‍‍

then the call to getWebSite has the arguments: "www.example.com", 80, and "/wcmqs/fr"  (note the addition of "/fr" on the context path)

Similarly, the "/fr" is then stripped from the path that is subsequently passed into the call to webSite.getAssetByPath (so this method is passed "/news/global/article1"). It would be sensible to store the selected locale as a thread local too so that it can be used to select static text from the appropriate message bundle and can also be used by a tweaked implementation of the UrlUtils interface to produce outbound URLs in the correct format.

I don't know if that's a step too far for you right now, but, if so, it is something that we will address as early as we can.