summaryrefslogtreecommitdiff
path: root/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-buffovl.html
diff options
context:
space:
mode:
Diffstat (limited to 'Master/texmf-doc/doc/english/FAQ-en/html/FAQ-buffovl.html')
-rw-r--r--Master/texmf-doc/doc/english/FAQ-en/html/FAQ-buffovl.html20
1 files changed, 10 insertions, 10 deletions
diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-buffovl.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-buffovl.html
index 4fbfbd20aa9..5dbf6e85c97 100644
--- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-buffovl.html
+++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-buffovl.html
@@ -3,29 +3,29 @@
</head><body>
<h3>Unable to read an entire line</h3>
<p>TeX belongs to the generation of applications written for
-environments that didn't offer the sophisticated string and i/o
+environments that didn&rsquo;t offer the sophisticated string and i/o
manipulation we nowadays take for granted (TeX was written in
Pascal, and the original Pascal standard made no mention of i/o, so
that anything but the most trivial operations were likely to be
unportable).
-<p>When you overwhelm TeX's input mechanism, you get told:
+<p>When you overwhelm TeX&rsquo;s input mechanism, you get told:
<pre>
! Unable to read an entire line---bufsize=3000.
Please ask a wizard to enlarge me.
</pre>
-(for some value of '3000' - the quote was from a
+(for some value of &lsquo;3000&rsquo; &mdash; the quote was from a
<i>comp.text.tex</i> posting by a someone who was presumably
using an old TeX).
-<p>As the message implies, there's (what TeX thinks of as a) line in
-your input that's "too long" (to TeX's way of thinking). Since
+<p>As the message implies, there&rsquo;s (what TeX thinks of as a) line in
+your input that&rsquo;s &ldquo;too long&rdquo; (to TeX&rsquo;s way of thinking). Since
modern distributions tend to have tens of thousands of bytes of input
-buffer, it's somewhat rare that these messages occur "for real".
+buffer, it&rsquo;s somewhat rare that these messages occur &ldquo;for real&rdquo;.
Probable culprits are:
<ul>
<li> A file transferred from another system, without translating
record endings. With the decline of fixed-format records (on
mainframe operating systems) and the increased intelligence of
- TeX distributions at recognising other systems' explicit
+ TeX distributions at recognising other systems&rsquo; explicit
record-ending characters, this is nowadays rather a rare cause of
the problem.
<li> A graphics input file, which a package is examining for its
@@ -38,11 +38,11 @@ Probable culprits are:
enlarging), and to put the problem right in the source.
<p>If the real problem is over-long text lines, most self-respecting text
editors will be pleased to automatically split long lines (while
-preserving the "word" structure) so that they are nowhere any longer
+preserving the &ldquo;word&rdquo; structure) so that they are nowhere any longer
than a given length; so the solution is just to edit the file.
<p>If the problem is a ridiculous preview section, try using
-<i>ghostscript</i> to reprocess the file, outputting a "plain
-<code>.eps</code>" file. (<i>Ghostscript</i> is distributed with a script
+<i>ghostscript</i> to reprocess the file, outputting a &ldquo;plain
+<code>.eps</code>&rdquo; file. (<i>Ghostscript</i> is distributed with a script
<i>ps2epsi</i> which will regenerate the preview if necessary.)
Users of the shareware program <i>GSview</i> will find buttons to
perform the required transformation of the file being displayed.