From: "Eli Zaretskii" <eliz@gnu.org>
To: Andrew Cagney <cagney@gnu.org>
Cc: kevinb@redhat.com, gdb-patches@sources.redhat.com
Subject: Re: i18n, part 2
Date: Sun, 12 Dec 2004 21:49:00 -0000 [thread overview]
Message-ID: <01c4e093$Blat.v2.2.2$f3ec9900@zahav.net.il> (raw)
In-Reply-To: <41BC8BDB.3090400@gnu.org> (message from Andrew Cagney on Sun, 12 Dec 2004 13:20:11 -0500)
> Date: Sun, 12 Dec 2004 13:20:11 -0500
> From: Andrew Cagney <cagney@gnu.org>
> Cc: Eli Zaretskii <eliz@gnu.org>, gdb-patches@sources.redhat.com
>
> When I first asked about i18n on the ``help'' list, it was made very
> clear to me that not just the pot file, but the entire source code
> should be made available.
>
> That way the translators could more easily refer to the source code
> examine any text's original context.
It's fine to make the sources available, but we cannot assume that
translators know C (or any programming language, for that matter).
Even if they do know C, they might know nothing about the subject
matter, such as threads, and thus will be unable to understand what
the code does. Such talents are not requested from them, while other
talents, which are utterly irrelevant for a programmer, are.
That is why we should try to come up with message string catalog that
allows to produce decent translations without reading the code.
I'm still waiting for TP people to respond to my questions. If they
don't reply in a few more days, I will try alternative addresses.
next prev parent reply other threads:[~2004-12-12 21:45 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-04 20:06 Baurjan Ismagulov
2004-12-04 21:52 ` Daniel Jacobowitz
2004-12-04 22:17 ` Baurjan Ismagulov
2004-12-04 23:59 ` Daniel Jacobowitz
2004-12-05 21:41 ` Eli Zaretskii
2004-12-05 23:39 ` Daniel Jacobowitz
2004-12-06 2:19 ` Baurjan Ismagulov
2004-12-06 4:59 ` Eli Zaretskii
2004-12-06 0:00 ` Baurjan Ismagulov
2004-12-15 0:50 ` Baurjan Ismagulov
2004-12-15 21:48 ` Eli Zaretskii
2004-12-06 18:53 ` Kevin Buettner
2004-12-06 20:59 ` Eli Zaretskii
2004-12-06 23:04 ` Kevin Buettner
2004-12-07 5:08 ` Eli Zaretskii
2004-12-07 5:10 ` Daniel Jacobowitz
2004-12-07 17:28 ` Kevin Buettner
2004-12-07 19:59 ` Eli Zaretskii
2004-12-07 20:28 ` Andreas Schwab
2004-12-12 19:50 ` Andrew Cagney
2004-12-12 22:08 ` Eli Zaretskii
2004-12-12 18:23 ` Andrew Cagney
2004-12-12 21:49 ` Eli Zaretskii [this message]
2004-12-07 22:02 ` Eli Zaretskii
2004-12-12 18:35 ` Andrew Cagney
2004-12-26 4:46 ` Baurjan Ismagulov
2004-12-26 23:25 ` Eli Zaretskii
2005-01-05 15:48 ` Andrew Cagney
2005-01-05 16:07 ` Baurjan Ismagulov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='01c4e093$Blat.v2.2.2$f3ec9900@zahav.net.il' \
--to=eliz@gnu.org \
--cc=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=kevinb@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox