Hello Tobías, thanks for your answer. 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 <[EMAIL PROTECTED]> 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. >> >>
