- Timestamp:
- 08/09/09 01:43:29 (3 years ago)
- Files:
-
- 1 modified
Legend:
- Unmodified
- Added
- Removed
-
enpraxis.educommons/trunk/enpraxis/educommons/docs/src/LOCALIZATION.txt
r8 r566 37 37 less time consuming because most of the translation work has already been done in Plone. 38 38 39 There are about 4 00 strings needed for a translation of eduCommons (compared to about 1600 strings39 There are about 470 strings needed for a translation of eduCommons (compared to about 1600 strings 40 40 for a Plone translation). Some of these are sentences or paragraphs, but the major part are one or 41 41 two words. These strings are scattered around in Plone, for example in page templates. Other items 42 42 to translate are widget labels, and workflow states. All those strings are collected in master 43 files. Currently eduCommons contains six.pot files. Each language requires its own .po files that43 files. These are called .pot files. Each language requires its own .po files that 44 44 corresponds to the strings or message ids declared in the .pot files. The .pot is the blueprint for 45 45 the .po files. … … 82 82 this translation compared to not getting one at all :) 83 83 84 4. Here is a link to the most recent translation files available for eduCommons (plone.po and 85 eduCommons.po). Remember, unless there is already an existing translation available, you need 86 to grab the .pot files. 87 88 http://cosl.usu.edu/svndev/eduCommons3/trunk/i18n/ 89 90 Here are links to the latest translations for each of the eduCommons products on the Plone 91 Collective site (these links may change, so check back for the most accurate information): 92 93 http://svn.plone.org/svn/collective/ZipFileTransport/branches/cosl-plone3/i18n/ 94 95 http://svn.plone.org/svn/collective/IMSTransport/branches/cosl-plone3/i18n/ 96 97 http://svn.plone.org/svn/collective/ContentLicensing/branches/cosl-plone3/i18n/ 98 99 http://svn.plone.org/svn/collective/PloneBookmarklets/branches/plone3/i18n/ 84 4. Each product in eduCommons has .po files located in the locales directory. We have combined 85 all these files in a single location of ease of translation. It can be accessed here: 86 http://educommons.com/localization/localization-files.zip 87 If you wish to translate a language for which we do not currently have translation files, 88 please contact us at info [at] educommons [dot] com. 100 89 101 90 … … 139 128 ${number} TRANSLATION. 140 129 141 9. Keep translating (but take breaks, this isn't done in one sitting - it's repet etive (but130 9. Keep translating (but take breaks, this isn't done in one sitting - it's repetitive (but 142 131 rewarding) work. After you have translated all of plone.pot, you should start on eduCommons.pot. 143 132 Don't worry, you have already completed the biggest part. … … 154 143 works, you can get an account with Plone (Here's how to request write access to the Collective.) 155 144 and maintain the files in SVN yourself (see next section). If not, no problem, just e-mail your 156 translation to us at eduCommons [at] cosl [dot] usu [dot] edu, and we will add it for you and put it into the145 translation to us at info [at] educommons [dot] com, and we will add it for you and put it into the 157 146 eduCommons distribution in the next release. We will also add you to our our `eduCommons 158 Localization Team page . <./educommons-localization-team>`__147 Localization Team page, here: http://educommons.com/documentation/how-to/educommons-localization-team 159 148 160 149 13. Please check on your translations periodically to keep them updated as new versions are 161 released. A quick findfor "" will reveal any new or missing stings that need to be translated.150 released. A quick search for "" will reveal any new or missing stings that need to be translated. 162 151 163 152 14. If you have other questions or about contributing a translation to eduCommons please contact 164 us at educommons [at] cosl [dot] usu [dot] edu. Thank you for you help!153 us at info [at] educommons [dot] com. Thank you for you help! 165 154
