Mario Menezes wrote: > Hi, > > I found some interesting things: > 1. Localizer has different code for Portuguese/Brazil, and this is > causing some confusion in CPS/Zope. > a. CPS uses pt_BR as language code for Brazilian Portuguese. > b. Localizer/languages.txt uses pt-BR > 2. I had put my calendar.po for Brazilian Portuguese in pt_BR folder > under CalZope/locales. As a result, Localizer couldn't find it, because > it didn't know pt_BR language code, only pt-BR. Localizer never finds it. It's not involved in the translation of CalZope. It is involved in a little bit of translation from CPSSharedCalendar (the files under i18n), but those files are explicitly imported during install. > a. I edited the languages.txt file under Localizer, changing > Brazilian code to pt_BR. > I got more translated messages now, but there are still some > mysterious untranslated messages, coming from nowhere :-) Not that strange, because the i18n for the calendar is a bit complex. Most things are in CalZope/locales. This uses the Zope3 translation. The menus and subscriptions are part of the CPS integration. Therefore, they are translated in CPSSharedCalendar/locales. Lastly, there are some labels that CPS currently must have in the Default domain. These are in CPSSharedCalendar/i18n. > 3. Strange is that I could only get my translations with Konqueror. > Firefox and Opera refuse to show them; of course, tried clear cache, > reloaded several times, changed language preferences, put pt_BR on top, > but nothing worked! That's very strange. Try installing french, and putting FR on top and see if you get a french translation, to verify if it is only pt_BR that is the problem, or if it is a general problem. -- Lennart Regebro, Nuxeo http://www.nuxeo.com/ CPS Content Management http://www.cps-project.org/
Hosting: Nuxeo: Zope service provider