qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Translation of strings in QEMU w/ gettext ?
Date: Tue, 2 Jun 2015 15:40:43 +0100	[thread overview]
Message-ID: <20150602144043.GI19508@redhat.com> (raw)
In-Reply-To: <20150602143409.GN3765@noname.str.redhat.com>

On Tue, Jun 02, 2015 at 04:34:09PM +0200, Kevin Wolf wrote:
> Am 02.06.2015 um 14:56 hat Daniel P. Berrange geschrieben:
> > In a number of cases libvirt includes the error message from QMP in the
> > message we pass back up to the user. Any errors from libvirt are always
> > translated, so if running libvirt in a non-en_US locale currently you
> > will get a translated message from libvirt which includes a bit english
> > text from QEMU.
> 
> The problem here is which locale to use. If the server uses a different
> locale than the client, not much is won. Can libvirt know on startup
> which language should be used?
> 
> Would we need a language per QMP connection? (Hopefully not.)

Libvirt doesn't have any client selected locale - whatever locale the
libvirtd server is started in is used for all strings. This is good
enough as the most common case will be people with both client and
server using the same locale.

> > Also, with the GTK ui frontend of QEMU now, you'll get some translation
> > of the user interface menu options thanks to GTK built-in translations,
> > but the rest are still english, which is not very satisfactory either.
> 
> As you noticed, this is not what happens, but I think this is the most
> important point: If you translate something, translate all of it.
> Mixed languages is worse than just English.
> 
> Currently the split is that the GTK UI is completely translated, and
> other parts (especially the monitor) isn't translated at all. This is
> a split that is easy to understand and doesn't feel like mixed
> languages.
> 
> If we want to extend it to the monitor, we need to translate all of the
> monitor (including all error messages that could eventually be passed to
> the monitor) in the same release. Sounds not impossible, but in this
> case we really can't do just half of it as we usually do with our
> conversions.

Well, even if all the code was translated, we would never guarantee that
all languages have 100% finished .po files. So incrementally updating the
QEMU source to mark more strings is not that different from a case where
all is marked but most translations are incomplete.

Regards,
Daniel
-- 
|: http://berrange.com      -o-    http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org              -o-             http://virt-manager.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org       -o-       http://live.gnome.org/gtk-vnc :|

  reply	other threads:[~2015-06-02 14:40 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 [this message]
2015-06-03  7:28     ` Markus Armbruster
2015-06-02 14:53 ` Paolo Bonzini

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=20150602144043.GI19508@redhat.com \
    --to=berrange@redhat.com \
    --cc=kwolf@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).