Dear Pylonistas && Pyramistas, I'm in the process of evaluating web frameworks for some simple projects, that highly depend on forms and i18n. For the time being, I tend to use the Pyramid framework, which is a pleasure to work with so far. Great work, guys.
ATM, I'm stuck with some Chameleon rendering and i18n interaction issue. I started from here: http://docs.pylonsproject.org/projects/pyramid_tutorials/en/latest/humans/forms_schemas/step02/index.html and mangled it up to the point, where the form is translated correctly apart from a small part of site_view.pt: Before: <p tal:condition="values">Valid form values: ${values.name} and ${values.shoe_size}.</p> Became: <p tal:condition="values" i18n:translate="valid_values">Valid form values: ${values.name} and ${values.shoe_size}.</p> Funnily, the expression is translated and displayed "correctly", but is simply the values.* replacements missing, unlike the untranslated version. I experimented with various tal:replace constructs for the values.* expressions, which all resulted in ${values.name} for the translation string, and consequently with the same rendering result, hence the question: how do I formulate this <p> in a way, that translation finally works. The "whole" project is available here: ftp://urpla.net/formtest-0.0.tar.gz Thanks in advance, Pete P.S: Versions in use: Python-2.7.3 pyramid-1.4.3 colander-1.0a5 Chameleon-2.11 deform-0.9.7 -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/pylons-discuss. For more options, visit https://groups.google.com/groups/opt_out.
