Changes between Version 2 and Version 3 of Translate

Timestamp:

06/01/09 03:17:17 (4 years ago)

Author:

datakid

Comment:

--

Translate

@@ -3 +3 @@
 == Background ==
 
+For the purposes of translating Plumi, it is important to understand some underlying aspects of both Plone and Plumi. 
+
+Plumi is quite a minimal new Plone Product but brings together many other Plone products available to create a site.
+
+As a result, translating Plumi itself is a smaller task than getting an entire Plumi site translated. For instance, things like the login and password translation strings are provided by the Plone Translation projects (see links below).
+
+Plumi translation follows the Plone translation system. 
+
+All master translation files for any product have .pot as their extension.
+
+From this, we make a country specific translation by copying that master file to the relevant [http://www.iso.org/iso/english_country_names_and_code_elements country-code] file and is given a .po extension:
+
+plumi-example.pot 
+
+becomes 
+
+plumi-example-id.po
+
+for Indonesian.
+
+== Getting the files == 
+To get the files to be translated:
+
+For the backend, retrieving and saving of files, all plumi .pot and .po files are available from the plumi subversion trunk:
+
+ * TODO - link to the locales folder for each part of plumi
+
+Similarly, the Plone translation files can be retrieved and saved here:
+
+https://svn.plone.org/svn/collective/PloneTranslations/trunk
+
+== Tools to use ==
+ 
+There are a number of tools that are available for translating. 
+
+ * [http://www.poedit.net/ poedit]
+ * [http://gtranslator.sourceforge.net/ gtranslator]
+ * [http://kbabel.kde.org/ kbabel] nb: for KDE 3.5.x
+ * [http://userbase.kde.org/Lokalize localize] nb: for KDE 4.x