Localization of .pages

Hi everyone,

I will try to be as clear as i can. I have two sites,

en_FR
en_US

In the en_FR site, i have a .page name "contact.page".

In the en_US site, i have the same .page above but differently named as "contact us.page".

When browsing the en_FR site, by clicking on a link "US", i can view the same page i am in but in the en_US site and vice versa.

But since the page names are different, i am unable to view the "contact us.page" when clicking on the "US" link and vice versa.

My question is how can i correctly redirect the user to the correct page wherever locale i am in without using Java.

Thank you everyone.

Find more posts tagged with

Comments

Rick Poulin

There's a bidirectional pointer between localized variants in TeamSite, which is stored as an association between those two files. What you can do is have your workflow "save" this information as an extended attribute on your page files, which will then make it available to LSCS. Your component can then query LSCS to get the proper value for your locale toggle.

If you're generating pages in TeamSite, the same concept applies. You could build a post-processor in workflow that updates the value of the language toggle based on the association information.

In either case, you don't necessarily need Java on the runtime (although I'd recommend it for performance reasons), but you WILL need to write some workflow code.

Ashish_Sangal

Hi Sameer,

I can think of below mention appoches -

1) Approach -1

a) Add "File" Datum in the component where you are going to display the link.

b) Browse to the page in the component.

c) In your xsl code find the locale as -

<xsl:variable name = "locale">
    <xsl:value-of select = "substring-before(substring-after(//Datum[@Name = 'RequestHeaders'],'accept-language] = ['), ']')"/>
</xsl:variable>

d) Create the link using locale and page browsed.

Note: This approach gives you the flexiblity to link to any page you want.

2) Approach -2

a) You can use localization feature of LSDS.

b) Create one site only and save your DCR in the format - DCRNAME_locale.xml and DCRNAME.xml(this will be your base DCR which you have to attach on component)

eg. test_en-US.xml, test_fr-FR.xml and test.xml

c) More about this you can find in SitePublisher Developer Guide under "Creating Locale-based Content Using DCRs".

I had the same required and used the 1st approach. Smiley Happy