#2368: [PATCH] Colelct translatable string in explicit gettext function calls in
Genshi templates
-------------------------+--------------------------------------------------
 Reporter:  Chris Arndt  |       Owner:  Chris Arndt           
     Type:  enhancement  |      Status:  new                   
 Priority:  normal       |   Milestone:  1.1                   
Component:  I18n         |     Version:  1.1 HEAD              
 Severity:  normal       |    Keywords:  i18n, genshi, tg-admin
-------------------------+--------------------------------------------------
 A while ago I committed a patch (r5799) for i18n in TG 1.1 that allowed
 translatable strings in Genshi templates to be collected with "tg-admin
 i18n collect".

 The current function does not collect any strings within Python
 expressions, because with the Genshi Translator filter you do not need to
 wrap your translatable strings in gettext function calls.

 This works good so far, since the Translator filter is automatically added
 in the Genshi renderer by TurboGears. But in the interest of easy porting
 of Kid templates it would be nice to also support strings in gettext
 function calls. So I created the attached patch to collect them.

 But it will currently lead to an error when you actually use gettext
 function calls (e.g. ``${_(u'Translatable string')}``) in your Genshi
 templates, because the gettext function (``'_'``) is not injected into the
 template namespace yet. See #2039 for this task.

-- 
Ticket URL: <http://trac.turbogears.org/ticket/2368>
TurboGears <http://www.turbogears.org/>
TurboGears front-to-back web development

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "TurboGears Tickets" group.
This group is read-only. No posting by normal members allowed.
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/turbogears-tickets?hl=en?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to