Localisation LiveSite 7.3

Hi
New to LiveSite and going through the docs struggling to find best practise, well to be fair any practise on the best way to handle local renditions and url's.

Our requirement is to support the following scernario

url of the forms

en.GB project.domain/xx > proxied to projectName.domain/project-en-GB/xx
fr.FR.project.domain/xx > proxied to projectName.domain/projectfr-FR/xx
fr.project.domain/xx > proxied to projectName.domain/project-fr/xx
etc

We will have a limited number of sites but would like to support any locale. having the most relevant site served for a particluar locale. For example

fr.PL would be served from the fr site.

What is LiveSites solution to this (common?) usecase.

cheers lee

Find more posts tagged with

Comments

RonaldV

Hi Lee,

using the ootb GCM (see the ts-user-manual) your editors can be assisted in creating and managing local version of a .page, content-dcr and/or a sitemap. Please read the chapter in the manual on this for more details.

However Teamsite/livesite has no mechanism to handle the locale-versions during runtime. Like a fall-back if a requested locale is not available. And also it is rather weak in using a customized url-schema like you describe in your question. Further it will not 'detect' ootb your current locale (based on what ever information available).

I hope this helps.

leec

Thanks for the reply Ronald

What is best practise around making livesite locale aware ? Also is url re-writing inbound and outbound supported. Again the docs are really vague on both of the above.

Apologies if i'm missing something obvious but i'm walking in treacle at the moment

RonaldV

Thanks for the reply Ronald

What is best practise around making livesite locale aware ? Also is url re-writing inbound and outbound supported. Again the docs are really vague on both of the above.

Apologies if i'm missing something obvious but i'm walking in treacle at the moment

Hi,

"all" docs on livesite are very vague in deed!

The livesite runtime (e.g the frontend) is not 'locale aware' and does not support url rewriting in any way. You have to create the code for this yourself.

F.i. by creating a filter that executes before the livesite code steps in and by parsing the generated html in some post-controller-thingy to replace any links. Not very easy to do.

leec

from livsite dev manual best practise section (**** knows why it is in their)

"If you are working in a globalized content management context, you must
maintain a site family, that is, a master site as well as numerous child sites
localized for different languages and regions. Each language or language/region
pair is called a locale. Locales can be used for many purposes. In site families,
locale information can be used to direct visitors to either the master site or a
localized rendition of the master site.
You can determine the appropriate locale to which to direct site visitors with
configurable criteria called locale determiners. Determiners can be explicit and
visible to end users, such as national flags or a language selection menu on a
Web page, or implicit, such as the locale identified in a site visitor’s session.
In Java, locales are represented by instances of java.util.Locale. Each
locale has a string representation similar to an IETF language tag. Refer to the
Locale Javadoc for more information"

It goes onto say you can configure locale determiners? is this sounds at least part of my solution. Does any one have an example configuration??