From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1C31nA-0003KR-R2 for qemu-devel@nongnu.org; Thu, 02 Sep 2004 20:19:00 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1C31n9-0003Ju-A4 for qemu-devel@nongnu.org; Thu, 02 Sep 2004 20:19:00 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1C31n9-0003Jr-7z for qemu-devel@nongnu.org; Thu, 02 Sep 2004 20:18:59 -0400 Received: from [38.113.3.61] (helo=smtp-out.hotpop.com) by monty-python.gnu.org with esmtp (Exim 4.34) id 1C31hh-0006fj-NZ for qemu-devel@nongnu.org; Thu, 02 Sep 2004 20:13:21 -0400 Received: from phreaker.net (kubrick.hotpop.com [38.113.3.103]) by smtp-out.hotpop.com (Postfix) with SMTP id 884C47DA5D4 for ; Fri, 3 Sep 2004 00:13:20 +0000 (UTC) Received: from jbrown.mylinuxbox.org (pcp02982829pcs.midval01.tn.comcast.net [68.85.196.73]) by smtp-1.hotpop.com (Postfix) with ESMTP id 775C31A009F for ; Fri, 3 Sep 2004 00:13:19 +0000 (UTC) Date: Thu, 2 Sep 2004 20:13:17 -0400 From: "Jim C. Brown" Subject: Re: [Qemu-devel] Qemu development schedule? Message-ID: <20040903001317.GB22689@jbrown.mylinuxbox.org> References: <200408310107.07350.hetz@witch.dyndns.org> <002101c48ee5$46b2e280$20389c3f@computername> <1093908872.26682.76.camel@aragorn> <1C8FBBB0-FB2F-11D8-8B6F-000A95D874F4@mac.com> <1093973009.29476.16.camel@sherbert> <4134DF1A.4010407@bellard.org> <20040901215857.GA21314@jbrown.mylinuxbox.org> <20040902092645.A15294@bbland> <20040902205633.GB21292@jbrown.mylinuxbox.org> <20040902235357.GA1789@aplik.cl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040902235357.GA1789@aplik.cl> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org On Thu, Sep 02, 2004 at 07:53:57PM -0400, Daniel Serpell wrote: > Hi! > > El Thu, Sep 02, 2004 at 04:56:33PM -0400, Jim C. Brown escribio: > > > > The idea is, use XLib when qemu is compiled under a *nix, use Win32 for > > Windows, the OSX Gui (Aqua?) for Mac OS X, etc. I don't see what the > > problem here is. > > > > The problem when using XLib directly is localization, it's hard > to port your app to other languages. Using Gtk (or other good recent > libs), the localization problem is already solved. > > Daniel > This makes sense in general, but in the case of qemu, most of the text is displayed on stdout (on the console/terminal). Gtk wouldn't make a difference here, as only the title bar has any text that is send thru the graphics driver (the text you see in the guest OS, by the time it gets to SDL/GTK/XLib layer, is just a bunch of pixels). I don't see how localization applies to qemu. It is true that the help text and such would need to be localized, but GTK wouldn't help too much for that case anyways. The only part of qemu that this issue applies to is the caption on the title bar. Seeing that it is only in one place, this shouldn't be hard to achieve... > > > _______________________________________________ > Qemu-devel mailing list > Qemu-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/qemu-devel > -- Infinite complexity begets infinite beauty. Infinite precision begets infinite perfection.