Re:Re: Re: Optimizing cutting paths - The proof

>Message: 25
> Date: Sun, 2 Sep 2001 00:25:46 +0100
> From: Peter Harrison <egroups@...>
>Subject: Re: Re: Optimizing cutting paths - The proof
>

>
>Oh please...
>
>Just about all the original Internet protocols are based around text
>transfers. So reliable is the transfer of text (as long as it is seven
>bit ASCII) that email attachments are converted to text for
>transmission. If there is a problem, it is potentially in the
>transmission of eight bit ASCII and binary files that are treated as
>eight bit ASCII.

Oh please, Mr. Experience tell me why you forgot to mention the 90% reduction in bandwidth?

Of course who cares if an attached joke list gets a few corrupted characters, it's just Text, or even a few JPG's of Gif's, just some speckles in the picture. How about if it is a file for the Concorde or the Space Shuttle, or any other "life" situation? I receive between 5-10 dxf files a day , and have received several hundred very large IGES files over the last few years. I know what causes and prevents corrupted files. It has been especially bad with files received from Germany for some reason. Partially because of the volume and I suspect because of other "communications" reasons. Never have any problems with zips. period.

My instructions were not to save twice. They were to save without displaying in the browser. A DXF file, being text, will open up in a browser window, saving this displayed file will change the formatting of the DXF file (to a bastardized form of HTML) and in some cases make it useless. Removing the extra garbage lines added by the browser, when it saves the text file, fixes the problem.

Best Regards, Fred Smith- IMService
Listserve Special discounts and offers are at: http://209.69.202.197/cced.html

imserv@... Voice:248-486-3600 or 800-386-1670 Fax: 248-486-3698