[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

3389.0. "Confused by pound signs?? - You will be..." by KERNEL::VANRIXTELE (Emma van Rixtel) Wed Oct 13 1993 18:17

Cross posted in WPS-PLUS conference (1365.0)
--------------------------------------------

Hello, I have a customer, who is using ALL-IN-1 V2.4, and when printing pound 
signs to a Cannon printer via a print queue it prints out ok, but when printed
to the same printer via a port he gets a '2' instead???!!!

I asked him to print the same document to the queue using the foreground 
formatter to see if this gave the same result but it did not! 

Has anyone any ideas, why this would happen ?

Also, to confuse you even more, he has 2 users which when say receiving mail,
one of them can see the pound sign straight away, but when they log out and log
back in again, the pound sign changes to a # and remains a #. The other user 
sees this the opposite way round. They first view the pound sign as a hash, but 
after logging out and then in again, it appears as a pound sign and stays a 
pound sign!!

They are using PC's with Pathworks, but the same thing is happening if they use
a VT terminal. One of the pc's (the one that see's the pound sign first then the
#) is set to 7 bit and the other to 8 bit.

Has anyone ever heard of this happening before as I am totally confused...


Emma.

T.R	Title	User	Personal Name	Date	Lines
3389.1	Sounds like a terminal/queue/port setup problem	SCOTTC::MARSHALL	Spitfire Drivers Do It Topless	`Wed Oct 13 1993 19:45`	14
	My recommendation to the basenoter is to set all the terminal lines to 8 bit if possible, to allow the DEC MCS character set to be transmitted correctly. Make sure everything everywhere is configured for eight bits, and understands the DEC MCS character set. I suspect the print queue is converting the MCS pound sign to a character the printer understands, but that when printing via the port, no usch conversion is being performed. Without having access to the printer, its manual showing printable character tables, your VT terminals and lines, etc, it's hard to say anything more specific, or suggest how you can get pound signs on the port printer. Most printers these days have such characters as the pound sign user-definable anyway, maybe that would be the best thing to do? Scott
3389.2	Which � signs?	IOSG::NEWLAND	Richard Newland, IOSG, REO2-G/L2	`Wed Oct 13 1993 20:18`	22
	How are the � signs being created? Some DEC terminals and printers (and particuarly those sold in the UK where I'm assuming the customer is) can be set-up so that the # character (Numeric code - Hex 23, Decimal 35, Octal 43) is printed as a pound sign. If the users are creating � signs in this way then all terminals and printers must be set-up in the same way. If you are using terminals and printers which support the DEC Multinational or the ISO Latin-1 character sets a pound sign can be generated using 'Compose' 'L' '-' (Numeric code - Hex A3, Decimal 163, Octal 243). Is the same Print Style, and therefore WPS-PLUS Printer Table, being used when printing to a queue and the port printer? What WPS-PLUS Printer Table is being used, and has it been created by the customer? Richard
3389.3	similar on Laserjets ?	TOPPER::BARHAM	Norbert:	`Tue Dec 07 1993 17:11`	62
	ALL-IN-1 3.0, SETHOST 4.? I think I have the same problem but on both HP Laserjet II's and III's with uncustomised LASERJET and HPLJIII tables. The customer is printing in parallel from a DEC 220 PC with a LK250 or Gold LK250 keyboard. They log in to VMS via sethost from the PC first. Since character 035 is printed for a Shift 3, we changed this in the HPLLFF.PRC printer character table to equal the character � (same as character 163). This worked fine for me but the customer gets the following results printing to PORT or 'networked' printers :- Where to Print style Output Character Set on printer PORT LASERJET ;;; ISO-4 PORT LASERJET ;;; Roman 8 NETWORK LASERJET �� ISO-4 NETWORK LASERJET �� Roman 8 PORT LP11 �� ISO-4 PORT LP11 ### Roman 8 Printing to FILE, style LASERJET/HPLJIII shows the � character is correctly output for a � sign. So the problem is that what he calls 'networked' or 'queued' printers print � signs fine whatever the character set on the printer but when printing to PORT with LASERJET (or HPLJIII) he gets ;;; characters. I want him to try it on a VT terminal but he says he doesn't have one. The PC group suggested that in DOS he do SET NVTNRC=1 which prevents a $SET TERM/INQUIRE from replacing your National Replacement Character Set with the DEC Multinational Character Set. (although I think we do actually want the DEC multinational character set! Still works for me anyway.) Then within sethost try choosing NRC mode and British Character Set (under GENERAL) and Digital LK250 keymap (under KEYBOARD) since they are using lk250's. This had no effect, neither did changing between 7 and 8 bit. I got him to print to file and copy the VMS file to DOS. This file appears to contain double top right square brackets (like character 012 or 297) in place of the double chevron � when editted from DOS but they print out as � signs when he does COPY FILE LPT1: Does this mean the port setup is OK ?? I also attempted the COPY_TO_PORT function but have been unable to get it working. I did <get #a="disk:[username]filetoprint.txt" <copy_to_port #a but nothing happened. Is this wrong ? So the question is, what could be causing ;;; characters to print in place of �� signs when printing to PORT ? I would like to blame sethost setup but I can't think what else to check.