[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: a little start at improving PSPP translatability
From: |
John Darrington |
Subject: |
Re: a little start at improving PSPP translatability |
Date: |
Thu, 16 Jul 2009 07:46:11 +0000 |
User-agent: |
Mutt/1.5.18 (2008-05-17) |
Regarding commit "Avoid translating strings that don't need translation",
I think your assertion that "Strings such as "%d" do not need translation"
is incorrect.
This is apparantly important for languages such as Arabic. See
http://www.gnu.org/software/gettext/manual/gettext.html#index-Arabic-digits-1137
Also, I believe that the ampersand character doesn't hold the same
semantics in every language, so has to be translated too.
Somewhere else I have read (I can't remember where) that arabic
translators also like to introduce special "punctuation" (in the
form of a long stroke) between certain words, depending on their
context. So even strings like "%s %s" need to be translated too.
Of course, translators of languages that don't have these fancy
requirements can leave such strings untranslated.
In summary, I think this entire commit is inappropriate. The others
look fine.
J'
On Wed, Jul 15, 2009 at 10:25:22PM -0700, Ben Pfaff wrote:
After our email discussion today, I decided to start looking
through PSPP for ways to make it easier to translate. After a
few minutes I came up with what I think are some improvements.
Do you want to look over the changes in the "i18n" branch that I
just pushed? They get rid of a number of translatable strings,
which should help I guess. It's only a small start--there is a
lot more that can be done.
--
PGP Public key ID: 1024D/2DE827B3
fingerprint = 8797 A26D 0854 2EAB 0285 A290 8A67 719C 2DE8 27B3
See http://pgp.mit.edu or any PGP keyserver for public key.
signature.asc
Description: Digital signature