From: Peter Ring <PRI@cddk.dk>
To: 'Cygwin' <cygwin@sourceware.cygnus.com>
Subject: RE: ÆANNÅ Cygwin DEV survey
Date: Tue, 09 Mar 1999 07:58:00 -0000 [thread overview]
Message-ID: <c=DK%a=_%p=CD-Danmark%l=CDDKSERVER-990309155825Z-3420@cddkserver.cddk.dk> (raw)
Re text/binary:
NOTEPAD is not a text editor. It is a bug. NOTEPAD compatibility
is not a valid concern. Seriously!
Why hang on to ancient conventions such as the distinction between
binary and text mode?
It is useless anyway. It _used_ to be like that if a file was 'text',
it was ASCII (aka ISO 646) text, and could be transmitted safely through
7-bit channels.
That was long ago. Most of my 'text' files use 8-bit or 16-bit character
sets, and you have to know beforehand, 'cause the file itself doesn't
say
what character set is used. I don't want any automatic conversion of any
characters, and I most certainly don't want truncation at first ^Z.
Why should I want to open a file in 'text' mode? What if I run a cygwin
application to write a 'text' file that is part of a MacOS application?
I need three different record separators, and I can't infer which to use
just from what OS the application is running on. BTW, this is an actual
example of what I use cygwin tools for.
Kind regards
Peter Ring.
-----Original Message-----
From: Earnie Boyd [ mailto:earnie_boyd@yahoo.com ]
Sent: Monday, March 08, 1999 14:49
To: Smith, Martin; Cygwin
Cc: 'tolj@uni-duesseldorf.de'
Subject: RE: ÆANNÅ Cygwin DEV survey
---"Smith, Martin" <martin@exchange.Scotland.NCR.COM> wrote:
8<
> * What about text/binary mounts - I get the feeling binary mounts are
> preferred for most applications but, by default, the Cygnus tools
install
> with text mounts. Is it wise to change this to binary for a
'development'
> install or not?
8<
NO! The preferred method is text mounts. That is the reason for the
default. If a program requires binary mounts then the program isn't
properly ported. Switching to binary mounts causes other problems.
In a program always _SPECIFY_ whether it is to be opened for text mode
processing or binary mode processing, don't rely on the default. A
file should be opened for text mode processing if the file can
potentially be read or created by humans with a text mode editor, such
as NOTEPAD. All other files should be opened for binary mode
processing.
<snip>
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
WARNING: multiple messages have this Message-ID
From: Peter Ring <PRI@cddk.dk>
To: 'Cygwin' <cygwin@sourceware.cygnus.com>
Subject: RE: ÆANNÅ Cygwin DEV survey
Date: Wed, 31 Mar 1999 19:45:00 -0000 [thread overview]
Message-ID: <c=DK%a=_%p=CD-Danmark%l=CDDKSERVER-990309155825Z-3420@cddkserver.cddk.dk> (raw)
Message-ID: <19990331194500.GFDt8aCFIU6Xc8C2-c0FHr5N5NdGyF-EmQmp_DBr38k@z> (raw)
Re text/binary:
NOTEPAD is not a text editor. It is a bug. NOTEPAD compatibility
is not a valid concern. Seriously!
Why hang on to ancient conventions such as the distinction between
binary and text mode?
It is useless anyway. It _used_ to be like that if a file was 'text',
it was ASCII (aka ISO 646) text, and could be transmitted safely through
7-bit channels.
That was long ago. Most of my 'text' files use 8-bit or 16-bit character
sets, and you have to know beforehand, 'cause the file itself doesn't
say
what character set is used. I don't want any automatic conversion of any
characters, and I most certainly don't want truncation at first ^Z.
Why should I want to open a file in 'text' mode? What if I run a cygwin
application to write a 'text' file that is part of a MacOS application?
I need three different record separators, and I can't infer which to use
just from what OS the application is running on. BTW, this is an actual
example of what I use cygwin tools for.
Kind regards
Peter Ring.
-----Original Message-----
From: Earnie Boyd [ mailto:earnie_boyd@yahoo.com ]
Sent: Monday, March 08, 1999 14:49
To: Smith, Martin; Cygwin
Cc: 'tolj@uni-duesseldorf.de'
Subject: RE: ÆANNÅ Cygwin DEV survey
---"Smith, Martin" <martin@exchange.Scotland.NCR.COM> wrote:
8<
> * What about text/binary mounts - I get the feeling binary mounts are
> preferred for most applications but, by default, the Cygnus tools
install
> with text mounts. Is it wise to change this to binary for a
'development'
> install or not?
8<
NO! The preferred method is text mounts. That is the reason for the
default. If a program requires binary mounts then the program isn't
properly ported. Switching to binary mounts causes other problems.
In a program always _SPECIFY_ whether it is to be opened for text mode
processing or binary mode processing, don't rely on the default. A
file should be opened for text mode processing if the file can
potentially be read or created by humans with a text mode editor, such
as NOTEPAD. All other files should be opened for binary mode
processing.
<snip>
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next reply other threads:[~1999-03-09 7:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-09 7:58 Peter Ring [this message]
1999-03-09 10:02 ` _FANNE_Cygwin_DEV_survey Dr. Volker Zell
[not found] ` < 4798-Tue09Mar1999190417+0100-vzell@de.oracle.com >
1999-03-09 16:13 ` text vs binary mode yet again Fergus Henderson
1999-03-31 19:45 ` Fergus Henderson
1999-03-31 19:45 ` _FANNE_Cygwin_DEV_survey Dr. Volker Zell
1999-03-31 19:45 ` ÆANNà Cygwin DEV survey Peter Ring
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='c=DK%a=_%p=CD-Danmark%l=CDDKSERVER-990309155825Z-3420@cddkserver.cddk.dk' \
--to=pri@cddk.dk \
--cc=cygwin@sourceware.cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).