[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

403.0. "Scandinavian chars & VTX$QUEUE (or OA$FORMATTER)" by EEMELI::SIRO (Welcome to my fog! -I guess...) Thu Apr 02 1992 20:18

Hi,

	I'm sure that one of you can tell me HOW.

	Problem is that when you print WPL-file to VTX$QUEUE
	all those strange scandinavian characters like �, � and
	� are generated to output file using method 
	
	<ESC>(<            ^N           D               ^O
	-------            **           �               ##
	char set to Gn     shift out    char � in set   shift in

	OA$FORMATTER is working the same way. 

	First of all I DO NOT understand why it should work like that
	within v 2.3 & 2.4; during 2.1 it was working in 'the good 
	old fashioned way'. Anyway 8-bit char set has �, � and �. 
	The method has cost a lot to our support people, some LN03 
	problems and now a problem with VTX. 

	The case is that the customer makes VTX page using WPS-PLUS 
	editor and then paginating it by printing the document through
	VTX$QUEUE and updating it to VTX using WORKBENCH (WB is
	not important part). And THIS IS *NOT* VTX case, so don't,
	please, tell me to put this to VTX conference.

	So, in VTX database there is, for example, � showed as a string
	<ESC>(>^ND^O. When you look the VTX page using VT terminal
	everything is OK. *BUT* if you use ALL-IN-1 in PC, naturally
	PC don't have the mentioned character set and the emulator ignores 
	all the esc's and shows the char on the screen as D.
	
	To the solving part (at last): What I want is to find a way
	to generate 'real' � (decimal 196 in DEC Multinational Character
	Set) to the output file instead of <ESC>(>^ND^O. 

thanks in advance
	       risto

T.R	Title	User	Personal Name	Date	Lines
403.1	WPS-PLUS Formatter	IOSG::NEWLAND	Richard Newland, IOSG, REO1-D/4A	`Fri Apr 03 1992 12:12`	39
	> First of all I DO NOT understand why it should work like that > within v 2.3 & 2.4; during 2.1 it was working in 'the good > old fashioned way'. Anyway 8-bit char set has �, � and �. > The method has cost a lot to our support people, some LN03 > problems and now a problem with VTX. It's the way that the WPS-PLUS V3.0 and V3.1 formatter creates the listing file, and as you have observed it seems to be different from WPS-PLUS V2.1. The versions of WPS-PLUS integrated into ALL-IN-1 are: ALL-IN-1 V2.1 -- WPS-PLUS V2.1 ALL-IN-1 V2.3 -- WPS-PLUS V3.0 ALL-IN-1 V2.4 -- WPS-PLUS V3.1 > OA$FORMATTER is working the same way. The same WPS-PLUS formatter routine is linked into OA$FORMATTER and OA$MAIN. It is to be expected that when OA$FORMATTER is performing WPS-PLUS formatting that the same results will occur. > To the solving part (at last): What I want is to find a way > to generate 'real' � (decimal 196 in DEC Multinational Character > Set) to the output file instead of <ESC>(>^ND^O. You could create a new WPS-PLUS Printer Character Table which uses DEC Multinational Characters directly, and then modify the ALL-IN-1 Printer entries to use this WPS-PLUS printer table when printing to the VTX$QUEUE printer destination. Since this is an issue with the WPS-PLUS formatter you may get further help in the WPS-PLUS conference. Richard
403.2	Solved	KIPPIS::SIRO	Welcome to my fog! -I guess...	`Fri Apr 03 1992 13:29`	30
	> It's the way that the WPS-PLUS V3.0 and V3.1 formatter creates the listing > file, and as you have observed it seems to be different from WPS-PLUS V2.1. Yes, I know that. But I am wondering why not to use Multinational characters instead using DEC Supplemental Graphic Character Set. > You could create a new WPS-PLUS Printer Character Table which uses DEC > Multinational Characters directly, and then modify the ALL-IN-1 Printer > entries to use this WPS-PLUS printer table when printing to the VTX$QUEUE > printer destination. This is exactly what I did first thing in the morning. For those who are interested: the characters which need to be modified are 196 (�), 197 (�), 214 (�), 228 (�), 229 (�) and 246 (�). Table should look like this after modifications: ---------------------------------------------------------------------------- CHR Cell 1 Cell 2 Cell 3 ---------------------------------------------------------------------------- 196 196 -1 -1 197 197 -1 -1 . . thanks risto