Date: Sun, 23 Feb 2014 21:01:34 +0400 From: Andrey Chernov <ache@freebsd.org> To: Ed Schouten <ed@80386.nl>, dickey@his.com Cc: arch@freebsd.org, Bryan Drewery <bdrewery@freebsd.org> Subject: Re: terminfo Message-ID: <530A296E.9090805@freebsd.org> In-Reply-To: <CAJOYFBB_K0ziNaTg=ThnCBN1EPU-b_H2kUxsc-MPYNEJHb3Y7w@mail.gmail.com> References: <5304A0CC.5000505@FreeBSD.org> <CAJOYFBCMS4k7pyRk2YHZm81F6iP=SApZhbCm0MO4P-pvXbTCxQ@mail.gmail.com> <20140223115939.GB4084@aerie.jexium-island.net> <CAJOYFBB_K0ziNaTg=ThnCBN1EPU-b_H2kUxsc-MPYNEJHb3Y7w@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 23.02.2014 17:49, Ed Schouten wrote: > This terminfo entry is incorrect. It will make ACS work on a standard > setup where the user has the BIOS CP437 font loaded, but will break > horribly if a user uses a different character set, like ISO-8859-1. > > There is a reason why syscons displays ASCII characters for ACS box > drawing, namely that there is no guarantee that the actual font loaded > into the graphics card has any ACS characters to begin with. Old syscons was able to displays pseudographics, and several cons25-like termcap entries exists to correspond ACS for each console font. It is your emulation which always displays ASCII now, which is step backward. -- http://ache.vniz.net/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?530A296E.9090805>