jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ard Schrijvers" <a.schrijv...@onehippo.com>
Subject RE: David's Model and translation projects
Date Mon, 08 Sep 2008 08:55:44 GMT

> Tobias Bocanegra wrote:
> the nice thing about not having SNS and having a folder 
> structure for the language is that you can easily access it 
> via webdav. so you just drop your translated files in the 
> respective folder again, and your done. having SNS and meta 
> data just renders this impossible.

Unless you access the repository through a node that exposes the content through a filtered
mirror, only showing you the language you are looking for, but this is not default Jackrabbit
functionality I agree :-) 

-Ard

> 
> regards, toby
> 
> ps: imo SNS were a stupid idea (the way they were speced in jcr1.0.
> there are some efforts in jsr283 to correct this) and are 
> actually only valid to use when importing/exploding XML files 
> into the repository. but you always have troubles as soon as 
> you have SNS, and you need a lot of application logic to 
> handle and use them efficiently.
> 
> 
> >
> >  Just my 2 cents,
> >
> >  Regards Ard
> >
> >
> >
> >  > Fabián Mandelbaum wrote:
> >  > Approach #2 is indeed, natural, however the "problem" I 
> see  > with 
> > approach #2 is that it seems to break David's rule #1  > 
> (data 1st vs.
> >  > structure 1st) by imposing a fixed content structure to  
> > projects 
> > (for example, /common/ /en/ /fr/ /es/ /it/ etc.).
> >  >
> >  > I'm not saying I won't end doing things this way 
> (actually,  > it 
> > is so far my personal choice), I just wanted to know if  > 
> there was a 
> > way to do it in a way that conforms a bit more to  > 
> David's rule #1.
> >  >
> >  > Thanks again.
> >  >
> >  > Tobias Bocanegra escribió:
> >  > > hi,
> >  > > it certainly depends on your intention, but having a folder  > 
> > for each  > > language is imo the best approach. you might 
> have other 
> > resources  > > later (like images) that are language dependent that 
> > you can put in  > > the folder.
> >  > >
> >  > > regards, toby
> >  > >
> >  > > On 9/6/08, Fabián Mandelbaum <fmandelbaum@gmail.com> wrote:
> >  > >
> >  > >> Hello there,
> >  > >>
> >  > >>     I'm considering David's Model
> >  > >>  (http://wiki.apache.org/jackrabbit/DavidsModel) and was 
> > wondering  > >> how  would David handle translations of documents.
> >  > >>
> >  > >>     Let's say I have a file, for example: file.xml which
> >  > is written
> >  > >> in  English, and I want to store its translation to, 
> say, Spanish.
> >  > >> Which  would be the recommended storage model?
> >  > >>
> >  > >>     1) Common storage place
> >  > >>
> >  > >>     /content/file.xml (English version)
> >  > >>     /content/file-es.xml (Spanish version)
> >  > >>     /content/file-fr.xml (French version)
> >  > >>
> >  > >>     2) Folders for each language
> >  > >>
> >  > >>     /content/en/file.xml
> >  > >>     /content/es/file.xml
> >  > >>     /content/fr/file.xml
> >  > >>
> >  > >>     3) Workspaces for each language
> >  > >>
> >  > >>     /content/file.xml (in 'en' workspace)
> >  > >>     /content/file.xml (in 'es' workspace)
> >  > >>     /content/file.xml (in 'fr' workspace)
> >  > >>
> >  > >>     Other? My ears are open, Thanks in advance.
> >  > >>
> >  > >>
> >  >
> >  >
> >
> 

Mime
View raw message