Date: Sun, 20 Jan 2013 13:46:30 -0500 From: Thomas Dickey <dickey@radix.net> To: David Lazaro Saz <dlazaro@mac.com> Cc: Devin Teske <dteske@freebsd.org>, FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: bsdinstall(8) line drawing characters Message-ID: <20130120184630.GA6610@saltmine.radix.net> In-Reply-To: <633A6573-BCDA-41CD-A5CA-1749DE36283A@mac.com> References: <1C064C2C-52A4-4A37-AB3D-68049093D7BD@mac.com> <88E25E2A-24EE-491A-B82A-A26E849B1ABF@fisglobal.com> <633A6573-BCDA-41CD-A5CA-1749DE36283A@mac.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--SLDf9lqlvOQaIe6s Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Jan 20, 2013 at 04:03:31PM +0100, David Lazaro Saz wrote: >=20 > On Jan 20, 2013, at 2:50 PM, Devin Teske <devin.teske@fisglobal.com> wrot= e: >=20 > > Of interest I would think is the output of: > >=20 > > dialog --version > > echo $TERM > >=20 > > and whether (if possible) sysinstall produces similar results (what rel= ease are you running?) >=20 > I'm still running 8.3 in production. I've noticed this while playing with= 9.0 and 9.1 both on vmware and older machines. >=20 > I think that you are right and it has to do with the TERM variable and ho= w it is set in the system console. In 8.3, the system console is defined as= "cons25" while on 9.1 it is defined as "xterm". If I execute the following= command: >=20 > # TERM=3Dcons25 bsdinstall >=20 > Then the line drawing characters are show correctly on the system console= . If I do the opposite on 8.3, defining TERM as xterm, then the results are= even worse than on 9.1. >=20 > dialog(1) is on version 1.1-20100428 on 9.1 and on version 0.3 on 8.3. >=20 > I can't find neither when nor why the system console was changed to xterm > looking at the release notes of FreeBSD 9.0, but this seem to be the reas= on.=20 > The TERM variable is defined on /etc/ttys, so I'll try to find the change= on > the svn repository to shed some light. TERM is one thing, the driver is another. Since the "xterm" terminal description supports line-drawing characters, it sounds as if the underlying problem is in the console driver. ncurses would use ASCII characters if it is told that the terminal cannot use line-drawing characters. However, it uses the VT100 line-drawing characters if possible. Running vttest establishes that the issue is not in ncurses (menu item 3, character sets). That shows only ASCII characters. --=20 Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net --SLDf9lqlvOQaIe6s Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (SunOS) Comment: For info see http://www.gnupg.org iD8DBQFQ/DuDtIqByHxlDocRAs1VAKCL8K1nc7Qf1EZonzQGkTbW9tckaQCePIda caQFXjZ4hiY2T2NhtTVS/0E= =FF0A -----END PGP SIGNATURE----- --SLDf9lqlvOQaIe6s--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130120184630.GA6610>