There are a couple of reasons for this.  The simplest may be that the
    font that you are using does not support line drawing characters.
    Simply switching fonts to a dec-vt220 compatible font may solve the
    problem.  This is usually the case with Windows telnet applications.

    Another reason for this is that your terminfo file may not be set up
    properly. The obvious solution is fix the terminfo file.  However, this
    may not be possible without the correct tools (untic and tic) and many
    systems do not have those tools installed.

    Although slang is a terminfo based system, there is another solution
    based on termcap if you are using version 0.99.18 of slang or later.
    First of all, get a termcap entry that contains the appropriate
    capabilities for an alternate character set, that is, the termcap `ac',
    `ae', `as', and possibly `eA' capabilities.  Let's call this file
    `my_termcap'.  Then do:

      setenv TERMCAP `pwd`/my_termcap
      eval `tset -s terminal-name`

    (Replace `terminal-name' by your terminal name).  `tset' will then read
    and parse the my_termcap file and set the TERMCAP variable
    appropriately. You will want to put this in your .login file.


User Contributions:
Comment about this article, ask questions, or add new information about this topic:
Name:
E-mail:
Display email publicly
Security Code:
Comment:  (50-4000 characters)

 




Archived related questions and answers