08/09/09 01:43:29 (5 years ago)

updating documentation and educommons.com links

1 edited


  • enpraxis.educommons/trunk/enpraxis/educommons/docs/LOCALIZATION.html

    r520 r566  
    2525setting from neutral to the appropriate setting for your instance.</p> 
    27 <div class="section" id="localization-with-educommons-3-2-1"> 
    28 <h1>Localization with eduCommons 3.2.1</h1> 
     27<div class="section" id="localization-with-educommons-3-2-1-rc2"> 
     28<h1>Localization with eduCommons 3.2.1-rc2</h1> 
    2929<div class="section" id="overview"> 
    4141translation work, but follows the same process as Plone. Adding an eduCommons translation is much 
    4242less time consuming because most of the translation work has already been done in Plone.</p> 
    43 <p>There are about 400 strings needed for a translation of eduCommons (compared to about 1600 strings 
     43<p>There are about 470 strings needed for a translation of eduCommons (compared to about 1600 strings 
    4444for a Plone translation). Some of these are sentences or paragraphs, but the major part are one or 
    4545two words. These strings are scattered around in Plone, for example in page templates. Other items 
    4646to translate are widget labels, and workflow states. All those strings are collected in master 
    47 files. Currently eduCommons contains six .pot files. Each language requires its own .po files that 
     47files. These are called .pot files. Each language requires its own .po files that 
    4848corresponds to the strings or message ids declared in the .pot files. The .pot is the blueprint for 
    4949the .po files.</p> 
    8181language you understand is Italian, and you want to provide a Chinese translation, we prefer 
    8282this translation compared to not getting one at all :)</p> 
    83 <p>4. Here is a link to the most recent translation files available for eduCommons (plone.po and 
    84 eduCommons.po). Remember, unless there is already an existing translation available, you need 
    85 to grab the .pot files.</p> 
    86 <blockquote> 
    87 <p><a class="reference external" href="http://cosl.usu.edu/svndev/eduCommons3/trunk/i18n/">http://cosl.usu.edu/svndev/eduCommons3/trunk/i18n/</a></p> 
    88 <p>Here are links to the latest translations for each of the eduCommons products on the Plone 
    89 Collective site (these links may change, so check back for the most accurate information):</p> 
    90 <p><a class="reference external" href="http://svn.plone.org/svn/collective/ZipFileTransport/branches/cosl-plone3/i18n/">http://svn.plone.org/svn/collective/ZipFileTransport/branches/cosl-plone3/i18n/</a></p> 
    91 <p><a class="reference external" href="http://svn.plone.org/svn/collective/IMSTransport/branches/cosl-plone3/i18n/">http://svn.plone.org/svn/collective/IMSTransport/branches/cosl-plone3/i18n/</a></p> 
    92 <p><a class="reference external" href="http://svn.plone.org/svn/collective/ContentLicensing/branches/cosl-plone3/i18n/">http://svn.plone.org/svn/collective/ContentLicensing/branches/cosl-plone3/i18n/</a></p> 
    93 <p><a class="reference external" href="http://svn.plone.org/svn/collective/PloneBookmarklets/branches/plone3/i18n/">http://svn.plone.org/svn/collective/PloneBookmarklets/branches/plone3/i18n/</a></p> 
    94 </blockquote> 
     83<p>4. Each product in eduCommons has .po files located in the locales directory. We have combined 
     84all these files in a single location of ease of translation. It can be accessed here: 
     85<a class="reference external" href="http://educommons.com/localization/localization-files.zip">http://educommons.com/localization/localization-files.zip</a> 
     86If you wish to translate a language for which we do not currently have translation files, 
     87please contact us at info [at] educommons [dot] com.</p> 
    9588<p>5. Open poEdit or your editor of choice and load the first of the master files. In poEdit 
    9689select File --&gt; Open (for existing .po translation files) or File --&gt; New catalog from POT file. 
    129122criteria.&quot; The code in the first part should be left as it is, so the translation will look like this: 
    130123${number} TRANSLATION.</p> 
    131 <p>9. Keep translating (but take breaks, this isn't done in one sitting - it's repetetive (but 
     124<p>9. Keep translating (but take breaks, this isn't done in one sitting - it's repetitive (but 
    132125rewarding) work. After you have translated all of plone.pot, you should start on eduCommons.pot. 
    133126Don't worry, you have already completed the biggest part.</p> 
    141134works, you can get an account with Plone (Here's how to request write access to the Collective.) 
    142135and maintain the files in SVN yourself (see next section). If not, no problem, just e-mail your 
    143 translation to us at eduCommons [at] cosl [dot] usu [dot] edu, and we will add it for you and put it into the 
    144 eduCommons distribution in the next release. We will also add you to our our <a class="reference external" href="./educommons-localization-team">eduCommons 
    145 Localization Team page.</a></p> 
     136translation to us at info [at] educommons [dot] com, and we will add it for you and put it into the 
     137eduCommons distribution in the next release. We will also add you to our our <a href="#id1"><span class="problematic" id="id2">`</span></a>eduCommons 
     138Localization Team page, here: <a class="reference external" href="http://educommons.com/documentation/how-to/educommons-localization-team">http://educommons.com/documentation/how-to/educommons-localization-team</a></p> 
     139<div class="system-message" id="id1"> 
     140<p class="system-message-title">System Message: WARNING/2 (<tt class="docutils">../LOCALIZATION.txt</tt>, line 142); <em><a href="#id2">backlink</a></em></p> 
     141Inline interpreted text or phrase reference start-string without end-string.</div> 
    146142<p>13. Please check on your translations periodically to keep them updated as new versions are 
    147 released. A quick find for &quot;&quot; will reveal any new or missing stings that need to be translated.</p> 
     143released. A quick search for &quot;&quot; will reveal any new or missing stings that need to be translated.</p> 
    148144<p>14. If you have other questions or about contributing a translation to eduCommons please contact 
    149 us at educommons [at] cosl [dot] usu [dot] edu. Thank you for you help!</p> 
     145us at info [at] educommons [dot] com. Thank you for you help!</p> 
    155151<hr class="footer" /> 
    156152<a class="reference external" href="LOCALIZATION.txt">View document source</a>. 
    157 Generated on: 2009-08-06 16:49 UTC. 
     153Generated on: 2009-08-09 07:41 UTC. 
    158154Generated by <a class="reference external" href="http://docutils.sourceforge.net/">Docutils</a> from <a class="reference external" href="http://docutils.sourceforge.net/rst.html">reStructuredText</a> source. 
Note: See TracChangeset for help on using the changeset viewer.