JargonFile/original/html/W/WYSIAYG.html
2014-03-27 18:54:56 +00:00

19 lines
2.9 KiB
HTML
Raw Blame History

This file contains invisible Unicode characters

This file contains invisible Unicode characters that are indistinguishable to humans but may be processed differently by a computer. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

<?xml version="1.0" encoding="ISO-8859-1" standalone="no"?>
<html xmlns="http://www.w3.org/1999/xhtml"><head><title>WYSIAYG</title><link rel="stylesheet" href="../../jargon.css" type="text/css"/><meta name="generator" content="DocBook XSL Stylesheets V1.61.0"/><link rel="home" href="../index.html" title="The Jargon File"/><link rel="up" href="../W.html" title="W"/><link rel="previous" href="wumpus.html" title="wumpus"/><link rel="next" href="WYSIWYG.html" title="WYSIWYG"/></head><body><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">WYSIAYG</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="wumpus.html">Prev</a> </td><th width="60%" align="center">W</th><td width="20%" align="right"> <a accesskey="n" href="WYSIWYG.html">Next</a></td></tr></table><hr/></div><dt><a id="WYSIAYG"/><dt xmlns="" id="WYSIAYG"><b>WYSIAYG</b>: <span xmlns="http://www.w3.org/1999/xhtml" class="pronunciation">/wiz´ee·ayg/</span>, <span xmlns="http://www.w3.org/1999/xhtml" class="grammar">adj.</span></dt></dt><dd><p> Describes a user interface under which &#8220;<span class="quote">What You See Is
<span class="emphasis"><em>All</em></span> You Get</span>&#8221;; an unhappy variant of
<a href="WYSIWYG.html"><i class="glossterm">WYSIWYG</i></a>. Visual,
&#8216;point-and-shoot&#8217;-style interfaces tend to have easy initial
learning curves, but also to lack depth; they often frustrate advanced
users who would be better served by a command-style interface. When this
happens, the frustrated user has a WYSIAYG problem. This term is most
often used of editors, word processors, and document formatting programs.
WYSIWYG &#8216;desktop publishing&#8217; programs, for example, are a clear
win for creating small documents with lots of fonts and graphics in them,
especially things like newsletters and presentation slides. When
typesetting book-length manuscripts, on the other hand, scale changes the
nature of the task; one quickly runs into WYSIAYG limitations, and the
increased power and flexibility of a command-driven formatter like
<a href="../T/TeX.html"><i class="glossterm">TeX</i></a> or Unix's <a href="../T/troff.html"><i class="glossterm">troff</i></a> becomes
not just desirable but a necessity. Compare
<a href="../Y/YAFIYGI.html"><i class="glossterm">YAFIYGI</i></a>.</p></dd><div class="navfooter"><hr/><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="wumpus.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="../W.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="WYSIWYG.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">wumpus </td><td width="20%" align="center"><a accesskey="h" href="../index.html">Home</a></td><td width="40%" align="right" valign="top"> WYSIWYG</td></tr></table></div></body></html>