I often create postscript files on a Mac, PC or NT system and transfer it to
one of our workstations. I've always used ASCII ftp without problems on Suns
and Ultrix.
Since I've got an Alpha with DU 3.2, I've noticed that the ftp connection
(initiated from the Mac or PC side) gives a message
230-WARNING! nnn bare linefeeds received in ASCII mode
File may not have transferred incorrectly
after which the ftp client hangs for several minutes.
Apparently the transfer is OK, only there is this annoying hangup.
To avoid this I started using binary ftp. Of course this does NOT convert
carriage returns into newlines, but, in accordance to postscript specs, this
does not do any harm to me (I can use dxvdoc to preview and print to an Apple
printer). Unfortunately some of my remote correspondents complain.
(I told them to do a tr '\015' '\012' to convert returns into newlines, so
please do not tell me that !).
What I'm asking is a way (some hidden QUOTE command ?) to avoid the "bare
linefeed hangup", and use good old ascii ftp as it used to be.
----------------------------------------------------------------------------
A member of G.ASS : Group for Astronomical Software Support
----------------------------------------------------------------------------
Lucio Chiappetti - IFCTR/CNR | Ma te' vugl' da' quost avis a ti' Orsign
via Bassini 15 - I-20133 Milano | Buttet rabios intant te se' pisnign
Internet: LUCIO_at_IFCTR.MI.CNR.IT | (Rabisch, II 46, 119-120)
----------------------------------------------------------------------------
For more info :
http://www.ifctr.mi.cnr.it/~lucio/personal.html
----------------------------------------------------------------------------
Received on Mon Oct 21 1996 - 21:23:29 NZDT