Re: Formatting ASCII to be read by Windows NotePad

"Waylen Gumbal" <wgumgfy@xxxxxxxxx> writes:

Sherman Pendley wrote:
"Waylen Gumbal" <wgumgfy@xxxxxxxxx> writes:

Sherman Pendley wrote:
UnRiel <bdwhite@xxxxxxxxx> writes:

I have a nice PERL script I use to generate CISCO configurations

No need to shout - neither Perl nor Cisco are acronyms.

I don't think two all-caps words in a sentence that's otherwise
properly cased really constitutes shouting.

It's shouting those words.

Not in that context it wasn't.

You must be new to usenet. All caps is considered shouting here,
unless that's the correct spelling of a word or acronym, and as I
said, that applies to neither Perl nor Cisco.

Transfer the files in text mode. That will translate the line
endings as needed.

While it is common to use ASCII mode one should still take care, as
this isn't always guarenteed to work. There used (still are?) issues
with this when uploading to MacOS based servers, for example.

Such as?

I've had issues in the past uploading to a MacOS based ftp server
(remember that Mac uses \r for line endings, where as Win32 uses \r\n,
and most Linux and Unix systems use \n)

I've been using a Mac for ten years, and I wrote the readme.macosx
that's included with Perl. So spare me the lectures.

Yes, I do remember that MacOS once, many years ago when "classic"
MacOS was relevant, used to use \r. Mac OS X uses \n, just like any
other Unix, as documented here:

<http://developer.apple.com/documentation/MacOSX/Conceptual/BPFileSystem/Articles/FileSystemGuidelines.html>
<http://tinyurl.com/58w7dy>

This ain't your grandpa's Mac any more. Try to keep up, OK?

and when uploading in "ASCII"
mode, the line endings became \n instead of \r (this happened with 3
different ftp clients, including the command line ftp client, so I
attribute the problem likely was the server wasn't properly telling the
client what sort of platform it was (what line endings it used.)

You're beginning to try my patience. This is little more than "it
didn't work." What *specific* server app were you connecting to? What
client were you using? What version of both?

Note that according to RFC 959, the client sends \r\n pairs in ASCII
mode, which the server translates to its native format. Because a
"neutral" format is used in transit, neither client nor server is
aware, nor needs to be aware of the native format used by the other,
by design. Your attribution of the problem, as you wrote it above,
makes no sense.

Do you have anything *useful* to say here? Do you actually understand
the FTP protocol? Did you actually debug the problem you had? Or are
you basically just saying "I had a problem in the past, and it must
have been the Mac at the other end because Macs are weird"?

sherm--

--
My blog: http://shermspace.blogspot.com
Cocoa programming in Perl: http://camelbones.sourceforge.net
.

Relevant Pages

  • Re: Mac file names too long??
    ... > Thank you for posting in SBS newsgroup. ... > networking settings on the MAC; modify the directory service options; ... > some settings on the SBS server need to be changed. ... > I. Check the TCP/IP properties of the MAC client. ...
    (microsoft.public.windows.server.sbs)
  • RE: Mac file names too long??
    ... Thank you for posting in SBS newsgroup. ... Generally speaking, for the SBS 2003 domain with MAC clients, some ... You can check the white paper and ensure both the server and the clients ... and client correctly: [note: please notice the ISA section of the bottom of ...
    (microsoft.public.windows.server.sbs)
  • RE: MAC client cannot access web site via ISA 2004
    ... I understand the issue to be: MAC client cannot ... browse the web site on web server which you have published. ... Generally speaking, for the SBS 2003 domain with MAC clients, some ...
    (microsoft.public.windows.server.sbs)
  • Re: Questions about serving database
    ... recommended a PC over a Mac. ... specs for a computer, and if my client environment is almost all mac, ... I've set up my database with a data file, ... Point in Space is perhaps the most well-known server, ...
    (comp.databases.filemaker)
  • Re: MacSrv Event ID 12061 Errors
    ... Connections can be slept on a per connection basis - the Mac client may or ... monitor tool on the server and looking at the time stamps of the traffic ... Mac clients will prefer afp over TCP/IP if the server supports it. ...
    (microsoft.public.win2000.macintosh)