Message-Id: <199907292028.PAA12782@darwin.sfbr.org>
Date: Thu, 29 Jul 1999 15:28:44 -0500 (CDT)
From: Jeff Williams <jeffw AT darwin DOT sfbr DOT org>
Subject: Re: about dtou and utod
To: djgpp AT delorie DOT com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: XBvf05EG8Igr7sM9Mh7pwA==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.3.4 SunOS 5.7 sun4u sparc 
Reply-To: djgpp AT delorie DOT com

-: > [4] The main reason any of this matters to me is because I move lots of
-: > files back and forth from work (Solaris 2.7) to home (djgpp).  I was
-: 
-: I use a C program or perl script to detect non-ascii characters (like
-: NUL or 0x80-0x9f) to select text vs binary files (html vs gif for
-: example).


...and then run the text files only through `dtou'?

I was thinking to detect whether a given text file (e.g., c source,
makefile, TeX source, etc). has already been run through `dtou' before
it gets added to the tarball.  If not, apply `dtou' before adding it to
the archive.  In other words, I want to be sure that every text file in
the tarball has been `dtou'ed, so I can avoid the need for `dos2unix'
after unpacking everything on a true Unix box.

It doesn't matter with files transported from office (Solaris) to home
(djgpp), because djgpp is so good about working with either format.