unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: eggert@cs.ucla.edu, 28242@debbugs.gnu.org
Subject: bug#28242: Batch mode compiling: Error messages are displayed with "invalid character" glyph bounding symbols.
Date: Sun, 27 Aug 2017 17:31:31 +0000	[thread overview]
Message-ID: <20170827173131.GI3520@ACM> (raw)
In-Reply-To: <83r2vx3p0r.fsf@gnu.org>

Hello, Eli.

On Sun, Aug 27, 2017 at 20:21:24 +0300, Eli Zaretskii wrote:
> > Date: Sun, 27 Aug 2017 17:05:04 +0000
> > From: Alan Mackenzie <acm@muc.de>
> > Cc: 28242@debbugs.gnu.org, Paul Eggert <eggert@cs.ucla.edu>

> > I've looked into this.  My system is currently using the standard Linux
> > font, the one baked into the kernel.  I would have thought it rather
> > important to support properly - there will be lots of similarly
> > "misconfigured" systems around.

> What non-ASCII characters does that font support?

Let me cite the comment at the top of the pertinent Linux source file,
/usr/src/linux-4.13-rc3/drivers/tty/vt/cp437.uni:

#
# Unicode table for IBM Codepage 437.  Note that there are many more
# substitutions that could be conceived (for example, thick-line
# graphs probably should be replaced with double-line ones, accented
# Latin characters should replaced with their nonaccented versions,
# and some upper case Greek characters could be replaced by Latin),
# however,
# I have limited myself to the Unicodes used by the kernel ISO 8859-1,
# DEC VT, and IBM CP 437 tables.
#

It seems to be mainly ASCII, Latin-1, with lots of miscellaneous
graphics characters, including the single and double line thingies,
sufficient to support mutt, for example.

-- 
Alan Mackenzie (Nuremberg, Germany).





  reply	other threads:[~2017-08-27 17:31 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-26 13:06 bug#28242: Batch mode compiling: Error messages are displayed with "invalid character" glyph bounding symbols Alan Mackenzie
2017-08-26 14:09 ` Eli Zaretskii
2017-08-26 17:06   ` Alan Mackenzie
2017-08-26 18:12     ` Eli Zaretskii
2017-08-26 19:24       ` Alan Mackenzie
2017-08-26 19:40         ` Eli Zaretskii
2017-08-26 20:39           ` Alan Mackenzie
2017-08-27  8:16 ` Paul Eggert
2017-08-27  9:16   ` Alan Mackenzie
2017-08-27 14:40     ` Eli Zaretskii
2017-08-27 16:46       ` Paul Eggert
2017-08-27 17:23         ` Alan Mackenzie
2017-08-27 17:53         ` Eli Zaretskii
2020-08-20 15:59           ` Lars Ingebrigtsen
2017-08-27 16:40     ` Paul Eggert
2017-08-27 16:56       ` Alan Mackenzie
2017-08-27 16:47     ` Glenn Morris
2017-08-27 17:05       ` Alan Mackenzie
2017-08-27 17:21         ` Eli Zaretskii
2017-08-27 17:31           ` Alan Mackenzie [this message]
2017-08-27 17:50             ` Eli Zaretskii
2017-08-27 18:43         ` Paul Eggert
2017-08-27 19:04           ` Alan Mackenzie
2017-08-27 21:38             ` Paul 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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170827173131.GI3520@ACM \
    --to=acm@muc.de \
    --cc=28242@debbugs.gnu.org \
    --cc=eggert@cs.ucla.edu \
    --cc=eliz@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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).