Translations need updating on Plone 3 version

[GoogleCodeExporter]

This may be a question of syncing the plone 3 and 2.5 buildouts, but I
noticed that there are places in the 3.0 version that do not have
translations that do exist in the 2.5 one. 

One example (please log others on here so people can take care of them) is
the "GetPaid Setup" page (with links) and the "Payment Options" screen
where there is info about accepted credit cards, anonymous checkout. 

Original issue reported on code.google.com by cjj.ifpe...@gmail.com on 30 Nov 2007 at 4:36

[GoogleCodeExporter]

Note, I was looking for the Spanish tranlsation above...

I also noticed the "Same as billing" button on the checkout screen needs 
translation.
In 3.0, could also be in 2.5 since this is a new feature. 

Original comment by cjj.ifpe...@gmail.com on 30 Nov 2007 at 4:42

[GoogleCodeExporter]

the new subtotal area on checkout needs to have translations also (also a new
feature, so both versions)

Original comment by cjj.ifpe...@gmail.com on 30 Nov 2007 at 4:57

[GoogleCodeExporter]

I want to take a look at this.  Feel free to be quicker. :)

Original comment by maurits.vanrees on 12 Dec 2007 at 4:44

[GoogleCodeExporter]

I have not actually looked at this yet (and I should be sleeping now ;-)).  But 
on a
default Plone 3 site you will only see one language.  If the browser used to 
create
the Plone Site had English as preferred language you will see only English.  If 
the
browser preferred Spanish all visitors would see only Spanish.  You can select 
more
languages either in the languages control panel within Site Setup or in
portal_languages in the ZMI.

Can this have been the problem?

If not, then that is strange.  For example the PloneTranslations product that is
shipped with Plone 3 is usable without problems in Plone 2.5 and the other way
around.  At least as far as I know whenever a bugfix release of 2.5 or 3.0 
comes out,
that latest PloneTranslations trunk is just tagged and shipped with it.

So if translations from plone get paid do not work in 3.0 I would not be 
surprised if
this is a core Plone bug.  But I will not point my blaming fingers immediately. 
:)

/me is off to bed.

Original comment by maurits.vanrees on 13 Dec 2007 at 1:47

[GoogleCodeExporter]

ah...oops. thanks for the clarification. i didn't know how plone3 handled it. i 
will
try adding the language info and test again. 

Original comment by cjj.ifpe...@gmail.com on 13 Dec 2007 at 1:44

[GoogleCodeExporter]

Okay, I see that the problem is real.  I partly fixed this by adding the correct
domain in browser/settings.zcml.  This fixes the main setup page.  But more 
spots
remain, like the one mentioned: @@manage-getpaid-payment-options is better 
translated
in 2.5 than in 3.0.  I am out of ideas, so I opened a thread on the plone i18n 
list
asking about that:

http://comments.gmane.org/gmane.comp.web.zope.plone.internationalization/3028

The "Same as billing" button does not show up translated as it has not yet been
translated in most languages.  I just added it in Dutch and it works.

Original comment by maurits.vanrees on 13 Dec 2007 at 11:26

[GoogleCodeExporter]

Did someone find anything about this?
I'm trying to translate parts of PloneGetPaid/cart.py (such as "Tax", 
"Shipping",
"N/A" in renderExtra()), but it doesn't seem to work.
For example, if I print _(u"N/A"), the string is not translated even if other 
strings
in the template are translated.
I suspect this has something to do with this bug...
(And in fact, it's not the first time I have trouble translating strings from 
python
files...)

Original comment by jpho...@gmail.com on 25 Apr 2008 at 5:51

[GoogleCodeExporter]

Ok, it seems that my problem was just that messages created by _(x) are 
translated by
the template engine, so strings in python code need to be translated manually 
with
zope.i18n.translate(msg, context=context.request) if they are not passed intact 
to
the template.

I still have problems translating parts of the interface, but I'll open another 
bug
about that.

Original comment by jpho...@gmail.com on 28 Apr 2008 at 7:58