From: "Jim C. Brown" <jbrown106@phreaker.net>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Qemu development schedule?
Date: Thu, 2 Sep 2004 20:13:17 -0400 [thread overview]
Message-ID: <20040903001317.GB22689@jbrown.mylinuxbox.org> (raw)
In-Reply-To: <20040902235357.GA1789@aplik.cl>
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.
next prev parent reply other threads:[~2004-09-03 0:19 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-30 21:44 [Qemu-devel] Qemu development schedule? Jeebs
2004-08-30 21:59 ` John R. Hogerhuis
2004-08-30 22:51 ` Jeebs
2004-08-31 11:59 ` Johannes Schindelin
2004-08-31 15:58 ` Jeebs
2004-08-31 16:27 ` Joe Batt
2004-08-31 17:42 ` Jeebs
2004-09-01 19:25 ` Kai Cherry
2004-09-01 19:33 ` andrej
2004-09-01 19:46 ` Joe Batt
2004-09-01 20:34 ` Mike Tremoulet
2004-09-01 20:46 ` Kai Cherry
2004-09-01 20:35 ` Kai Cherry
2004-09-02 20:46 ` Jim C. Brown
2004-09-03 7:52 ` [Qemu-devel] Filegetopt (Was: Qemu development schedule?) Renzo Davoli
2004-08-31 16:32 ` [Qemu-devel] Qemu development schedule? Johannes Schindelin
2004-08-31 17:40 ` Jeebs
2004-09-01 15:43 ` Lionel Ulmer
2004-09-01 17:03 ` John R. Hogerhuis
2004-09-01 19:07 ` Kai Cherry
2004-09-02 10:20 ` Info
2004-08-31 17:42 ` John R. Hogerhuis
2004-08-31 19:07 ` andrej
2004-08-31 19:44 ` Kai Cherry
2004-08-30 22:07 ` Hetz Ben Hamo
2004-08-30 22:59 ` Jeebs
2004-08-30 23:34 ` John R. Hogerhuis
2004-08-31 9:21 ` Kai Cherry
2004-08-31 10:15 ` Patrick Mauritz
2004-08-31 10:23 ` Kai Cherry
2004-08-31 17:23 ` Gianni Tedesco
2004-08-31 19:08 ` Kai Cherry
2004-09-01 20:53 ` Magnus Damm
2004-08-31 20:27 ` Fabrice Bellard
2004-08-31 21:50 ` René Korthaus
2004-09-01 22:04 ` Jim C. Brown
2004-08-31 22:02 ` Patrick Mauritz
2004-09-01 21:58 ` Jim C. Brown
2004-09-02 7:26 ` Lionel Ulmer
2004-09-02 20:56 ` Jim C. Brown
2004-09-02 23:28 ` Lionel Ulmer
2004-09-03 0:07 ` Jim C. Brown
2004-09-03 8:32 ` Fabrice Bellard
2004-09-03 7:29 ` Adrian Smarzewski
2004-09-03 8:28 ` Fabrice Bellard
2004-09-02 23:53 ` Daniel Serpell
2004-09-03 0:13 ` Jim C. Brown [this message]
2004-09-03 1:35 ` John R. Hogerhuis
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=20040903001317.GB22689@jbrown.mylinuxbox.org \
--to=jbrown106@phreaker.net \
--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).