From: tomas@tuxteam.de
To: emacs-devel@gnu.org
Subject: Re: [Emacsweblogs] i18n
Date: Mon, 1 Feb 2010 19:13:08 +0100 [thread overview]
Message-ID: <20100201181308.GA7499@tomas> (raw)
In-Reply-To: <87vdehozth.fsf@xemacs.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Mon, Feb 01, 2010 at 10:22:50PM +0900, Stephen J. Turnbull wrote:
> Juri Linkov writes:
> > > The question is "Too ugly?"
> >
> > Perhaps less ugly would be not to add special markers to each and every
> > message, but to translate existing messages internally [...]
> The problem is that the *human* translators need the markers to know
> what to translate.
...and then there are menus and other things. You'd have to locate every
function bound to display a user-facing string (and what do you do about
messages being "synthesised" programatically?).
I think it does make sense to mark the strings themselves: "this is a
translatable string".
Regards
- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFLZxm0Bcgs9XrR2kYRApcyAJ9fqfwqHbdTq80l9GxnJTnhEQUcRwCfQldH
8parkqxpnGSB6yV6U2W3RY0=
=lM0j
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-02-01 18:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1e7a74211001281954h1295a717id942a4405dc98b25@mail.gmail.com>
[not found] ` <87vdekbt60.fsf@everybody.org>
2010-01-31 15:29 ` [Emacsweblogs] i18n smc
2010-02-01 7:52 ` Mark A. Hershberger
2010-02-01 8:51 ` Stephen J. Turnbull
2010-02-01 12:04 ` Juri Linkov
2010-02-01 13:22 ` Stephen J. Turnbull
2010-02-01 18:13 ` tomas [this message]
2010-02-01 18:20 ` Andreas Schwab
2010-02-01 21:45 ` i18n Juri Linkov
2010-02-01 16:01 ` [Emacsweblogs] i18n Stefan Monnier
2010-02-01 18:56 ` Drew Adams
2010-02-01 20:33 ` i18n Stefan Monnier
2010-02-01 21:36 ` [Emacsweblogs] i18n Drew Adams
2010-02-01 23:14 ` i18n Stefan Monnier
2010-02-02 1:21 ` [Emacsweblogs] i18n Kenichi Handa
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=20100201181308.GA7499@tomas \
--to=tomas@tuxteam.de \
--cc=emacs-devel@gnu.org \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.