Changes between Version 31 and Version 32 of TracL10N

Timestamp:

Mar 23, 2007, 12:15:41 PM (17 years ago)

Author:

senger@…

Comment:

i18n in zope

TracL10N

@@ -43 +43 @@
 The Drupal CMS [http://www.drupal.org] has a nice translation unit for its backend. It uses .po-files that can be edit and translated with the poedit [http://www.poedit.org/] software.
 
+=== Zope ===
+Zope also uses gettext-catalogs for translation. All basic functionality is provided by the packages  [http://svn.zope.org/Zope3/trunk/src/zope/i18n/ zope.i18n] (language-negotiation, formats for time, date, translation of msgids with languagefallback) and [http://svn.zope.org/Zope3/trunk/src/zope/i18nmessageid/ zope.i18nmessageid]. It also has [http://svn.zope.org/Zope3/trunk/src/zope/i18n/locales/ code to use LDML-files] (Locale Data Markup Language).
+
+The template-language provides some special attibutes (e.g. i18n:domain, i18n:translate).
+Translation in python-code works like this (from [http://svn.zope.org/Zope3/trunk/src/zope/i18nmessageid/messages.txt?rev=65911&view=log])
+
+{{{
+In this example, we create a message factory and assign it to _.  By
+convention, we use _ as the name of our factory to be compatible with
+translatable string extraction tools such as xgettext.  We then call _
+with a string that needs to be translatable:
+
+  >>> from zope.i18nmessageid import MessageFactory, Message
+  >>> _ = MessageFactory("futurama")
+  >>> robot = _(u"robot-message", u"${name} is a robot.")
+}}}
+
+robot looks like a unicode-string and will be translated depending on the negotiated language and the available message-catalogs. 
+
 === Your Own Example ===