Post #124,263
11/5/03 10:56:09 AM
|
DOS style text graphics in a terminal window?
Based on Andrew's input in the past(much thanx!), we're implementing Vigilant for a chain of weight loss centers in the Houston area. This is on a Red Hat Enterprise 3 system. Vigilant is CLI program and based on screen shots it looks like it's using the old text graphics to draw boxes around options and such. On screen I'm getting letters with accent marks. I found a reference to typing the following at the prompt before running the app: TERM=ansi;export TERM The accented characters changed to graphics, but are still not right. I've tried running in both text mode and via a terminal under Xwindows. Maybe I need a different font? I've tried all the installed fonts with no luck. Darrell Spice, Jr. [link|http://www.spiceware.org/cgi-bin/spa.pl?album=./Artistic%20Overpass|Artistic Overpass]\n[link|http://www.spiceware.org/|SpiceWare] - We don't do Windows, it's too much of a chore
|
Post #124,271
11/5/03 11:46:01 AM
|
It's an endless problem.
There's about 7,284 different ways to interpret the definition of a VT100/VT220/ANSI termianl, and no two programmers ever pick the same interpretation. The termcap used to compile the terminfo files for Linux has a lot of errors and omissions as well.
For this reason I use KoalaTerm for emulation on Windows workstations. It costs $35/pop, but it gives me the flexibility I need to get the function keys to work, and once it's set up it stays that way.
I always install my own terminfo file to go with it too. Remember, Linux uses SVr4 terminfo, so modifying the termcap does nothing until you compile it into a terminfo definition and put it in the right directory.
The other way is Wyse60, but that means expensive terminal emulation programs. American small and medium business has traditionally run 100% on Wyse60, but programmers of low cost emulation are uninterested - Wyse60 isn't used in the universities.
I've talked to several publishers of VT100/200 emulation and they are all completely, totally, 220% uninterested in serving customer needs. All they want to do is produce yet another "BEST" VT220 emulator, and it'll it'll have a different interpretation of how a VT220 works than any of the others.
[link|http://www.aaxnet.com|AAx]
|
Post #124,273
11/5/03 11:53:52 AM
|
PuTTY on Windows
Head and shoulders above all other terminal emulators I've tried, which includes Hummingbird, Tera Term, PowerTerm, blah blah.
Remember I'm connecting to the very definition of VT220, OpenVMS :-)
Behaves perfectly when connecting to AIX, Solaris, Linux, FreeBSD and HP-UX, too - including running ANSI menu-driven programs.
Peter
[link|http://www.debian.org|Shill For Hire]
[link|http://www.kuro5hin.org|There is no K5 Cabal]
[link|http://guildenstern.dyndns.org|Blog]
|
Post #124,326
11/5/03 3:58:01 PM
|
Yeah, the trouble is . .
. . most of the rest of us are not connected to "the very definition of VT220". Linux in particular has ratty termcap/terminfo definitions that need to be fixed before use.
My favorite item is that the lower function keys use completely different coding than the higher function keys, and whether the transition is at F4 or F5 or whatever seems a matter of opinion, but some programmers use one or the other encoding all the way through. Which one appears also to be a matter of opinion.
Anyway, next time I mess with this stuff I'll take a look at PuTTY and see what I think of it. By the way, KoalaTerm makes full use of available TrueType fonts, which many emulators do not.
[link|http://www.aaxnet.com|AAx]
|
Post #124,341
11/5/03 4:58:16 PM
|
It's the very model of any modern major emulator!
--
[link|mailto:greg@gregfolkert.net|greg],
[link|http://www.iwethey.org/ed_curry|REMEMBER ED CURRY!] @ iwethey
|
Post #124,276
11/5/03 11:59:27 AM
|
Re: DOS style text graphics in a terminal window?
This is interaction between the console font and the default encoding. The terminal type should be set to "linux" for a console, and "xterm" or "xterm-color" for an X terminal. The "ansi" entries in termcap are horrible. Then try first: \nsetfont cp850-8x16\n in a console, or start an xterm with the command line: \nxterm -fn -misc-console-medium-r-normal--16-160-72-72-c-80-iso10646-1\n If that doesn't work, change the default encoding to cp437 or cp850 from ISO8859-1. You can alias this long name to something like VGA if you want. -drl
|
Post #124,320
11/5/03 2:57:47 PM
|
What you need then is an ANSI font file with IBM PC graphics
I heard that there is a font named "Terminal" that has the extended IBM PC ANSI characters in it. Built into Windows, but it isn't a True Type Font. Google has failed me, too much information, not what I needed. I did find this: [link|http://groups.yahoo.com/group/OFFSite_Announce/message/1|http://groups.yahoo....nnounce/message/1]
MonoDisplay
MonoDisplay was posted at alt.binaries.fonts by Matthew Balmer on August 21, 2003. The font has 254 characters, which includes upper and lower case letters, numerals, puntuations, accented letters and special characters, like box drawing symbols and greek letters. The font is only available in Open Type format. Matt Balmer's statement about his font:
I've created a font that I wanted to use to replace the "terminal" font that comes with Windows - something that could display the full ANSI character set, and be used to display all the nifty box-drawing characters, etc. Letters, numbers, punctuation, etc., and any program that conforms to what seems like the Windows CP 1251 (ISO Latin 1) character set draws characters correctly, but for whatever reason, the DOS box seems to pay this font no mind, so I can't exactly use it as I intended it. Notepad seems to gleefully ignore the existence of the extended character set too, and it's a problem I can't quite figure out. I haven't filled out the standard Windows character set yet, but the font is usable in its current form.
It is in Open Type, not sure if you can use it, but it sounds like what you are looking for. That is the best site that Google found.
"Lady I only speak two languages, English and Bad English!" - Corbin Dallas "The Fifth Element"
|
Post #124,353
11/5/03 6:34:47 PM
|
I've seen exactly that
though under OS/2 <-> Windows telnetting. It's an artifact of the code page; try getting away from latin-X and going (far) more oldschool (ie- CP437). You're probably looking at things under the latin-1 equiv of CP850 under Warp.
--\n-------------------------------------------------------------------\n* Jack Troughton jake at consultron.ca *\n* [link|http://consultron.ca|http://consultron.ca] [link|irc://irc.ecomstation.ca|irc://irc.ecomstation.ca] *\n* Kingston Ontario Canada [link|news://news.consultron.ca|news://news.consultron.ca] *\n-------------------------------------------------------------------
|
Post #124,386
11/5/03 9:40:03 PM
|
It's the font, stupid.
Your DOS screen graphics are font-dependent. You need an ANSI VGA screen font with linedrawing characters. \r\n\r\n I see this most often showing up in Linux when I switch from standard console to SVGATextMode, which has the side effect of changing screen font. Muck around a bit to find what works. \r\n\r\n And strong second on PuTTY. --\r\n
Karsten M. Self [link|mailto:kmself@ix.netcom.com|kmself@ix.netcom.com]\r\n
[link|http://kmself.home.netcom.com/|http://kmself.home.netcom.com/]\r\n
What part of "gestalt" don't you understand?\r\n
[link|http://twiki.iwethey.org/twiki/bin/view/Main/|TWikIWETHEY] -- an experiment in collective intelligence. Stupidity. Whatever.\r\n
\r\n
Keep software free. Oppose the CBDTPA. Kill S.2048 dead.\r\n[link|http://www.eff.org/alerts/20020322_eff_cbdtpa_alert.html|http://www.eff.org/alerts/20020322_eff_cbdtpa_alert.html]\r\n
|
Post #124,457
11/6/03 10:20:50 AM
|
minor update
saw Revolutions last night(it was great) so didn't spend much time on this before going to bed.
The default terminal does not list very many encoding options. None of the alternatives mentioned here(CP437, CP850, etc) were listed. I tried launching xterm with the -en option and would get warnings along the line of "no CP850 encoding, defaulting to ISO8859-1". Also tried the MonoDisplay font and got the same display results as the other fonts I'd selected.
Thinking back, I've had this same issue(with a CLI program) on an older Red Hat release and was able to get it working. As such, I suspect the issue is related to the missing encoding options.
Due to other commitments I won't be able to do anything else with this until Sunday.
Darrell Spice, Jr. [link|http://www.spiceware.org/cgi-bin/spa.pl?album=./Artistic%20Overpass|Artistic Overpass]\n[link|http://www.spiceware.org/|SpiceWare] - We don't do Windows, it's too much of a chore
|
Post #124,733
11/8/03 10:41:01 AM
|
It won't be called that
in my (admittedly limited) experience, at least. Look for IBM* perhaps? The encodings I'm talking about were all based on "standards" set by IBM back in the '70s and '80s.
--\n-------------------------------------------------------------------\n* Jack Troughton jake at consultron.ca *\n* [link|http://consultron.ca|http://consultron.ca] [link|irc://irc.ecomstation.ca|irc://irc.ecomstation.ca] *\n* Kingston Ontario Canada [link|news://news.consultron.ca|news://news.consultron.ca] *\n-------------------------------------------------------------------
|
Post #124,747
11/8/03 3:44:48 PM
|
right - look in /usr/X11R6/lib/X11/fonts/encodings
ibm-cp437.enc.gz etc.
Unfortunately that doesn't work :/
The "10x20" xterm console font seems to understand linedraw characters without further muckage. So
xterm -fn 10x20
Also simply appending -u8 (make the xterm understand Unicode-8) seems to work with any font having linedraw characters - e.g. Andale Mono, Lucida Console, Courier New..so use the "-fa" option for a TT font and do
xterm -fa "Andale Mono" -fs 12 -u8
-fs is font size in points, of course.
You need X > 4.2 to get an xterm that understands Xft. A modern Red Hat probably has it.
As for console fonts - I use the Neomagic framebuffer device on my laptop and have the sun12x22 console font compiled into the fbcon module. This has line draw capability under ISO-8859-1 without munging anything. The standard VGA font should as well.
-drl
|
Post #124,717
11/8/03 6:19:11 AM
|
While fixing another issue..
..I came across the following rarely used xterm switch: \n +fbx This option indicates that xterm should assume\n that the normal and bold fonts have VT100 line-\n drawing characters.\n So, use the console font indicated in an earlier post an add this switch if necessary. Now if you can just get the keys to work right... -drl
|
Post #125,194
11/11/03 5:11:04 PM
|
minor update 2
We've been having problems in the console(is that the right term for non-GUI terminal?) as well as the terminal emulators. Apparently something's changed between RHE(Red Hat Enterprise) 2.x and RHE 3.
The vendor's been updating the program to run under RHE 2.x(instead of SCO's Linux), however we ended up with RHE 3. Since nobody's yet using Vigilant under RHE, they're switching to 3. They think they'll have an update at the end of the week for us. So I'm going to work on the database instead and worry about this issue after we've received the update.
Darrell Spice, Jr. [link|http://www.spiceware.org/cgi-bin/spa.pl?album=./Artistic%20Overpass|Artistic Overpass]\n[link|http://www.spiceware.org/|SpiceWare] - We don't do Windows, it's too much of a chore
|
Post #128,650
12/3/03 2:08:57 PM
|
New Sourceforge project you should look at Gtermix
See if you can use this Telnet client to run that App in:
[link|http://sourceforge.net/projects/gtermix/|http://sourceforge.net/projects/gtermix/]
"Lady I only speak two languages, English and Bad English!" - Corbin Dallas "The Fifth Element"
|
Post #128,709
12/3/03 5:50:55 PM
|
Thanx!
Darrell Spice, Jr. [link|http://www.spiceware.org/cgi-bin/spa.pl?album=./Artistic%20Overpass|Artistic Overpass]\n[link|http://www.spiceware.org/|SpiceWare] - We don't do Windows, it's too much of a chore
|
Post #128,708
12/3/03 5:49:25 PM
12/3/03 5:51:43 PM
|
interesting update
Aparently Vigilant decided they had enough of Red Hat's changing of the console mode's fonts work between versions and is now considering BSD. It's even possible they'll support Mac OS X in a future release.
edit - subject typo
Darrell Spice, Jr. [link|http://www.spiceware.org/cgi-bin/spa.pl?album=./Artistic%20Overpass|Artistic Overpass]\n[link|http://www.spiceware.org/|SpiceWare] - We don't do Windows, it's too much of a chore
Edited by SpiceWare
Dec. 3, 2003, 05:51:43 PM EST
|
