Hey there,
I came to the conclusion, that option number 1 works for the most of the cases. Since Magnolia is page centric per default you would have to internationalize the page properties too (to show internationalized menus etc). You also have to handle the case what should happen if there is no translation for some content. Additionally the content could be entered by different users (translator), how to manage security/user privileges in such a case (okay that's a minor issue).
So I think it would be best to create site trees for each language.
Someone could write a plugin (if there is a reasonable mechanism in magnolia) to diff the content trees against each other, or to manage your option 2.
But most of the time I would stick to option 1.

Best regards,
Richard Kogelnig

Chris Miner wrote:
Hi All,

Naturally I want a localized web site. Therefore all my content needs to be in several languages. I have read on this board and elsewhere that people are using a couple of approaches. They are either:
    1. creating complete site trees for each language
or
    2. creating dialogs which contain all attributes for every language

The first option seems the most compatible with Magnolia. Just need the one set of (possibly localized) dialogs, and everything else works the same. Can probably work in a little workflow, to make sure the sites stay roughly in sync. Each language tree would work independently of the others. The problem here for me is that it is too independent. I need to maintain the distinction between 1 story translated 7 times and 7 different stories that happen to be in 7 languages. So I am not sure this approach would work well for me. I think it is best to rely on the jcr:uuid for uniqueness.

With the second approach I ran into problems right away. First I wanted a tab containing other tabs in my dialog. That way I could have a General Properties tab containing several language tabs. I couldn't get this to work. Perhaps tabs only work at the dialog level and you can't add them to other tabs? Anybody done that successfully before?

I suppose I could create a different dialog for each language, but then I'd probably need a paragraph for each language too, so that the right dialog would come up during edit. Also impractical.

Anyway, I'd appreciate reading any feedback or suggestions people may have on this penetrating and exceedingly interesting topic.

Chris

----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------








----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------

Reply via email to