kallio@tukki.jyu.fi (Seppo Kallio) (04/18/89)
Sorry, the name was Dan Sahlin, do you know his e-mail address? Have anyone tested the code in Aufs version 3.00 Feb 1988? I can see any code modifigations in files, except this cr-lf -transform. I have tested type TEXT, owner unix + .fin and .latin1 ... but I cannot see any visible character modifications. I have checked aufs code and the code tables are there. Seppo Kallio kallio@tukki.jyu.fi kallio@finjyu.bitnet
ragge@nada.kth.se (Ragnar Sundblad) (04/18/89)
In article <577@tukki.jyu.fi> kallio@tukki.jyu.fi (Seppo Kallio) writes: >Sorry, the name was Dan Sahlin, do you know his e-mail address? Dan Sahlin, e-mail: dan@sics.se
kallio@tukki.jyu.fi (Seppo Kallio) (04/19/89)
Yes I did found my error, the FULL_NCS_SUPPORT code is ok. But the Laser Print problem I have still. I have found this: When I use Command-F and output the PostScript0, kermit or zmodem it to the Unix, use macps and lpr -Pps the oe, ae -letters are OK. Direct Print using lwsrv (cap) and oe, ae are replaced by spaces! And I have found why: Commad-F writes \232 \212 \214 octal code to the file but direct print is writing 8-bit characters, and QMS PS 201 does not know these 8-bit characters, or ... what ... they are replaced by spaces, so they do not disappear on the RS232 line (yes?). Should I fix the Prefix or the lwsrv -code? Prefix looks awful, PostScript is not my language. C is not my programming language either, and I know nothing about lwsrv program! Please, answer if you know this problem, know Mac laser prefix or lwsrv. Seppo Kallio Universuity of Jyvaskyla kallio@tukki.jyu.fi kallio@finjyu.bitnet
RSILVERMAN@EAGLE.WESLEYAN.EDU (Richard Silverman) (04/20/89)
Seppo,
I have missed the beginning of this conversation; I assume when you
say "Direct Print" you mean printing via the Macintosh Print Manager, over
an AppleTalk network through a gateway or EtherTalk. Although I am not familiar
with the QMS, it would be very strange if it trashed 8-bit characters;
PostScript has no such prohibition (although using them inhibits portability,
as you are finding out). Likewise, the info should be delivered fine to
lwsrv, so it would seem that lwsrv, or some other entity between it and the
printer is responsible. Perhaps the line settings for the printer port?
Good luck,
Richard Silverman
arpa: rsilverman@eagle.wesleyan.edu Computing Center
bitnet: rsilverman@wesleyan.bitnet Wesleyan University
CIS: [72727,453] Middletown, CT 06457