From: Juri Linkov <juri@jurta.org>
To: "Stephen J. Turnbull" <stephen@xemacs.org>
Cc: emacsweblogs@nongnu.org, emacs-devel@gnu.org
Subject: Re: i18n
Date: Mon, 01 Feb 2010 23:45:48 +0200 [thread overview]
Message-ID: <877hqwn4g3.fsf@mail.jurta.org> (raw)
In-Reply-To: <87vdehozth.fsf@xemacs.org> (Stephen J. Turnbull's message of "Mon, 01 Feb 2010 22:22:50 +0900")
> The problem is that the *human* translators need the markers to know
> what to translate.
I like very much how the translation process is organized in Drupal.
In addition to using gettext, at the time an untranslated string is
displayed it dynamically gets added to the database. Later it can be
translated using UI to search for untranslated strings and translate
them. It's possible to export translated strings in the .po format.
http://drupal.org/handbook/modules/locale
But in the source code, strings are still explicitly marked by special markers.
An alternative to marking translatable strings is to use a regexp-based
approach like is used by `debug-ignored-errors'. For a message format
like "Can't find the %s manpage" it uses a regexp to match its variable part
like "^Can't find the .* manpage$". However, performance wise this approach
doesn't seem optimal.
--
Juri Linkov
http://www.jurta.org/emacs/
next prev parent reply other threads:[~2010-02-01 21:45 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
2010-02-01 18:20 ` Andreas Schwab
2010-02-01 21:45 ` Juri Linkov [this message]
2010-02-01 16:01 ` 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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877hqwn4g3.fsf@mail.jurta.org \
--to=juri@jurta.org \
--cc=emacs-devel@gnu.org \
--cc=emacsweblogs@nongnu.org \
--cc=stephen@xemacs.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).