CMS language strategy?

[Eirikur Hrafnsson <ei...@idega.is>]

I'm curious to know what strategy other Slide users creating content 
management systems have taken in linking together translated version of 
the "same" article.
e.g. I write an article in english and then someone does a Swedish 
version of it but that is a different file in Slide.

I have thought about using the file names as identifiers e.g. english 
version would be called "article_27_EN.article" and the swedish version 
"article_27_SE.article".
But is there a "standard" webdav way of handling this "problem"? Or a 
best way someone has discovered?

Best Regards

Eirikur S. Hrafnsson, eiki@idega.is
Chief Software Engineer
Idega Software
http://www.idega.com


---------------------------------------------------------------------
To unsubscribe, e-mail: slide-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: slide-user-help@jakarta.apache.org

Re: CMS language strategy?

[delbd <de...@oma.be>]

Hello,

we ran into this problem at work because we have multilingual documents 
content and multilingual document metadatas, however documents needed to be 
manipulated as a whole.

Before using slide we were using a commercial CM. In this commercial CM we 
used the following way for multilingual content:
- create an 'empty' document (named metadocument)
- create a multilingual category
- link metadocuments to that category (so we know they are metadocuments)
- add a translation in each language as child docs of the meta documents
- each translation is linked to a language category (FR, NL, EN) (so we know 
in which language it's translated)
- generic metadatas were stored in metadocument and  translated ones (like 
title) were stored in the language document.

This could be achieved with slides (using linknodes) i think.

However, we are thinking about using some other way now, This looks more easy
to do the following:
- when user wants file.pdf, give him file_userlanguage.pdf (file_en.pdf for 
english user)  or file.pdf if translation does not exist. 
- Same thing for metadatas. 

This appear to be more consistent with the java localisation of properties 
files and easier to manipulate, though we still need a metadocument to 
manipulate the publication.

Am opened to discussions about it. 

Le Vendredi 4 Février 2005 16:18, Eirikur Hrafnsson a écrit :
> I'm curious to know what strategy other Slide users creating content
> management systems have taken in linking together translated version of
> the "same" article.
> e.g. I write an article in english and then someone does a Swedish
> version of it but that is a different file in Slide.
>
> I have thought about using the file names as identifiers e.g. english
> version would be called "article_27_EN.article" and the swedish version
> "article_27_SE.article".
> But is there a "standard" webdav way of handling this "problem"? Or a
> best way someone has discovered?
>
> Best Regards
>
> Eirikur S. Hrafnsson, eiki@idega.is
> Chief Software Engineer
> Idega Software
> http://www.idega.com
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: slide-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: slide-user-help@jakarta.apache.org

-- 
David Delbecq
Royal Meteorological Institute of Belgium 

---------------------------------------------------------------------
To unsubscribe, e-mail: slide-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: slide-user-help@jakarta.apache.org