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

Conference iosg::all-in-1_v30

Title:	OLD ALL-IN-1 (tm) Support Conference
Notice:	Closed - See Note 4331.l to move to IOSG::ALL-IN-1
Moderator:	IOSG::PYE

Created:	Thu Jan 30 1992
Last Modified:	Tue Jan 23 1996
Last Successful Update:	Fri Jun 06 1997
Number of topics:	4343
Total number of notes:	18308

1039.0. "LIST function and ESCAPE SEQUENCES" by OASS::AMATO_A () Mon Jul 13 1992 21:44

    Hello,
    
    Under 2.4 I was able to use the LIST function to display an ASCII file
    with escape sequences to the screen and the escape sequences were 
    interpreted correctly. If I use the LIST function to display the same 
    ASCII file in 3.0 the actual escape sequences are displayed.
    
    Do I need to do something different in 3.0  to display a file with
    escape sequences?
    
    Thanks,
    
    Angela

T.R	Title	User	Personal Name	Date	Lines
1039.1	LIST was changed in V3.0	IOSG::NEWLAND	Richard Newland, IOSG, REO1-D/4A	`Mon Jul 13 1992 23:21`	92
	The LIST function was changed in V3.0 so that it did not display control sequences. Attached are notes discussing this change from the DIAMONDFT conference. Richard ================================================================================ Conference: diamondft Topic title: Displaying <ESC> characters in READ Note title: Lines: 29 Author: EVTAI1::PROT Number: 202.0 Created: 20-Nov-1991 17:27 Replies: 2 -------------------------------------------------------------------------------- BL90 ---- One account on the system has EDT as editor, and creates a document. Then he types some ESCAPE sequences like <ESC>[1m <ESC>[0m to get some particular renditions, and exit. When he reads or print to terminal, all the <ESC> are replaced by a black box on the screen. But if he read the same document in V2.4 he got the good rendition (bold or reverse). I think that this behavior occurs because now the list option in Diamond is able to handle non-revisable documents, and then always translate <ESC> to boxes. This a big problem for some sites where users was used to create and send such kind of documents. Now they can't read them. Why the TEXT DSAB doesn't check if the document is revisable or not before translating the <ESC> ? It would be interesting to translate only for non-revisable documents, and not translate for revisable documents, including EDT documents containing such escape sequences. Regards. Louis ================================================================================ Conference: diamondft Topic title: Displaying <ESC> characters in READ Note title: LIST changed for security Lines: 28 Author: IOSG::NEWLAND Richard Newland, IOSG, REO1-D/4A Number: 202.1 Created: 20-Nov-1991 18:35 Replies: 2 -------------------------------------------------------------------------------- LIST has been changed in ALL-IN-1 V3.0, but not for the reason you have suggested. LIST does not send escape and control sequences to the terminal. The V2.4 behaviour of passing all escape and control sequences caused problems if the sequences were not understood by the terminal. A common situation was listing an LN03 file, which usually locked up the terminal and required a hardware reset of the terminal to recover. Also, sending escape and control sequences is not considered good for security because a message could contain sequences which perform some operation on the user's terminal or PC terminal emulator when it is displayed. Other VMS utilities, such as VMS mail, take the same approach as ALL-IN-1 V3.0 LIST in not sending escape sequences to the terminal. The document can be displayed using Print to TYPE, because this uses the VMS TYPE command which does not attempt to prevent control sequences being sent to the terminal. I think it would be unusual for users to create and mail such documents because they can only be printed to a printer which also understands the terminal display sequences. Richard ================================================================================ Conference: diamondft Topic title: Displaying <ESC> characters in READ Note title: Yes Lines: 2 Author: EVTAI1::PROT Number: 202.2 Created: 21-Nov-1991 15:31 Replies: 2 -------------------------------------------------------------------------------- Ok , Print to TYPE does what we need. Thanks.
1039.2		EVTDD1::WOOD		`Thu Sep 24 1992 10:03`	30
	I have a problem with an application where ALL-IN-1 documents are made with characters to enable line drawing. Since V3, all the characters are visible as explained earlier, the users don't like it. I told them that P TYPE, (print to destination TYPE) would give a workround where they could see what was 'meant' in the document and this works OK. However, once a user has done this print, for the rest of their session they are able to read their documents normally with the lines being correctly interpreted. This has led to the inevitable question, "Is there something you can set at login time so they don't have to do the initial Print to TYPE" Below is an example of a bit of line drawing. Regards, Dave Wood )0~[70;100 B[4 L[0 J [?21 J Text Page:1 Run Date : 24-SEP-1992 �� Text � � � Some more text � Heading � Heading � � Text � xyz � abcdefghijk � abcdefghi � abcdefghi � abcdefghi � abcdefghi � Text � Text � �� 1234 � xy � abcdefghijklmn � abcdefg � abc � abc � abc � abc � abc � [0 J
1039.3	Programming terminal	IOSG::NEWLAND	Richard Newland, IOSG, REO1-D/4A	`Thu Sep 24 1992 12:15`	20
	I have been able to reproduce the behaviour you have reported with the example line drawing control sequence. However, if after I have done the Print to TYPE I do any of the following: - Run the EDT or WPS editors - Run the WPS-PLUS editor - Reset the terminal a LIST operation reverts to the standard behaviour. I haven't examined the VT220 control sequences in detail but I guess that they are reprogramming the terminal so that it interprets the block characters sent by LIST as ESC characters. Given that operations such as using an editor undo the reprogramming of the terminal I can't see that doing things at login time will ever work. Richard