From 93ccfd5df1c7c5e8596a5d742547a0628ba475f3 Mon Sep 17 00:00:00 2001 From: "justdave%syndicomm.com" <> Date: Tue, 19 Mar 2002 13:42:40 +0000 Subject: Getting the stuff Timeless missed with his checkin for bug 106386 --- docs/html/Bugzilla-Guide.html | 4 ++-- docs/html/win32.html | 6 +++--- docs/sgml/installation.sgml | 9 ++++++++- docs/txt/Bugzilla-Guide.txt | 2 +- docs/xml/installation.xml | 9 ++++++++- 5 files changed, 22 insertions(+), 8 deletions(-) diff --git a/docs/html/Bugzilla-Guide.html b/docs/html/Bugzilla-Guide.html index 77f0578ac..769ecce55 100644 --- a/docs/html/Bugzilla-Guide.html +++ b/docs/html/Bugzilla-Guide.html @@ -7416,7 +7416,7 @@ TARGET="_top" >, the perl documentation says that you should always use binmode() when dealing with binary files, but never when dealing with text files. That seems to suggest that rather than aribtrarily putting when dealing with binary files, but never when dealing with text files. That seems to suggest that rather than arbitrarily putting binmode() at the beginning of the attachment files, there should be logic to determine if \ No newline at end of file +> diff --git a/docs/html/win32.html b/docs/html/win32.html index 350b6b881..6db638867 100644 --- a/docs/html/win32.html +++ b/docs/html/win32.html @@ -1246,10 +1246,10 @@ TARGET="_top" >, the perl documentation says that you should always use binmode() when dealing with binary files, but never when dealing with text files. That seems to suggest that rather than aribtrarily putting when dealing with binary files, but never when dealing with text files. That seems to suggest that rather than arbitrarily putting binmode() at the begining of the attachment files, there should be logic to determine if at the beginning of the attachment files, there should be logic to determine if binmode() is needed or not. @@ -1632,4 +1632,4 @@ VALIGN="top" > \ No newline at end of file +> diff --git a/docs/sgml/installation.sgml b/docs/sgml/installation.sgml index 9d14a02be..b50481e9f 100644 --- a/docs/sgml/installation.sgml +++ b/docs/sgml/installation.sgml @@ -1772,7 +1772,14 @@ binmode(STDOUT); According to bug 62000, the perl documentation says that you should always use binmode() when dealing with binary files, but never when dealing with text files. That seems to suggest that rather than aribtrarily putting binmode() at the begining of the attachment files, there should be logic to determine if binmode() is needed or not. + url="http://bugzilla.mozilla.org/show_bug.cgi?id=62000">bug 62000, + the perl documentation says that you should always use + binmode() when dealing with binary + files, but never when dealing with text files. That seems + to suggest that rather than arbitrarily putting + binmode() at the beginning of the + attachment files, there should be logic to determine if + binmode() is needed or not. diff --git a/docs/txt/Bugzilla-Guide.txt b/docs/txt/Bugzilla-Guide.txt index a01651b63..200ec5c23 100644 --- a/docs/txt/Bugzilla-Guide.txt +++ b/docs/txt/Bugzilla-Guide.txt @@ -2171,7 +2171,7 @@ binmode(STDOUT); According to bug 62000, the perl documentation says that you should always use binmode() when dealing with binary files, but never when dealing with text files. That seems to suggest that rather than - aribtrarily putting binmode() at the beginning of the attachment files, + arbitrarily putting binmode() at the beginning of the attachment files, there should be logic to determine if binmode() is needed or not. Tip diff --git a/docs/xml/installation.xml b/docs/xml/installation.xml index 9d14a02be..b50481e9f 100644 --- a/docs/xml/installation.xml +++ b/docs/xml/installation.xml @@ -1772,7 +1772,14 @@ binmode(STDOUT); According to bug 62000, the perl documentation says that you should always use binmode() when dealing with binary files, but never when dealing with text files. That seems to suggest that rather than aribtrarily putting binmode() at the begining of the attachment files, there should be logic to determine if binmode() is needed or not. + url="http://bugzilla.mozilla.org/show_bug.cgi?id=62000">bug 62000, + the perl documentation says that you should always use + binmode() when dealing with binary + files, but never when dealing with text files. That seems + to suggest that rather than arbitrarily putting + binmode() at the beginning of the + attachment files, there should be logic to determine if + binmode() is needed or not. -- cgit v1.2.3-24-g4f1b