[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference iosg::all-in-1

Title:ALL-IN-1 (tm) Support Conference
Notice:Please spell ALL-IN-1 correctly - all CAPITALS!
Moderator:IOSG::PYECE
Created:Fri Jul 01 1994
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:2716
Total number of notes:12169

2607.0. "Displaying technical characters" by SNOFS1::JOYCEJENNY (Still crazy after all these years) Tue Apr 08 1997 04:14

    Chapter 4 of the ALL-IN-1 WPS-PLUS User's Reference talks about the
    Technical Character set and says "to display or print technical
    characters you must have the required hardware...Even if you have the
    required hardware, you may have to set your terminal differently or
    reset your system characteristics".
    
    Unfortuneatley it doesn't specify what the required hardware is, or
    what terminal or system characteristics need to be set to display the
    technical characters.
    
    Can anyone shed any light on what needs to be done to display them
    (printing works ok).
    
    
    Jenny Joyce
    
T.RTitleUserPersonal
Name
DateLines
2607.1Not much help but...IOSG::ELLIOTTRRussell ElliottTue Apr 08 1997 10:4320
    Jenny,
    
    I believe it was left deliberately vague because there are many
    different types of display media and there would be even more
    introduced during the lifetime of the documentation. It was probable
    that any specifics would be either wrong, out of date or confusing at
    some stage.
    
    The required hardware would be a VT or a monitor (plus terminal
    emulator) capable of displaying all eight bit characters. Any terminal
    or system characteristics would be specific to the VT, monitor or
    terminal emulator.
    
    To confuse matters it is my experience that just because some eight bit
    characters are displayed correctly, doesn't mean that they all will be!
    
    HTH,
    Russ.
    
    
2607.2What about SYSGEN parameterssSNOFS1::JOYCEJENNYStill crazy after all these yearsWed Apr 09 1997 01:5414
    We're trying this on both VT340's and DECTERMS, and I believe both
    should be capable of displaying the 8-bit characters.
    
    Are there any SYSGEN parameters I should be checking out?
    
    The reason I ask is that I have a user who insists that it used to work
    in the previous version of ALL-IN-1 which we ran on a different cluster
    (hence different system parameters.  He is a power user, and not the
    sort with whom I feel I should dismiss claims of "it used to work". 
    BTW, he admits it never worked for all the characters, but says it
    definitely used to work for some of them.
    
    
    Jenny
2607.3SYS$MANAGER:A1WPSPLUS_LOGIN.COM ??IOSG::PYEGraham - ALL-IN-1 Sorcerer's ApprenticeWed Apr 09 1997 10:072
    Has the new system got A1WPSPLUSLOGIN.COM in its SYLOGIN? And is it
    identifying a terminal that it knows about?
2607.4Some more info...IOSG::ELLIOTTRRussell ElliottWed Apr 09 1997 10:2420
    Jenny,
    
    The only setting I am aware of is the $set term/eight_bit. I don't know
    about there being any SYSGEN parameters (which doesn't mean there
    aren't any!).
    
    One thing to bare in mind is the difference between Reading and
    Editing. The sequences sent to the terminal are different. If you are
    in a WPS-PLUS edit session then most Technical characters are displayed
    as their fallback characters. When you Read the same document the
    characters _should_ be displayed correctly (assuming the terminal is
    set up correctly).
    
    To demonstrate this, pull the WPL$LIB:CHARACTER.WPL document into your
    filecab and read it. Near the end the technical character set is
    displayed. If this works OK now edit the document and see the
    difference. If the read doesn't work then there's still a problem with
    the terminal setup.
    
    Russ.
2607.5A1WPSPLUS_LOGIN and WPKEYBOARD to set up terminalCOPCLU::ELINElin Christensen @DMO, DTN 857-2406Wed Apr 09 1997 18:5815
    
    Both DECterms and VTs from VT200 and up can display technical
    characters in WPS-PLUS.
    
    If you execute these commands before entering ALL-IN-1, I think you'll
    succeed:
    
    $  @SYS$MANAGER:A1WPSPLUS_LOGIN.COM
    $! Put your own LLV language instead of DANISH in the next line:
    $  @OA$LIB:WPKEYBOARD KB_VT200_DANISH  
    
    You can put the lines into your LOGIN.COM.
    
    Elin
    
2607.6A few detailsSHRMSG::HOWARDWhoever it takesWed Apr 09 1997 19:5221
    There were a lot of discussions about this in the WPS-PLUS conference
    many years ago.  I don't think much has changed.  The previous replies
    appear to be correct to me, but I thought I would throw in a few more
    details of what A1WPSPLUS_LOGIN is trying to do.
    
    There's a tricky logical that has to be defined for ALL-IN-1 to
    use TCS. It gets defined by A1WPSPLUS_LOGIN.COM.  In addition, the TCS
    has to be in the terminal or emulator.  If it isn't there by default,
    the terminal has to have the capability of loading it from the host
    (e.g., the VT220).
    
    Some terminals have the TCS loaded by default, and some do not. 
    A1WPSPLUS_LOGIN.COM is supposed to "know" which ones do.  My
    recollection is that VT220's and VT320's do not, but VT240's and
    VT330's do.  I don't remember about VT400-class terminals, and you
    would have to check the documentation for terminal emulators on PC's. 
    Some terminals, such as VT100's, cannot do TCS at all.  I would
    ass*u*me this to be true of VT100 emulators.  I think the DECterm
    emulators were covered in previous replies.
    
    Ben
2607.7Fixed!SNOFS1::JOYCEJENNYStill crazy after all these yearsThu Apr 10 1997 02:2814
    I've got it working to the user's satisfaction now.  The problem was
    the A1WPSPLUS_LOGIN, but I'd tested that and it didn't seem to solve
    the problem - what threw me was that I was testing it from a DECterm by
    reading the message and couldn't see the TCS.  Then I tried editing the
    document and the characters were all there!  So then I got the user to
    check, and he could see them on both read and edit from his terminal. 
    So I'd say the problem is solely with the DECterms, and when I
    mentioned this to the user he said "oh, no, it's never worked from a
    DECterm."  I could have saved myself some greif if he'd told me that
    before.
    
    Thanks for everyone's help
    
    Jenny