On 1 June 2011 10:11, george hu <[email protected]> wrote: > Although the issue is fixed, but it reminds me the following points: > 1. Is there a better way to deal with this issue? Since it seems too tricky > to spot the problem, either it should be documented or there must be a fix > in the chameleon zpt.
Which version of Chameleon is this? > 2. For the <br i18n:name="break"/> part, it is missed from the documentation > of chameleon and pyramid. Finally, I found "Internationalization (i18n) For > Developers" in the Plone documentation. It has more detail information about > the i18n of zpt. Although it doesn't mention the same issue as we > encountered here, it is far more completed and practical. Maybe we can > improve the i18n chapter of pyramid, otherwise people like me with none or > little zpt experience will be scratching head for hours. Try this: http://pagetemplates.org/docs/latest/reference.html#i18n-name Meanwhile, I've considered whether expressions like ${...} should automatically become i18n:name blocks, e.g. ${1}, ${2} and so forth for each unnamed apperance (that is, if there's an enclosing i18n:translate statement). \malthe -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
