From: Gerd Hoffmann <kraxel@redhat.com>
To: Samuel Thibault <samuel.thibault@gnu.org>
Cc: qemu-devel@nongnu.org, pbonzini@redhat.com, berrange@redhat.com,
peter.maydell@linaro.org, mjt@tls.msk.ru
Subject: Re: [Qemu-devel] [PATCH 0/5] curses: wide character support
Date: Wed, 26 Oct 2016 12:05:55 +0200 [thread overview]
Message-ID: <1477476355.18984.32.camel@redhat.com> (raw)
In-Reply-To: <20161025222616.GE2801@var.home>
On Mi, 2016-10-26 at 00:26 +0200, Samuel Thibault wrote:
> Hello,
>
> Ping?
Back online now after being sick for a while.
Sorry for the delay.
> Samuel Thibault, on Sat 15 Oct 2016 21:53:03 +0200, wrote:
> > This patch series adds wide character support to the curses frontend of qemu,
> > thus allowing to fix a lot of input and output issues with e.g. accented letters
> > and semi-graphic glyphs. Since qemu can't know the encoding of the VGA font, the
> > user has to specify it (just like he has to specify the keyboard layout with
> > -k). I used option -f to make it simple for now, but I welcome any other idea :)
>
> I forgot to mention that I updated the patches according to the reviews
> on the list (assume cursesw support, and use -display option).
Good, looks much better now without all the #ifdefs.
/me wonders whenever we should do the same with iconv. It's part of the
POSIX.1-2001 specs, and we have 2016 now. Do we *really* need configure
checks and #ifdefs for it? Also we could use iconv for the
cp437-to-unicode mapping instead of having a hard-coded table for it.
Given how close the freeze deadline is now I'm tempted to cherry-pick
patches 0-3 and prepare a pull request ASAP.
cheers,
Gerd
next prev parent reply other threads:[~2016-10-26 10:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-15 19:53 [Qemu-devel] [PATCH 0/5] curses: wide character support Samuel Thibault
2016-10-15 19:53 ` [Qemu-devel] [PATCH 1/5] curses: fix left/right arrow translation Samuel Thibault
2016-10-15 19:53 ` [Qemu-devel] [PATCH 2/5] curses: Use cursesw instead of curses Samuel Thibault
2016-10-15 19:53 ` [Qemu-devel] [PATCH 3/5] curses: use wide output functions Samuel Thibault
2016-10-15 19:53 ` [Qemu-devel] [PATCH 4/5] curses: add option to specify VGA font encoding Samuel Thibault
2016-10-15 21:07 ` Paolo Bonzini
2016-10-25 23:16 ` Samuel Thibault
2016-10-15 19:53 ` [Qemu-devel] [PATCH 5/5] curses: support wide input Samuel Thibault
2016-10-25 22:26 ` [Qemu-devel] [PATCH 0/5] curses: wide character support Samuel Thibault
2016-10-26 10:05 ` Gerd Hoffmann [this message]
2016-10-26 11:43 ` Samuel Thibault
2016-10-26 12:18 ` Gerd Hoffmann
2016-10-26 12:40 ` Gerd Hoffmann
2016-10-26 15:19 ` Samuel Thibault
-- strict thread matches above, loose matches on Subject: below --
2016-06-22 22:23 Samuel Thibault
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=1477476355.18984.32.camel@redhat.com \
--to=kraxel@redhat.com \
--cc=berrange@redhat.com \
--cc=mjt@tls.msk.ru \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=samuel.thibault@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.