|
|
Rank: Newbie
Joined: 4/13/2007
Posts: 3
|
Hi all,
I have a multi-language site that it´s working great (created one sub-folder for each language and added content to each one).
Now, i have some content that don´t need to be translated (news section for example). This section needs to be the "same" on all languages.
My problem is: I build the site menu/sub-menus by using a macro/xslt, so i actually need to have the content replicated on each language.
It is possible to create a "content" that is linked to another content? (think like a shortcut on windows).
Any other way?
Thanks in advance.
|
|
Rank: Devotee
Joined: 8/14/2006
Posts: 212
|
As far as i know, its not possible. I wanted something myself, but i dont think there is a easy way to do that. If possible, it would proparly not be done before 4.0, maybe 3.1?
Please add it to codeplex :)
Signatures suck. No reason to have one.
|
|
Rank: Addict
Joined: 7/19/2006
Posts: 815
Location: Århus, Denmark
|
For your specific problem it might be worth making a new tempalate for your news section that uses another xslt fil that gets the news content from a specific node instaed of currentPage ?
|
|
Rank: Devotee
Joined: 7/28/2006
Posts: 57
|
I think it would be possible using existing functionality. These are just some ideas!
Option 1: Let's say you have a document type 'Text Page'. This is where all your content is stored, and you have the following arrangement
/en/home-page
/en/products
/en/product/product-A
/en/product/product-B
/en/news
/en/news/item-A
then in french...
/fr/home-page
/fr/products
/fr/product/product-A
/fr/product/product-B
/fr/news
You could create another type of document called 'Shortcut' which only has one property: content picker [shortcutPage]. You can then create an item of type 'Shortcut' in the French versions news item...
/fr/news/item-A ... content picker selects item /en/news/item-A
You then modify the XSLT's to set the current page node to either $currentPage or ./data [@alias='shortcutPage'] if that is defined.
Option 2: You could let the XSLTs do all the work. This would be my favoured approach (I do something similar on another multi-lingual site). Pseudo code would be something like:
IF $currentPage/data [@alias='bodyText'] = '' THEN
take find [ replace($currentPage/@nodeName, '/??/', '/en/') ] in the tree and show that node's bodyText...
The downside with this method is that you'd need the same name for each item - which is poor SEO for non-English versions.
Hope that gives you some ideas... ??
S.
Bawden Quinn Associates, UK
|
|
Rank: Newbie
Joined: 4/13/2007
Posts: 3
|
Thanks! I will try that!!
|
|
|
Guest |