| 1 | TRANSLATION TEMPLATES FOR DRUPAL 6.0 |
|---|
| 2 | ================================================================================ |
|---|
| 3 | |
|---|
| 4 | The translation templates hosted here are updated for Drupal 6.0. |
|---|
| 5 | |
|---|
| 6 | Updating Drupal 5 translations: |
|---|
| 7 | -------------------------------- |
|---|
| 8 | |
|---|
| 9 | Start at http://drupal.org/node/202631 |
|---|
| 10 | |
|---|
| 11 | File naming: |
|---|
| 12 | ------------- |
|---|
| 13 | |
|---|
| 14 | Just rename .pot files to .po files when translating, otherwise leave them |
|---|
| 15 | where they are. Packages are generated in the format required by Drupal 6 on |
|---|
| 16 | drupal.org. |
|---|
| 17 | |
|---|
| 18 | Package structure generated on drupal.org: |
|---|
| 19 | ------------------------------------------- |
|---|
| 20 | |
|---|
| 21 | Drupal 6 comes with automated translation file import, so the translation |
|---|
| 22 | source strings are organized by location. For the translations to be imported |
|---|
| 23 | automatically, translated templates will be renamed for the translations |
|---|
| 24 | by the packager script such as (for example in Italian): |
|---|
| 25 | |
|---|
| 26 | - general.pot to general.it.po |
|---|
| 27 | - themes-garland.pot to themes-garland.it.po |
|---|
| 28 | - ... |
|---|
| 29 | |
|---|
| 30 | The hard rule is that the file name will end in the language code and |
|---|
| 31 | the .po extension, while keeping the original first part of the name. Drupal 6 |
|---|
| 32 | translation packager scripts use the first part of the file name for |
|---|
| 33 | file placement (eg. 'themes-garland'), while Drupal itself will look for the |
|---|
| 34 | last part when importing translations on your site (eg. 'it'). Finally, |
|---|
| 35 | the '.po' extension is important to identify the file as a translation |
|---|
| 36 | to import. |
|---|
| 37 | |
|---|
| 38 | File placement is just as important as file naming. Translation files are |
|---|
| 39 | automtically imported from module and theme folders, and used from install |
|---|
| 40 | profile folders on installation. The following placement is used |
|---|
| 41 | by the packager based on the template file set in this directory: |
|---|
| 42 | |
|---|
| 43 | - general.pot, includes.pot, misc.pot and modules-system.pot |
|---|
| 44 | translations to modules/system/translations |
|---|
| 45 | |
|---|
| 46 | - modules-*.pot translations to their corresponding modules/*/translations |
|---|
| 47 | directory |
|---|
| 48 | |
|---|
| 49 | - themes-*.pot translations to their corresponding themes/*/translations |
|---|
| 50 | directory |
|---|
| 51 | |
|---|
| 52 | - installer.pot to profiles/default/translations |
|---|
| 53 | as it.po (for example in Italian) |
|---|
| 54 | |
|---|
| 55 | Note that all this renaming and directory placement is done by the |
|---|
| 56 | packaging script on drupal.org, you should only rename .pot files to |
|---|
| 57 | .po files! |
|---|
| 58 | |
|---|
| 59 | $Id: README.txt,v 1.6.2.4 2008/02/15 12:55:15 goba Exp $ |
|---|
