关于GenericSetup配置文件的翻译

In your GenericSetup profile you can have several xml files. In someof these it makes sense to do translations. In most of those cases itonly helps to use the plone domain. Let's try out most of thexml files, at least the ones contained in CMFPlone itself.

• actions.xml: use your own domain. Example<object name="ducktest" meta_type="CMF Action" i18n:domain="collective.ducks"> <property name="title" i18n:translate="">Duck Test</property> <property name="description" i18n:translate="">Action: test a duck</property> ... </object>
Note that when you go to the portal_actions tools in the ZMI, youwill see an i18n domain specified for each action.
• [align=left]catalog.xml: no i18n needed[/align]
• [align=left]componentregistry.xml: no i18n needed[/align]
• [align=left]contenttyperegistry.xml: no i18n needed[/align]
• controlpanel.xml: use your own domain. Example<?xml version="1.0"?> <object name="portal_controlpanel" meta_type="Plone Control Panel Tool" i18n:domain="collective.ducks" xmlns:i18n="http://xml.zope.org/namespaces/i18n"> <configlet title="Duck Configuration Panel" action_id="Duck" appId="Duck" category="Products" condition_expr="" icon_expr="string:$portal_url/duck_icon.png" url_expr="string:${portal_url}/prefs_install_products_form" visible="True" i18n:attributes="title"> <permission>Manage portal</permission> </configlet> </object>
• [align=left]cssregistry.xml: no i18n needed[/align]
• [align=left]diff_tool.xml: no i18n needed[/align]
• [align=left]factorytool.xml: no i18n needed[/align]
• [align=left]jsregistry.xml: no i18n needed[/align]
• [align=left]kssregistry.xml: no i18n needed[/align]
• [align=left]mailhost.xml: no i18n needed[/align]
• [align=left]memberdata_properties.xml: no i18n needed[/align]
• [align=left]metadata.xml: no i18n needed[/align]
• [align=left]portal_atct.xml: use the plone domain. Note that this has noinfluence on the Collections panel in Site Setup. It is only usedon the edit and criteria pages of a Collection.[/align]
• [align=left]portlets.xml: use the plone domain.[/align]
• [align=left]properties.xml: no i18n needed[/align]
• [align=left]propertiestool.xml: no i18n needed[/align]
• [align=left]rolemap.xml: no i18n needed[/align]
• [align=left]skins.xml: no i18n needed[/align]
• [align=left]toolset.xml: no i18n needed[/align]
• [align=left]types: use your own domain[/align]
• [align=left]viewlets.xml: no i18n needed[/align]
• [align=left]workflows: use the plone domain[/align]

Combining i18n and locales in your own package So: for your owndomain you should always use either an i18n or a localesdirectory.
You should put your own domain in a locales directory and someextra translations for the plone domain in an i18n directory.