From: Paolo Bonzini <pbonzini@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Translation of strings in QEMU w/ gettext ?
Date: Tue, 02 Jun 2015 16:53:34 +0200 [thread overview]
Message-ID: <556DC36E.1000907@redhat.com> (raw)
In-Reply-To: <20150602125634.GD19508@redhat.com>
On 02/06/2015 14:56, Daniel P. Berrange wrote:
> In my work on TLS encryption, I've been blindly adding gettext markers
> around all error messages I raise. eg error_setg(errp, _("foo bar"));
> I've done this out of habit, since most apps I work on translate all
> strings that could end up visible by a user.
>
> Looking again at existing QEMU codebase though, I notice that adding
> gettext _("...") markers is the exception, not the rule.
I think that _("...") markers should remain the exceptions. However, we
could autoextract for example error_setg/error_setg_errno's message
arguments into PO files.
Paolo
prev parent reply other threads:[~2015-06-02 14:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-02 12:56 [Qemu-devel] Translation of strings in QEMU w/ gettext ? Daniel P. Berrange
2015-06-02 13:20 ` Daniel P. Berrange
2015-06-02 14:34 ` Kevin Wolf
2015-06-02 14:40 ` Daniel P. Berrange
2015-06-03 7:28 ` Markus Armbruster
2015-06-02 14:53 ` Paolo Bonzini [this message]
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=556DC36E.1000907@redhat.com \
--to=pbonzini@redhat.com \
--cc=berrange@redhat.com \
--cc=qemu-devel@nongnu.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.
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 NNTP newsgroup(s).