Re: i18n versus design choices

From: Chris Leonard <cjlhomeaddress_at_gmail.com>
Date: Wed Jul 06 2011 - 02:02:29 CEST

On Mon, Jul 4, 2011 at 2:40 PM, Kathiravelu Pradeeban
<kk.pradeeban@gmail.com> wrote:
> Hi Chris,
> Nice to hear from you again. Apologies for not getting back to the
> localization efforts, on time.
>
> By the way, just wanted to give my opinion that I am -1 for this
> change. In this particular case, though ':' seems a bit redundant, I
> feel it gives a more natural look. Most of these small burdens add
> some beauty to the program. I don't think our localizers take this as
> a big burden anyway. However that is just my opinion.
>
> On the other hand, I am +1 for working towards finding the ways to
> enhance the translator experience and productivity, without
> compromising the aesthetic aspects of AbiWord.
>
> Thank you.
> Regards,
> Pradeeban.

Pradeeban,

Thank you for replying. I was trying to judge the balance given
between small design elements and i18n and L10n considerations and I
was looking for just the type of feedback you provided. However, I
can't say that I'm not a little disappointed. I thought that , if
anything, the Document Properties box would be a non-controversial
opportunity to make small trade-offs between design finesse elements
and practical L10n considerations. It doesn't give me a lot of hope
that time spent on seeking out additional i18n enhancements would be
worth further effort on my part. Other changes I might propose would
likely to be more intrusive than dropping a colon at the end of a
string.

That is as it may be, I will continue to pursue other ways to enhance
the L10n of AbiWord. I do hope that consideration will be given to
re-basing the PO files for any upcoming 2.8.x release that might occur
on the files hosted in Pootle. I was able to make a number of
corrections in a wide variety of languages (e.g. there was a
persistently incorrect "Version %s" printf error in almost all files
that even a non-speaker could correct, in most languages). printf
errors are generally bad news, but I still don't fully understand
AbiWord's .strings files and the rest of your build process, there is
always more to learn.

There are also a number of other version migration errors that have
resulted in bad translation choices supplied by the migration matching
algorithm (these are marked as fuzzy). I would strongly encourage any
AbiWord localizers to review the PO files on Pootle with an eye
towards addressing suggestions or fuzzy string as well as completing
untranslated strings. . One of the great advantages of Pootle hosting
is that a little work can be done at a time. It is not a commitment
to do the entire file all at once before sending the file to the list.
 Many little contributions add up quickly.

The files can be found here, by language:
http://translate.sugarlabs.org/projects/upstream_POT/

Regards,

cjl
Received on Wed Jul 6 02:03:40 2011

This archive was generated by hypermail 2.1.8 : Wed Jul 06 2011 - 02:03:40 CEST