[OPEN-ILS-DEV] Evergreen translation Web site (beta)

[Dan Scott]

2009/3/20 Karen Schneider <kgs at esilibrary.com>:
>> 2009/3/19 Dan Scott <denials at gmail.com>:
>> > I took a few hours yesterday to set up a basic Pootle instance for the
>> > current Evergreen translations that we have.
>> >
>> > It's still very barebones, and I haven't set it up to allow direct
>> > commits to the repository, but it can be useful if you register and
>> > then log in - you can very quickly drill down to see the overall
>> > status of each language in the Evergreen project, then the status of
>> > each file per language, and have it show you just the untranslated or
>> > fuzzy strings for a given file. Or, if you prefer translating offline,
>> > you can download the zip file for your language, and later upload
>> > files as you complete their translation.
>> >
>> > If there is interest in the community in using this, I can certainly
>> > put some time into refining it and managing the permissions. I suspect
>> > it will make life a lot easier.
>
> Dan, wow! I just registered and looked at this. It really illuminates the
> status of translations. For example, I looked at the status of Canadian
> English for the OPAC. I was able to view statistics. I was less successful
> with viewing "show goals." ("!! This software has encountered an error.
> Please tell your friendly system administrator or software developer the
> following:\n %1$s\n %2$s\n The JSAN library object is missing.").

That's actually a translatable string. It's doing exactly what it's supposed to.

> I also downloaded a zip file for the entire Evergreen Can-English
> translation po file -- cool!  I extracted this file (which included all POs
> -- something to warn people about) and it automatically provided me with PO
> Edit (which informed me "this is the first time you use this program" -- uh
> me talk pretty, too). At that point I'm at work stoppage, as it says, "You
> do not have permission to run reports" and I can't seem to do anything else.

Well, people can use POEdit today if they grab the en-US POT or ll-LL
PO files from a release or SVN. That's an entirely different workflow
than using a Web-based translation interface though. As for warning
about downloading PO files, well, that won't be a surprise to most
translators.

> But maybe that is all permissions related... anyway, this is a really
> interesting direction for monitoring/managing/mentoring/encouraging
> translations!

Right, all of the permissions are listed at
http://translate.sourceforge.net/wiki/pootle/permissions - the default
permissions are rather strict for logged-in users. This makes sense
for a production system, because you don't want to enable a person who
has just registered themselves to start changing strings for any and
every language.

In practice, we would probably grant the rights to change a particular
language to particular users once they have registered. If a given
language has enough translators, certain users could be granted
authorization to review and accept changes that others have made.

And we could create a special SVN user, with commit rights restricted
to the build/i18n/po/ directory, to grant translators permission to
commit changes to SVN through this translation interface. One less
bottleneck!

-- 
Dan Scott
Laurentian University