Re: HEADS UP: ncurses is updated
On Mon, Apr 09, 2007 at 03:55:20PM -0400, Thomas Dickey wrote: For PuTTY, most users have it incorrectly set to xterm(*). There are no clues - so I added the environment variable to help. BTW, we have putty terminal entry for that purpose. -- http://ache.pp.ru/ pgpKG6sfVF1Fr.pgp Description: PGP signature
Re: HEADS UP: ncurses is updated
On Fri, Apr 13, 2007 at 11:28:15PM +0400, Andrey Chernov wrote: On Mon, Apr 09, 2007 at 03:55:20PM -0400, Thomas Dickey wrote: For PuTTY, most users have it incorrectly set to xterm(*). There are no clues - so I added the environment variable to help. BTW, we have putty terminal entry for that purpose. yes - but see http://www.chiark.greenend.org.uk/~sgtatham/putty/faq.html A.5.1 What terminal type does PuTTY use? which is not really helpful. Compare PuTTY and xterm using ftp://invisible-island.net/vttest/ (the difference in wrapping behavior which is evident in the first menu selection is reflected in the different terminal descriptions). -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net pgpVKiSmf2BTF.pgp Description: PGP signature
Re: HEADS UP: ncurses is updated
In muc.lists.freebsd.stable Thomas Dickey [EMAIL PROTECTED] wrote: yes - but see http://www.chiark.greenend.org.uk/~sgtatham/putty/faq.html A.5.1 What terminal type does PuTTY use? which is not really helpful. Compare PuTTY and xterm using As an aside, the second paragraph in that FAQ entry is incorrect, since xterm implements the same title-string control sequences. PuTTY's developers have chosen to selectively use (not limited to this instance) old X11R6 xterm for comparison, while implementing features from modern xterm (since 1996), e.g., the 256-color support. xterm doesn't implement the Linux color palette sequences (though it does recognize a different set with comparable functionality). From xterm's manpage: brokenLinuxOSC (class BrokenLinuxOSC) If true, xterm applies a workaround to ignore malformed control sequences that a Linux script might send. Compare the palette control sequences documented in console_codes with ECMA-48. The default is ``true.'' -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HEADS UP: ncurses is updated
On Sat, Apr 07, 2007 at 02:05:45AM +0800, Rong-en Fan wrote: I just merged ncurses 5.6 and wide character support from HEAD to 6.x. That means ncurses in 6.x is now up-to-date and has wide character support, i.e., ncursesw library. I just wanted to take a moment to thank you for this. You have no idea how long I've been waiting (okay, now you do: years!), as I never felt comfortable with having two versions of ncurses installed on a single box (base + port). So far it works great. Thank you so much! The only thing I've found, though, is that dialog(1) does not appear to properly handle UTF-8 encoding. Line drawing characters show up as gibberish (alphanumeric characters). I realise dialog isn't part of ncurses, but it does rely on it. We should consider updating dialog to match this change. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HEADS UP: ncurses is updated
On 4/10/07, Jeremy Chadwick [EMAIL PROTECTED] wrote: On Sat, Apr 07, 2007 at 02:05:45AM +0800, Rong-en Fan wrote: I just merged ncurses 5.6 and wide character support from HEAD to 6.x. That means ncurses in 6.x is now up-to-date and has wide character support, i.e., ncursesw library. I just wanted to take a moment to thank you for this. You have no idea how long I've been waiting (okay, now you do: years!), as I never felt comfortable with having two versions of ncurses installed on a single box (base + port). So far it works great. Thank you so much! You are welcome. The only thing I've found, though, is that dialog(1) does not appear to properly handle UTF-8 encoding. Line drawing characters show up as gibberish (alphanumeric characters). I realise dialog isn't part of ncurses, but it does rely on it. We should consider updating dialog to match this change. You mean it display sometihng like tqxu instead of line drawing characters? Last time I checked, I thought it is terminal related. When I use screen, it uses line drawing character. For PuTTY, see: http://lists.freebsd.org/pipermail/freebsd-questions/2007-April/146577.html The current dialog + utf8 MacOS's Term.app seems work just fine. I'm playing with devel/cdialog and no matter it uses ncurses or ncursesw the result is the same. I'm CCing ache@ who imports GNU's dialog to our base and cdialog/ncurses author, hope they can comment :-) Regards, Rong-En Fan -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HEADS UP: ncurses is updated
On Tue, Apr 10, 2007 at 01:49:32AM +0800, Rong-en Fan wrote: On 4/10/07, Jeremy Chadwick [EMAIL PROTECTED] wrote: The only thing I've found, though, is that dialog(1) does not appear to properly handle UTF-8 encoding. Line drawing characters show up as gibberish (alphanumeric characters). I realise dialog isn't part of ncurses, but it does rely on it. We should consider updating dialog to match this change. You mean it display sometihng like tqxu instead of line drawing characters? Last time I checked, I thought it is terminal related. When I use screen, it uses line drawing character. For PuTTY, see: http://lists.freebsd.org/pipermail/freebsd-questions/2007-April/146577.html The current dialog + utf8 MacOS's Term.app seems work just fine. I'm playing with devel/cdialog and no matter it uses ncurses or ncursesw the result is the same. I'm CCing ache@ who imports GNU's dialog to our base and cdialog/ncurses author, hope they can comment :-) So here's how to reproduce this. I'm using PuTTY 0.59 (and I have tried using the snapshots as well, same behaviour) on Windows, using a font that has Unicode line-drawing characters. PuTTY is set for ISO-8859-1 encoding/translation. My UNIX environment: TERM=xterm export LANG=en_GB.ISO8859-1 export LC_CTYPE=en_GB.ISO8859-1 export LC_COLLATE=C Results of COLUMNS=40 dialog --msgbox testing 6 30 (sorry if this doesn't come across right, but if I save it to a file and cat it, it does appear correctly): ââââââââââââââââââââââââââââââ â testingâ ââ âââââââââââââââââââââââââââââ⤠â[ OK ]â ââââââââââââââââââââââââââââââ Now we change PuTTY encoding/translation to UTF-8, and the UNIX environment to: export LANG=en_GB.UTF-8 export LC_CTYPE=en_GB.UTF-8 Results of COLUMNS=40 dialog --msgbox testing 6 30 : lk x testingx xx tu x[ OK ]x mj mutt and other apps, however, draw line characters just fine with this configuration. This is what I meant by specific to dialog(1). Hope this helps. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HEADS UP: ncurses is updated
On Mon, Apr 09, 2007 at 11:21:08AM -0700, Jeremy Chadwick wrote: On Tue, Apr 10, 2007 at 01:49:32AM +0800, Rong-en Fan wrote: On 4/10/07, Jeremy Chadwick [EMAIL PROTECTED] wrote: The only thing I've found, though, is that dialog(1) does not appear to properly handle UTF-8 encoding. Line drawing characters show up as gibberish (alphanumeric characters). I realise dialog isn't part of ncurses, but it does rely on it. We should consider updating dialog to match this change. You mean it display sometihng like tqxu instead of line drawing characters? Last time I checked, I thought it is terminal related. When I use screen, it uses line drawing character. For PuTTY, see: http://lists.freebsd.org/pipermail/freebsd-questions/2007-April/146577.html This is quite applicable. I just now got around to reading it (should've done this before I sent my previous Email). Yep, that's the exact problem: /usr/bin/dialog: libdialog.so.5 = /usr/lib/libdialog.so.5 (0x3807e000) libncurses.so.6 = /lib/libncurses.so.6 (0x38099000) libc.so.6 = /lib/libc.so.6 (0x380dd000) At least I have a workaround with NCURSES_NO_UTF8_ACS=1. :-) -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HEADS UP: ncurses is updated
On Tue, Apr 10, 2007 at 01:49:32AM +0800, Rong-en Fan wrote: ... You mean it display sometihng like tqxu instead of line drawing characters? Last time I checked, I thought it is terminal related. When I use screen, it uses line drawing character. For PuTTY, see: PuTTY implemented UTF-8 much later than screen and Linux console. Those (the last two) tend to have $TERM set properly (at least half the time). I could let ncurses guess what to do based on $TERM and locale. For PuTTY, most users have it incorrectly set to xterm(*). There are no clues - so I added the environment variable to help. (*) It's incorrect because in several areas it does not match xterm. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net pgpZMNr5k30YW.pgp Description: PGP signature
Re: HEADS UP: ncurses is updated
On Monday, 9 April 2007 at 11:48:08 -0700, Jeremy Chadwick wrote: On Mon, Apr 09, 2007 at 11:21:08AM -0700, Jeremy Chadwick wrote: On Tue, Apr 10, 2007 at 01:49:32AM +0800, Rong-en Fan wrote: On 4/10/07, Jeremy Chadwick [EMAIL PROTECTED] wrote: The only thing I've found, though, is that dialog(1) does not appear to properly handle UTF-8 encoding. Line drawing characters show up as gibberish (alphanumeric characters). I realise dialog isn't part of ncurses, but it does rely on it. We should consider updating dialog to match this change. You mean it display sometihng like tqxu instead of line drawing characters? Last time I checked, I thought it is terminal related. When I use screen, it uses line drawing character. For PuTTY, see: http://lists.freebsd.org/pipermail/freebsd-questions/2007-April/146577.html This is quite applicable. I just now got around to reading it (should've done this before I sent my previous Email). Yep, that's the exact problem: /usr/bin/dialog: libdialog.so.5 = /usr/lib/libdialog.so.5 (0x3807e000) libncurses.so.6 = /lib/libncurses.so.6 (0x38099000) libc.so.6 = /lib/libc.so.6 (0x380dd000) At least I have a workaround with NCURSES_NO_UTF8_ACS=1. :-) I am not sure, but maybe this is related to ncurses update. I am getting this trying to run sysinstall utility: Probing devices, please wait (this can take a while)...BARF 170 105 Than goes EOL and exit... It's a current from April 6. -- == - Best regards, Nikolay Pavlov. --- == ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HEADS UP: ncurses is updated
On 4/10/07, Nikolay Pavlov [EMAIL PROTECTED] wrote: On Monday, 9 April 2007 at 11:48:08 -0700, Jeremy Chadwick wrote: On Mon, Apr 09, 2007 at 11:21:08AM -0700, Jeremy Chadwick wrote: On Tue, Apr 10, 2007 at 01:49:32AM +0800, Rong-en Fan wrote: On 4/10/07, Jeremy Chadwick [EMAIL PROTECTED] wrote: The only thing I've found, though, is that dialog(1) does not appear to properly handle UTF-8 encoding. Line drawing characters show up as gibberish (alphanumeric characters). I realise dialog isn't part of ncurses, but it does rely on it. We should consider updating dialog to match this change. You mean it display sometihng like tqxu instead of line drawing characters? Last time I checked, I thought it is terminal related. When I use screen, it uses line drawing character. For PuTTY, see: http://lists.freebsd.org/pipermail/freebsd-questions/2007-April/146577.html This is quite applicable. I just now got around to reading it (should've done this before I sent my previous Email). Yep, that's the exact problem: /usr/bin/dialog: libdialog.so.5 = /usr/lib/libdialog.so.5 (0x3807e000) libncurses.so.6 = /lib/libncurses.so.6 (0x38099000) libc.so.6 = /lib/libc.so.6 (0x380dd000) At least I have a workaround with NCURSES_NO_UTF8_ACS=1. :-) I am not sure, but maybe this is related to ncurses update. I am getting this trying to run sysinstall utility: Probing devices, please wait (this can take a while)...BARF 170 105 Than goes EOL and exit... It's a current from April 6. The ncurses update to 5.6 is in late Jan, and enable wide character support it in late Feb. My sysinstall runs just fine under console and rxvt-unicode on my currenct as of yesterday. -- == - Best regards, Nikolay Pavlov. --- == ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
HEADS UP: ncurses is updated
Hi all, I just merged ncurses 5.6 and wide character support from HEAD to 6.x. That means ncurses in 6.x is now up-to-date and has wide character support, i.e., ncursesw library. Regards, Rong-En Fan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
