From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] ISO 8859-15 at the header
Date: Sat, 05 Apr 2008 16:35:13 -0700 [thread overview]
Message-ID: <1207438404-sup-888@south> (raw)
In-Reply-To: <20080403140711.GA482@weisshuhn.de>
Reformatted excerpts from Carsten Sch?lzki's message of 2008-04-03:
> William Morgan <wmorgan-sup at masanjin.net> [03.04.2008 03:12]:
> > It should work, if you have your LANG and stuff all set up
> > correctly. What console character set encoding does Sup detect?
> > (Typically the first message of the log buffer.)
>
> The detecting seems right to me. The log says: using character set
> encoding "ISO8859-15"
This means that as far as Sup can tell, it can emit iso8859-15 directly
to the terminal and not have to worry about transcoding anything. Does
that seem correct?
If so, then this may bring us to the very scary world of "why isn't
ncurses does the right thing on my particular
platform/terminal/encoding setup".
--
William <wmorgan-sup at masanjin.net>
prev parent reply other threads:[~2008-04-05 23:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-27 4:49 Carsten Schölzki
2008-04-03 1:12 ` William Morgan
2008-04-03 14:07 ` Carsten Schölzki
2008-04-05 23:35 ` William Morgan [this message]
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=1207438404-sup-888@south \
--to=wmorgan-sup@masanjin.net \
/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