Spanish Localization of the Perl Core Documentation - Grant Report #1
Wed, 04-Jul-2012 by
Alan Haggai Alavi
edit post
<![CDATA[
*Enrique Nell and Joaquin Ferrero reported:*
> <p>Project status:
> <a href='https://docs.google.com/spreadsheet/ccc?key=0AkmrG_9Q4x15dC1MNWloU0lyUjhGa2NrdTVTOG5WZVE'>https://docs.google.com/spreadsheet/ccc?key=0AkmrG_9Q4x15dC1MNWloU0lyUjhGa2NrdTVTOG5WZVE</a></p>
>
> <p>CPAN distribution:
> <a href='http://search.cpan.org/~enell/POD2-ES-5.16.0.04/'>http://search.cpan.org/~enell/POD2-ES-5.16.0.04/</a></p>
>
> <p>Project host:
> <a href='https://github.com/zipf/perldoc-es'>https://github.com/zipf/perldoc-es</a></p>
>
> <p>During the last month we updated <code>POD2::ES</code> from v5.14.2 to v5.16.0 (translated new segments and updated changed ones), and released to CPAN the updated distribution. Other translated files that still must be reviewed (i.e., that haven't been released to CPAN) are currently being updated to v5.16.0.</p>
>
> <p><code>POD2::ES</code> v5.16.0.01 included all the files in the previous release, except perlcheat.pod, which had a bug that we reported through perlbug. Discussion in the p5p list suggested that this file would undergo further changes, and since the localized version entails heavy formatting work, we decide to wait until v5.16.1 to include it back in the distribution.</p>
>
> <p>New files added during the v5.16.0 track of <code>POD2::ES</code>:</p>
>
> <ul>
> <li>perlbot</li>
> <li>perlboot</li>
> <li>perldata</li>
> <li>perlexperiment</li>
> <li>perlootut</li>
> <li>perltodo</li>
> <li>perltooc</li>
> <li>perltoot</li>
> </ul>
>
><p>We also fixed code issues (related to <code>POD2::Base</code>) in <code>ES.pm</code>, the main module, and made a few doc changes.</p>
>
> <h3>Stats</h3>
>
> <p>Here is a brief summary of the final project status for v5.14.2 (June 4):</p>
>
> <ul>
> <li>Total documents: 190 (98 in core docs)</li>
> <li>Total words: 924,435 (619,056 in core docs)</li>
> <li>% translated: 44.02% (42,30% of core docs)</li>
> <li>% reviewed: 4.43%</li>
> </ul>
>
> <p>And the current status of our v5.16.0 track:</p>
>
> <ul>
> <li>Total documents: 162 (100 in core docs)</li>
> <li>Total words: 841,604 (597,294 in core docs)</li>
> <li>% translated: 43.51% (44.74% of core docs)</li>
> <li>% reviewed: 5.06%</li>
> </ul>
>
> <h3>Team</h3>
>
> <p>Our new team members, Jennifer Maldonado and Manuel Gómez, started working remotely through a remote server setup deployed in April. New collaborators can start working right away with very little training, since they don't have to install and configure the translation tool (although they can do it if they prefer a local setup; the project wiki contains guidelines for both scenarios.)</p>
>
> <h3>Tools</h3>
> <p>We have implemented several changes in the post-processing script:</p>
>
> <ul>
> <li>Support for the new naming convention used for Readmes in v5.16</li>
> <li>Handling of pod files containing the =encoding utf8 command (our translation tool currently generates latin-1 files, so now the post-processing script checks and changes the encoding of the generated file if necessary)</li>
> <li>Command line switch to add names of people involved in the translation of a particular file to the Translators section at the bottom of the file</li>
> <li>Hardcoded paths were updated for the new v5.16 project setup.</li>
> </ul>
>
> <h3>Future work</h3>
>
> <p>For our second month, we plan to do more work on tools and keep translating/reviewing pods while we wait for v5.16.1, which will require another update.</p>
>
> <p>Our immediate TO DO list includes reporting the issues found in <code>POD2::Base</code> and several pod processing issues that should be fixed for localized versions.</p>
> <p>For instance, the CPAN page for <code>POD2::ES</code> does not show the description of the translated modules because the POD processor does not find section NAME (it's NOMBRE in Spanish).</p>
>
> <p>The French team fixed this by using NAME/NOM, but we think that a cleaner solution would be better.</p>
>
> <p>Another issue we found is related to the processing of POD links like <code>L<perlport/"Supported Platforms"></code>, which produces English text: "Supported Platforms" in <code>perlport</code> (for Spanish, "in" should be "en".)</p>
>
> <p>It seems that the *roff-related issues that prevented displaying correctly the extended characters in UTF-8 encoded files using perldoc in Xterminals have been fixed in v5.16.0, so we may switch back to UTF-8.</p>
>
> <p>We are also testing the latest version of the translation tool, OmegaT v2.6, which includes a new feature that allows team work using a single memory.</p>
]]>
Comments (0)
