Ignore:
Timestamp:
08/17/09 10:36:44 (5 years ago)
Author:
tom
Message:

updated translation instructions

File:
1 edited

Legend:

Unmodified
Added
Removed
  • enpraxis.educommons/trunk/enpraxis/educommons/docs/src/LOCALIZATION.txt

    r566 r586  
    4848Tools 
    4949----- 
    50 When creating the .po files, we strongly recommend using a specialized tool called poEdit  
    51 (http://www.poedit.net). This makes the translation process very easy. But a normal  
    52 text editor work fine if you prefer that (both vim and emacs are great for this, and have special  
    53 modes for PO files). poEdit exists for both Linux and Windows, and Mac OS X. 
     50When creating the .po files, we strongly recommend using a specialized tool called poEdit (http://www.poedit.net). This makes the translation process very easy. poEdit exists for both Linux and Windows, and Mac OS X. When you open a .po file with PoEdit, you will see a list of translations in English and four boxes below. As you click on a line to highlight it, you will see that the top two boxes are for English and Default translations. Type your translation in the lower left box. Do not change the naming of the individual translation files. Just send them back when you are done (you may zip them up if you like). 
    5451 
    55 If you use a plain text editor instead of a dedicated tool, you should make sure you use utf-8  
    56 as your charset, even if your country usually uses iso-8859-* or similar. The reason for this is  
    57 that Plone uses a few characters (like the ellipsis) that don't have representations in other  
    58 charsets. 
     52You can also use a normal text editor if you prefer (both vim and emacs are great for this, and have special modes for PO files). If you use a plain text editor instead of a dedicated tool, you should make sure you use utf-8 as your charset, even if your country usually uses iso-8859-* or similar. The reason for this is that Plone uses a few characters (like the ellipsis) that don't have representations in other charsets. Please review the step-by-step instructions below for more information about the actual translation process. 
    5953 
    6054 
Note: See TracChangeset for help on using the changeset viewer.