Re: [Nuxeo-localizer] Announcement: HowTo for CMF and Localizer

[Juan David Ibáñez Palomar]

It will be possible to use Localizer as the back-end for the i18n
namespace of ZPT, Jean-Paul Smets already started to work on this
direction.



Myroslav Opyr wrote:

> Chris Herrnberger wrote:
>
> > On September 5, 2002 04:29 pm, Myroslav Opyr wrote:
> >
> > > Hope I didn't messed everything up,
> > >
> > > m.
> > > P.S. If you are interested in Plone i18n effort you can visit
> > > http://collective.plone.org/i18n
> > >   
> >
> > No not at all, thanks for the information. I am on the list too just 
> > lurking however. Once a plone french is available I think I will do 
> > it like so to keep it simple
> >
> > |--------------------------------------------|
> > plone-fr     plone-en
> >
> > The problem with this structure is that the user is limited to one 
> > instance for the duration of the session. I was hoping to use 
> > localizer to allow the user to switch between instances of en-fr but 
> > this would require extending localizer to where its has not been 
> > befor me thinks.
> Ok. Now I'll give more details.
>
> Plone has all translations of its interface compiled in .mo files in 
> i18n folder. It have different translations there. In your case you 
> need at least plone-en-ua.mo and plone-fr-ca.mo. To decide which 
> language to use for displau of Plone UI there is Language Negotiator 
> which picks up the target language from request/user_language and 
> request/HTTP_ACCEPT_LANGUAGE. This will be improved later but it is in 
> the way I've described right now.
>
> For content you can use Localizer of course. Localizer has more 
> sources for it's Negotiator (cookie, etc.).
>
> You can make these Negotiators to work in sync or separately (for 
> instance UI language to be per-user preference and content language 
> contolled by application/portal logic).
>
> > I basically need to build a dual language CMF based site. Any 
> > suggestions would be most appreciated as this is first attempt at 
> > this..:)
> So if you understood what I tried to explain, there is no problem to 
> build dual-language Plone based CMS. Your task will be to develop 
> dual-language content objects and make them play nicely with Plone 
> Workflow.
>
> Regards,
>
> m.



--
J. David Ibáñez, http://www.j-david.net
Software Engineer / Ingénieur Logiciel / Ingeniero de Software