From: Egmont Koblinger <egmont@uhulinux.hu>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: "H. Peter Anvin" <hpa@zytor.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] console UTF-8 fixes
Date: Sat, 7 Apr 2007 19:26:03 +0200 [thread overview]
Message-ID: <20070407172603.GA25351@uhulinux.hu> (raw)
In-Reply-To: <Pine.LNX.4.61.0704071232560.22181@yvahk01.tjqt.qr>
On Sat, Apr 07, 2007 at 01:00:48PM +0200, Jan Engelhardt wrote:
Hi,
> Please, no dot, and no inverse color.
> Imagine someone had the following bitmap for <unknown glyph/illegal sequence>:
No dot, I'm already convinced. To clarify the inverse thingy:
This is what the current kernel does:
1) tries to display the desired symbol
2) if it fails, tries to display U+FFFD (which usually looks similar to an
inverted question mark)
3) if this fails again then displays a normal '?'
(or a different symbol due to a bug discussed below)
Here's my proposal. This only alters the 3rd step, not the first two:
1) tries to display the desired symbol
2) if it fails, tries to display U+FFFD, still with _normal_ attributes
3) if this fails then display an ascii '?' with inverted attributes
So you won't get "double" inversion. If you do have U+FFFD in your font then
this will introduce no chance. If you don't have U+FFFD, you'll see inverse
question marks instead of normal ones.
> I blame your latin2 unicode map. (See above about 'Û'.)
There's nothing wrong with my latin2 unicode map, and I've located and
changed the part _in the kernel_ that displays a false glyph using the
algorithm I've outlined. It just uses "the glyph at that code position
within the glyph table" as a fallback, which might be okay in 8-bit mode
(and I haven't modified the behavior in that case), but I got rid of this
behavior in UTF-8 mode since it's definitely a fault in the world of
Unicode.
> It should perhaps display a regular 'u' if it cannot display 'û',
I rather think it should display U+FFFD but YMMV.
> but definitely not 'ü' (which is not called a double accent, btw).
This is not the character I've been talking about, I actually _did_ talk
about u with double acute accent (ű - you might not have seen this character
so far, AFAIK it's only used in Hungarian, no other languages). But we agree
that the kernel definitely shouldn't display a character with a different
accent on it. This is one of the bugs my patch addresses.
bye,
Egmont
next prev parent reply other threads:[~2007-04-07 17:26 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-06 19:12 Egmont Koblinger
2007-04-06 19:43 ` H. Peter Anvin
2007-04-07 9:24 ` Egmont Koblinger
2007-04-07 11:00 ` Jan Engelhardt
2007-04-07 17:26 ` Egmont Koblinger [this message]
2007-04-07 17:59 ` H. Peter Anvin
2007-04-10 9:43 ` Egmont Koblinger
2007-04-10 15:43 ` H. Peter Anvin
2007-04-10 17:19 ` Egmont Koblinger
2007-04-10 17:30 ` H. Peter Anvin
2007-04-10 18:51 ` Egmont Koblinger
2007-04-11 12:58 ` Jan Engelhardt
2007-04-10 17:36 ` Alan Cox
2007-04-10 17:36 ` H. Peter Anvin
2007-04-11 18:28 ` Egmont Koblinger
2007-04-11 18:36 ` H. Peter Anvin
2007-04-12 9:11 ` Egmont Koblinger
2007-04-12 15:36 ` H. Peter Anvin
2007-04-12 16:41 ` Jan Engelhardt
2007-04-12 16:55 ` Egmont Koblinger
2007-04-12 16:58 ` H. Peter Anvin
2007-04-12 17:16 ` Egmont Koblinger
2007-04-12 17:35 ` H. Peter Anvin
2007-04-12 17:44 ` Egmont Koblinger
2007-04-12 17:49 ` H. Peter Anvin
2007-04-12 18:46 ` Jan Engelhardt
2007-04-12 12:54 ` Egmont Koblinger
2007-04-12 13:13 ` Alan Cox
2007-04-12 14:06 ` Egmont Koblinger
2007-04-12 14:38 ` Roman Zippel
2007-04-12 14:58 ` Egmont Koblinger
2007-04-12 15:52 ` Roman Zippel
2007-04-12 16:36 ` Egmont Koblinger
2007-04-12 18:09 ` Roman Zippel
2007-04-11 19:00 ` Jan Engelhardt
2007-04-12 9:22 ` Egmont Koblinger
2007-04-11 19:36 ` Pavel Machek
2007-04-12 8:14 ` Jan Engelhardt
2007-04-17 10:22 Egmont Koblinger
2007-06-19 12:13 ` Egmont Koblinger
[not found] <8aT6Q-3iM-17@gated-at.bofh.it>
[not found] ` <8xLa7-25v-5@gated-at.bofh.it>
2007-06-19 13:54 ` Bodo Eggert
2007-06-19 14:42 ` Egmont Koblinger
2007-06-19 17:10 ` Bodo Eggert
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=20070407172603.GA25351@uhulinux.hu \
--to=egmont@uhulinux.hu \
--cc=hpa@zytor.com \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®