summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorjustdave%syndicomm.com <>2002-03-19 14:42:40 +0100
committerjustdave%syndicomm.com <>2002-03-19 14:42:40 +0100
commit93ccfd5df1c7c5e8596a5d742547a0628ba475f3 (patch)
treebb3734b5e7470d5351fc0ca138f9947a0f5f5eaa
parent4accb1955e7d530a322dc64d63807c52bf11c968 (diff)
downloadbugzilla-93ccfd5df1c7c5e8596a5d742547a0628ba475f3.tar.gz
bugzilla-93ccfd5df1c7c5e8596a5d742547a0628ba475f3.tar.xz
Getting the stuff Timeless missed with his checkin for bug 106386
-rw-r--r--docs/html/Bugzilla-Guide.html4
-rw-r--r--docs/html/win32.html6
-rw-r--r--docs/sgml/installation.sgml9
-rw-r--r--docs/txt/Bugzilla-Guide.txt2
-rw-r--r--docs/xml/installation.xml9
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 <TT
CLASS="function"
>binmode()</TT
-> when dealing with binary files, but never when dealing with text files. That seems to suggest that rather than aribtrarily putting <TT
+> when dealing with binary files, but never when dealing with text files. That seems to suggest that rather than arbitrarily putting <TT
CLASS="function"
>binmode()</TT
> at the beginning of the attachment files, there should be logic to determine if <TT
@@ -17725,4 +17725,4 @@ NAME="zarro-boogs-found"
></DIV
></BODY
></HTML
-> \ 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 <TT
CLASS="function"
>binmode()</TT
-> when dealing with binary files, but never when dealing with text files. That seems to suggest that rather than aribtrarily putting <TT
+> when dealing with binary files, but never when dealing with text files. That seems to suggest that rather than arbitrarily putting <TT
CLASS="function"
>binmode()</TT
-> at the begining of the attachment files, there should be logic to determine if <TT
+> at the beginning of the attachment files, there should be logic to determine if <TT
CLASS="function"
>binmode()</TT
> is needed or not.
@@ -1632,4 +1632,4 @@ VALIGN="top"
></DIV
></BODY
></HTML
-> \ 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);
<note>
<para>
According to <ulink
- url="http://bugzilla.mozilla.org/show_bug.cgi?id=62000">bug 62000</ulink>, the perl documentation says that you should always use <function>binmode()</function> when dealing with binary files, but never when dealing with text files. That seems to suggest that rather than aribtrarily putting <function>binmode()</function> at the begining of the attachment files, there should be logic to determine if <function>binmode()</function> is needed or not.
+ url="http://bugzilla.mozilla.org/show_bug.cgi?id=62000">bug 62000</ulink>,
+ the perl documentation says that you should always use
+ <function>binmode()</function> when dealing with binary
+ files, but never when dealing with text files. That seems
+ to suggest that rather than arbitrarily putting
+ <function>binmode()</function> at the beginning of the
+ attachment files, there should be logic to determine if
+ <function>binmode()</function> is needed or not.
</para>
</note>
</step>
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);
<note>
<para>
According to <ulink
- url="http://bugzilla.mozilla.org/show_bug.cgi?id=62000">bug 62000</ulink>, the perl documentation says that you should always use <function>binmode()</function> when dealing with binary files, but never when dealing with text files. That seems to suggest that rather than aribtrarily putting <function>binmode()</function> at the begining of the attachment files, there should be logic to determine if <function>binmode()</function> is needed or not.
+ url="http://bugzilla.mozilla.org/show_bug.cgi?id=62000">bug 62000</ulink>,
+ the perl documentation says that you should always use
+ <function>binmode()</function> when dealing with binary
+ files, but never when dealing with text files. That seems
+ to suggest that rather than arbitrarily putting
+ <function>binmode()</function> at the beginning of the
+ attachment files, there should be logic to determine if
+ <function>binmode()</function> is needed or not.
</para>
</note>
</step>