summaryrefslogtreecommitdiff
path: root/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-notWYSIWYG.html
diff options
context:
space:
mode:
authorKarl Berry <karl@freefriends.org>2010-04-07 22:47:28 +0000
committerKarl Berry <karl@freefriends.org>2010-04-07 22:47:28 +0000
commit3f1971c9b7717818766692c9aa497e20e7472f2c (patch)
tree678de0190b6643b1b21fd9441fa1387bce180726 /Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-notWYSIWYG.html
parentc7c3b090320a234149dbe23315e2a15a2773ac79 (diff)
FAQ-en 3.19d (7apr10)
git-svn-id: svn://tug.org/texlive/trunk@17742 c570f23f-e606-0410-a88d-b1316a301751
Diffstat (limited to 'Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-notWYSIWYG.html')
-rw-r--r--Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-notWYSIWYG.html34
1 files changed, 17 insertions, 17 deletions
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-notWYSIWYG.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-notWYSIWYG.html
index 09247c59096..13b331a0481 100644
--- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-notWYSIWYG.html
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-notWYSIWYG.html
@@ -2,54 +2,54 @@
<title>UK TeX FAQ -- question label notWYSIWYG</title>
</head><body>
<h3>Why is TeX not a WYSIWYG system?</h3>
-<p/>WYSIWYG is a marketing term (&ldquo;What you see is what you get&rdquo;) for
+<p/>WYSIWYG is a marketing term (&#8220;What you see is what you get&#8221;) for
a particular style of text processor. WYSIWYG systems are
characterised by two principal claims: that you type what you want to
print, and that what you see on the screen as you type is a close
approximation to how your text will finally be printed.
<p/>The simple answer to the question is, of course, that TeX was
conceived long before the marketing term, at a time when the marketing
-imperative wasn&rsquo;t perceived as significant. However, that was a long
-time ago: why has nothing been done with the &ldquo;wonder text processor&rdquo;
+imperative wasn&#8217;t perceived as significant. However, that was a long
+time ago: why has nothing been done with the &#8220;wonder text processor&#8221;
to make it fit with modern perceptions?
-<p/>There are two answers to this. First, the simple &ldquo;things <em>have</em>
-been done&rdquo; (but they&rsquo;ve not taken over the TeX world); and second,
-&ldquo;there are philosophical reasons why the way TeX has developed is
-ill-suited to the WYSIWYG style&rdquo;.
+<p/>There are two answers to this. First, the simple &#8220;things <em>have</em>
+been done&#8221; (but they&#8217;ve not taken over the TeX world); and second,
+&#8220;there are philosophical reasons why the way TeX has developed is
+ill-suited to the WYSIWYG style&#8221;.
Indeed, there is a fundamental problem with applying WYSIWYG techniques
to TeX: the complexity of TeX makes it hard to get the
-equivalent of TeX&rsquo;s output without actually running TeX.
-<p/>A celebrated early system offering &ldquo;WYSIWYG using TeX&rdquo; came from the
+equivalent of TeX&#8217;s output without actually running TeX.
+<p/>A celebrated early system offering &#8220;WYSIWYG using TeX&#8221; came from the
VorTeX project: a pair of (early) Sun workstations worked in
tandem, one handling the user interface while the other beavered away
in the background typesetting the result. VorTeX was quite
impressive for its time, but the two workstations combined had hugely less
power than the average sub-thousand dollar Personal Computer
nowadays, and its code has not proved portable (it never even made the
-last &lsquo;great&rsquo; TeX version change, at the turn of the 1990s, to
+last &#8216;great&#8217; TeX version change, at the turn of the 1990s, to
TeX version 3). Modern systems that are similar in
their approach are Lightning Textures (an extension of
-Blue Sky&rsquo;s original TeX system for the Macintosh), and Scientific
+Blue Sky&#8217;s original TeX system for the Macintosh), and Scientific
Word (which can also cooperate with a computer algebra system); both
these systems are <a href="FAQ-commercial.html">commercially available</a>.
<p/>The issue has of recent years started to attract attention from TeX
developers, and several interesting projects addressing the
-&ldquo;<a href="FAQ-WYGexpts.html">TeX document preparation environment</a>&rdquo;
+&#8220;<a href="FAQ-WYGexpts.html">TeX document preparation environment</a>&#8221;
are in progress.
<p/>Nevertheless, the TeX world has taken a long time to latch onto the
idea of WYSIWYG.
-Apart from simple arrogance (&ldquo;we&rsquo;re better, and have no need to
-consider the petty doings of the commercial word processor market&rdquo;),
+Apart from simple arrogance (&#8220;we&#8217;re better, and have no need to
+consider the petty doings of the commercial word processor market&#8221;),
there is a real conceptual difference between the word processor model
-of the world and the model LaTeX and ConTeXt employ &mdash; the idea of
-&ldquo;markup&rdquo;. &ldquo;Pure&rdquo; markup expresses a logical model of a document,
+of the world and the model LaTeX and ConTeXt employ &#8212; the idea of
+&#8220;markup&#8221;. &#8220;Pure&#8221; markup expresses a logical model of a document,
where every object within the document is labelled according to what
it is rather than how it should appear: appearance is deduced from the
properties of the type of object. Properly applied, markup can
provide valuable assistance when it comes to re-use of documents.
<p/>Established WYSIWYG systems find the expression of this sort of
structured markup difficult; however, markup <em>is</em> starting to
-appear in the lists of the commercial world&rsquo;s requirements, for two
+appear in the lists of the commercial world&#8217;s requirements, for two
reasons. First, an element of markup helps impose style on a
document, and commercial users are increasingly obsessed with
uniformity of style; and second, the increasingly pervasive use of