From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:33233) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YznGi-0002k7-Sj for qemu-devel@nongnu.org; Tue, 02 Jun 2015 10:34:17 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YznGd-0005YR-Sp for qemu-devel@nongnu.org; Tue, 02 Jun 2015 10:34:16 -0400 Received: from mx1.redhat.com ([209.132.183.28]:33772) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YznGd-0005YL-O1 for qemu-devel@nongnu.org; Tue, 02 Jun 2015 10:34:11 -0400 Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) by mx1.redhat.com (Postfix) with ESMTPS id 30E77344ED8 for ; Tue, 2 Jun 2015 14:34:11 +0000 (UTC) Date: Tue, 2 Jun 2015 16:34:09 +0200 From: Kevin Wolf Message-ID: <20150602143409.GN3765@noname.str.redhat.com> References: <20150602125634.GD19508@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150602125634.GD19508@redhat.com> Subject: Re: [Qemu-devel] Translation of strings in QEMU w/ gettext ? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Daniel P. Berrange" Cc: qemu-devel@nongnu.org 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.) > 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. Kevin