2012Q2: Grant Proposal: Spanish Localization of the Perl Core Documentation

Category: Grants

Comments (7)

Every time someone proposes a translation grant, the same question arises. How will this translation be maintained?

It really doesn't seem useful to translate the docs once and then have *that* be the canonical doc source for Spanish users, even after they've long gone stale.

Hi Dave

We always follow the current version.
Whenever a new version rolls out, we use the translation memory to update, complete new strings and fuzzy matches, and keep working on the new version (and stop working on the previous one; i.e., we don't plan to do a complete translation of 5.14.2). This way, in each version we get a little closer to 100% translation, and eventually we will have a parallel documentation in Spanish.

As chair of the Grants Committee I try not to comment or ask any questions. Nevertheless, I will abstain regarding this one (as I know Enrique), so I feel more comfortable commenting.

Is the TMX already available? Will it be available? Is there any terminology behind this? Is it available already? Some TBX file or so?

Also, looking to the repository, you are using OmegaT for the translation task. Are you developing any software that might help other languages for a similar task, or just translating as a common translator would do?


Hi Alberto

The TMX is available. In fact, we have several translation memories in the repository. The clean one contains the fully reviewed translations that are already published on CPAN; we also keep work memories from the team members in the github repository, and the Padre and Kephra memories as a reference.

Regarding terminology, for the time being we've been using the clean memory to check terms that have been validated already, but will add a glossary soon (we are working on a terminology extraction tool more focused to machine translation explorations). We discuss new terms using perlglossary.pod as our guide, so perhaps we should give priority to that document.

As for the software that might help other languages, we have already published on github a couple of scripts for postprocessing and memory merge tasks (which will be improved soon), and plan to develop a program to compare the documentation of different Perl versions (i.e., current stable and current development) that shows new documents, documents removed, documents with the most/least changes, etc., to guide us in our translation strategy. This is a long term project and, who knows, more goodies may appear some day in our repository.

We would like to stress the fact that all these procedures and tools can be applied to any language. So far we haven't worked on Spanish-specific tools (although we may do that as well, of course).

A small side note - perlglossary.pod got some updates recently, but the English version really could do with someone reviewing/updating and cleaning out old references.

If anyone is interested please fork:


and join



In general, I like the idea and particularly the CAT approach, as I can see how that would help keep thing up to date (assuming volunteers to respond to deltas).

However, I'm not sure a grant is the right vehicle for a project that is effectively open-ended and ongoing. If a grant is necessary now to boost the project, what happens when the grant is over? Or put differently, what will be different about the sustainability after the grant is over?

The deliverables seem fairly arbitrary. I'd be more supportive if they more clearly achieved some critical mass or milestone. What does the 18% increase from 42% to 60%? E.g. I care a lot more about the new OO docs than I do about perlhist or perldeltas.

(I do think that translating perldeltas is useful, but they are about a quarter of the pod directory in the perl source and not what I would prioritize.)

Without more clarity about what specifically is getting translated and why that will position the project for long term success without grant support, I can't support this grant.

Hi David

We have been working on this project without any support for some time now, so work will not cease after eventually completing a grant.

The purpose of applying for this grant is to commit ourselves to spend more time on the project for a few months in order to gain momentum and produce a larger translation memory (i.e., more reviewed segments and approved terms for reference), and better materials (procedures, guidelines, etc.) for the team, which also started to grow.

You can check our status spreadsheet referenced in the grant application to see which documents we are working on.
The new doc on object-oriented programming (perlootut) will be one of our top priorities as soon as Perl 5.16.0 hits CPAN (we would rather wait until a final version is released). We have already translated a couple of the old OO docs, however, so we may publish them anyway in our 5.14 track.
As we mention in our application "We have split the documentation in core documents on one hand, and perldeltas & readmes on the other, to give priority to the most popular documents."

Yes, this is as open-ended project. As we all know, Perl 5 is here to stay and Perl 6 is growing healthy and strong, so our goal is developing a framework to create/maintain localized versions as Perl evolves.

Sign in to add comment