Ticket #596 (new defect)

Opened 14 years ago

Last modified 14 years ago

CPS should use the Placeless Translation Service instead of the current Localizer

Reported by: madarche Owned by: trac
Priority: P2 Milestone: CPS 3.5.7
Component: CPSDefault Version: unspecified
Severity: normal Keywords: i18n
Cc:

Description

CPS should use the Placeless Translation Service instead of the current Localizer.

Change History

comment:1 Changed 14 years ago by madarche

  • dependson set to 595

comment:2 Changed 14 years ago by madarche

  • blocked set to 597

comment:3 Changed 14 years ago by jmorliaguet

hi!

I don't know if this can be implemented in CPSCore, but Localizer has a feature that allows to do language negociation but adding the language code after the portal root and before the first element of the path to change the portal's current language.

For instance:

mysite.com/cps/en/sections will display the site in English and mysite.com/cps/fr/sections will display the site in French

we are currently using this to do multilingual sites (with 2 roots of sections)

then it is the Apache rewrite rules that make it possible to set the language based on the url:

RewriteCond? %{REQUEST_URI} /cps/sections-sv(.*) RewriteRule? /cps/(.*)  http://localhost:9990/VirtualHostBase/http/localhost:80/cps/sv/VirtualHostRoot/_vh_cps/$1 [P,L]

RewriteCond? %{REQUEST_URI} /cps/sections-en(.*) RewriteRule? /cps/(.*)  http://localhost:9990/VirtualHostBase/http/localhost:80/cps/en/VirtualHostRoot/_vh_cps/$1 [P,L] Is it possible to do this kind of language negociation after Localizer is removed?

comment:4 Changed 14 years ago by fguillaume

  • Milestone changed from unspecified to CPS 3.5.0

We'll probably never get there, as in the meantime we'll be able to use Zope 3's i18n...

Note: See TracTickets for help on using tickets.