jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sascha Rodekamp <sascha.rodekamp.lynx...@googlemail.com>
Subject Re: multilanguage best practices
Date Thu, 01 Sep 2011 09:23:26 GMT
Hi,
so you have one node for all locals? Why you use nt:file/ nt:folder?



2011/9/1 Sverker Abrahamsson <sverker@abrahamsson.com>

> Hi
> The approach I've taken is to extend nt:folder and nt:file to add an i18n
> child node with the different locales.
> Best regards
> Sverker
>
> > -----Original Message-----
> > From: Sascha Rodekamp [mailto:sascha.rodekamp.lynx.de@googlemail.com]
> > Sent: den 1 september 2011 11:07
> > To: users@jackrabbit.apache.org
> > Subject: multilanguage best practices
> >
> > Hi David, hi List
> >
> > i had some thoughts about the same problem. What is best practice for
> > multi
> > language nodes.
> >
> > Maybe you can share some experience you made during the last month with
> > your
> > solution?
> >
> > I prefer the "One Tree with Translation" solution, because if i have
> > i.e.
> > product contents in different languages it is possible to switch
> > between the
> > languages and simply determine a fallback.
> >
> > A Product Gizmo52 can have a description in eng, de, fr the node tree
> > could
> > look like:
> >
> > /products/gizmo52/eng
> > /products/gizmo52/de
> > /products/gizmo52/fr
> >
> > I could also easily determine which description languages are available
> > for
> > the product gizmo52 (more easily than with a different tree for each
> > language).
> >
> > I also thought of a proper way to map this structure to OCM classes.
> > I.E. a content object with a collection of language objects?!
> >
> > What do you think?
> >
> > Cheers
> > Sascha
>
>


-- 

Sascha Rodekamp
    Visit the new german OFBiz Blog: http://www.ofbiz.biz
    Lynx-Consulting GmbH
    Johanniskirchplatz 6
    D-33615 Bielefeld
    http://www.lynx.de

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message