Ticket #13378 (confirmed Bug)
Adding new (translated) criteria to plone.app.collection force to translate also group
Reported by: | keul | Owned by: | vincentfretin |
---|---|---|---|
Priority: | minor | Milestone: | 4.x |
Component: | Internationalization | Version: | 4.2 |
Keywords: | Cc: | keul |
Description
I need to add a new criteria, for a new index.
Following plone.app.querystring example I create this registry.xml file:
<registry xmlns:i18n="http://xml.zope.org/namespaces/i18n" i18n:domain="my.domain"> <records interface="plone.app.querystring.interfaces.IQueryField" prefix="plone.app.querystring.field.eventType"> <value key="title" i18n:translate="">Event type</value> <value key="description" i18n:translate="">Possible type of events</value> <value key="enabled">True</value> <value key="sortable">True</value> <value key="operations"> <element>plone.app.querystring.operation.selection.is</element> </value> <value key="vocabulary">my.vocabularies.AAA</value> <value key="group" i18n:domain="plone" i18n:translate="">Text</value> </records> </registry>
Using my own translation domain works. Problem is that I don't want to create also a new category/group, so I'm using there the "plone" domain (trying to reuse existing translation for it).
The problem is that this isn't working. The criteria is added in a new category ("Text", untranslated) while other default criteria are in the translated group ("Testo", in italian).
Solutions:
- To see also my new criteria in this group I'm forced to translate also the "group", which is weird because in this way I can only translated in my own language.
... <value key="group" i18n:translate="">Text</value> ...
- Probably, using only "plone" works, but I found this not a proper way to manage this issue.
Change History
Note: See
TracTickets for help on using
tickets.