WYSIWYG

The program on the left uses a WYSIWYG editor to produce a Lorem Ipsum document. The program on the right contains LaTeX code, which when compiled will produce a document that will look very similar to the document on the left. Compilation of formatting code is not a WYSIWYG process.

WYSIWYG implies a user interface that allows the user to view something very similar to the end result—while the document is being created.[3] In general, WYSIWYG implies the ability to directly manipulate the layout of a document without having to type or remember names of layout commands.[4] The actual meaning depends on the user's perspective, e.g.:

• In presentation programs, compound documents, and web pages, WYSIWYG means the display precisely represents the appearance of the page displayed to the end-user, but does not necessarily reflect how the page will be printed unless the printer is specifically matched to the editing program, as it was with the Xerox Star and early versions of the Apple Macintosh.
• In word processing and desktop publishing applications, WYSIWYG means that the display simulates the appearance and represents the effect of fonts and line breaks on the final pagination using a specific printer configuration, so that, for example, a citation on page 1 of a 500-page document can accurately refer to a reference three hundred pages later.[5]
• WYSIWYG also describes ways to manipulate 3D models in stereo-chemistry, computer-aided design, and 3D computer graphics.

Modern software does a good job of optimizing the screen display for a particular type of output. For example, a word processor is optimized for output to a typical printer. The software often emulates the resolution of the printer in order to get as close as possible to WYSIWYG. However, that is not the main attraction of WYSIWYG, which is the ability of the user to be able to visualize what they are producing.

In many situations, the subtle differences between what the user sees and what the user gets are unimportant. In fact, applications may offer multiple WYSIWYG modes with different levels of "realism", including

• A composition mode, in which the user sees something somewhat similar to the end result, but which employs an interface more conducive to composing than the layout itself (e.g., inclusion of section breaks and non-printing characters).
• A layout mode, in which the user sees something very similar to the end result, but which includes some additional information to facilitate proper alignment and spacing (e.g., margin lines).
• A preview mode, in which the application attempts to produce an output that is as close to the final result as possible.

Compound document displayed on Xerox 8010 Star system

Before the adoption of WYSIWYG techniques, text appeared in editors using the system standard typeface and style with little indication of layout (margins, spacing, etc.). Users were required to enter special non-printing control codes (now referred to as markup code tags) to indicate that some text should be in boldface, italics, or a different typeface or size. In this environment there was very little distinction between text editors and word processors.

These applications typically used an arbitrary markup language to define the codes/tags. Each program had its own special way to format a document, and it was a difficult and time-consuming process to change from one word processor to another.

The use of markup tags and codes remains popular today in some applications due to their ability to store complex formatting information. When the tags are made visible in the editor, however, they occupy space in the unformatted text, and as a result can disrupt the desired layout and flow.

Bravo, a document preparation program for the Alto produced at Xerox PARC by Butler Lampson, Charles Simonyi and colleagues in 1974, is generally considered to be the first program to incorporate the WYSIWYG technology,[6] displaying text with formatting (e.g. with justification, fonts, and proportional spacing of characters).[7] The Alto monitor (72 PPI, based on the typographic unit) was designed so that one full page of text could be seen and then printed on the first laser printers. When the text was laid out on the screen, 72 PPI font metric files were used, but when printed, 300 PPI files were used. As a result, one would occasionally find characters and words that are slightly off—a problem that would continue up to this day.

Bravo was released commercially, and the software eventually included in the Xerox Star can be seen as a direct descendant of it.[8]

In late 1978, in parallel with but independent of the work at Xerox PARC, Hewlett Packard developed and released the first commercial WYSIWYG software application for producing overhead slides (or what today are referred to as presentation graphics). The first release, named BRUNO (after an HP sales training puppet), ran on the HP 1000 minicomputer, taking advantage of HP 2640—HP's first bitmapped computer terminal. BRUNO was then ported to the HP-3000 and re-released as "HP Draw".[9]

By 1981, MicroPro advertised that its WordStar word processor had WYSIWYG,[10] but its display was limited to displaying styled text in WYSIWYG fashion; bold and italic text would be represented on screen, instead of being surrounded by tags or special control characters.[11] In 1983, the Weekly Reader advertised its Stickybear educational software with the slogan "what you see is what you get", with photographs of its Apple II graphics,[12] but home computers of the 1970s and early 1980s lacked the sophisticated graphics capabilities necessary to display WYSIWYG documents, meaning that such applications were usually confined to limited-purpose, high-end workstations (such as the IBM Displaywriter System) that were too expensive for the general public to afford. Towards the mid-1980s, however, things began to change. as improving technology allowed the production of cheaper bitmapped displays, and WYSIWYG software started to appear in more popular computers, including LisaWrite for the Apple Lisa, released in 1983, and MacWrite for the Apple Macintosh, released in 1984.[13]

The Apple Macintosh system was originally designed so that the screen resolution and the resolution of the ImageWriter dot-matrix printers sold by Apple were easily scaled: 72 PPI for the screen and 144 DPI for the printers. Thus, the scale and dimensions of the on-screen display in programs such as MacWrite and MacPaint were easily translated to the printed output. If the paper were held up to the screen, the printed image would be the same size as the on-screen image, but at twice the resolution. As the ImageWriter was the only model of printer physically compatible with the Macintosh printer port, this created an effective closed system. Later, when Macs-using external displays became available, the resolution was fixed to the size of the screen to achieve 72 DPI. These resolutions often differed from the VGA-standard resolutions common in the PC world at the time. Thus, while a Macintosh 15-inch (38 cm) monitor had the same 640 × 480 resolution as a PC, a 16-inch (41 cm) screen would be fixed at 832 × 624 rather than the 800 × 600 resolution used by PCs. With the introduction of third-party dot-matrix printers as well as laser printers and multisync monitors, resolutions deviated from even multiples of the screen resolution, making true WYSIWYG harder to achieve.

In 2012, Wikipedia offered a WYSIWYG editor called VisualEditor, which allowed edits of Wikipedia to be performed without seeing the page source.[14]

Because designers of WYSIWYG applications typically have to account for a variety of different output devices, each of which has different capabilities, there are a number of problems that must be solved in each implementation. These can be seen as tradeoffs between multiple design goals, hence applications that use different solutions may be suitable for different purposes.

Typically, the design goals of a WYSIWYG application may include the following:

• Provide high-quality printed output on a particular printer
• Provide high-quality printed output on a variety of printers
• Provide high-quality on-screen output
• Allow the user to visualize what the document will look like when printed
• Allow the user to visualize what the website will look like when published

However, it is usually not possible to achieve all of these goals at once, and the major problem to overcome is that of the varying output resolutions. As of 2016, monitors typically have a resolution of between 102 and 125 pixels per inch, while printers generally have resolutions between 240 and 1440 pixels per inch. In some printers, the horizontal resolution is different from the vertical. This becomes a problem when trying to lay out text; because older output technologies require the spacing between characters to be a whole number of pixels (as rounding errors will cause the same text to require different amounts of space in different resolutions).

Solutions to this include the following:

• Always laying out the text using a resolution higher than the user is likely to use in practice. This can result in poor quality output for lower resolution devices (although techniques such as spatial anti-aliasing may help mitigate this), but provides a fixed layout, allowing easy user visualisation. This is the method used by Adobe Acrobat.
• Laying out the text at the resolution of the printer on which the document will be printed. This can result in low quality on-screen output, and the layout may sometimes change if the document is printed on a different printer (although this problem occurs less frequently with higher resolution printers, as rounding errors are smaller). This is the method used by Microsoft Word.
• Laying out the text at the resolution of a specific printer (in most cases the default one) on which the document will be printed using the same font information and kerning. The character positions and number of characters in a line are exactly similar to the printed document.
• Laying out the text at the resolution for the output device to which it will be sent. This often results in changes in layout between the on-screen display and printed output, so is rarely used (though it could be common in web page designing tools claiming to be WYSIWYG).

Other problems that have been faced in the past include differences in the fonts used by the printer and the on-screen display (largely solved by the use of downloadable font technologies like TrueType), and differences in color profiles between devices (mostly solved by printer drivers with good color model conversion software).

Apart from these issues, the practice of WYSIWYG has also been argued to being more conducive to a distracted writing process, as the WYSIWYG philosophy assumes no separation between composition and formatting, which opens up the possibility of repeatedly tweaking the layout of the document—as one prepares its content in real-time.[20][21]

Many variations are used only to illustrate a point or make a joke, and have very limited real use. Some that have been proposed include the following:

• WISIWIT, what I see is what I type, also used to describe text-oriented editing systems in the opposite sense of WYSIWYG.
• WYCIWYG, what you cache is what you get.
• WYGIWYG; what you get is what you get, often used in a similar way to WYSIAYG, WYSIMOLWYG, or WYSINWYW.[22]
• WYGIWYS, what you get is what you see, used in computing to describe an interaction paradigm in results-oriented user interface. The term was used by Jakob Nielsen to describe Microsoft Office 2007's "Ribbon" interface[23]
• WYSIAWYG; what you see is almost what you get, similar to WYSIMOLWYG.[4]
• WYSIAYG, what you see is all you get, used to point out that advanced users are sometimes limited by the user interface.[24]
• WYSIMOLWYG, what you see is more or less what you get, recognizing that most WYSIWYG implementations are imperfect.[4]
• WYSINWYW, what you see is not what you want, suggesting that Microsoft Word often controls the user, not the other way around[25]
• WYSIPWYG, what you see is probably what you get, relates to html and markup editors where code and macro tags sort of show what the result will eventually be. This type of WYSIWYG view is hard to render while editing so the user can only guess at the outcome.
• WYSIWYD, what you see is what you deserve refers to the ability of the user and their effort to create something worthwhile.
• WYSIWYM, what you see is what you mean, saying that the user sees what best conveys the message and the structure of it—rather than its actual formatting.
• WYGIWYM, what you get is what you mean, saying that the user gets (visually, aurally or by any other means) what best conveys the message.
• WYSIWYN, what you see is what you need relates to Software, which is not composed through the interconnection of modules, but work with such a detailed user and rights management, that users can see only what they really need.
• WYSIWYS, what you see is what you sign, an important requirement for digital signature software. It means that the software has to be able to show the user the content without any hidden content before the user signs it.
• WYSIWYW, what you see is what you want, used to describe GNU TeXmacs editing platform.[26] The abbreviation clarifies that unlike in WYSIWYG editors, the user is able to customize WYSIWYW platforms to act (possibly in part) as manual typesetting programs such as TeX or troff.
• WYSYHYG, what you see you hope you get (/ˈwɪzihɪɡ/), a term ridiculing text mode word processing software; used in the Microsoft Windows video collection, a video distributed around 1991 on two VHS cassettes at promotional events.
• YAFIYGI, you asked for it you got it, used to describe a text-command oriented document editing system that does not include WYSIWYG, in reference to the fact that users of such systems often ask for something they did not really want. It is considered to be the opposite of WYSIWYG.[27] The phrase was first used in this context in 1983 in the essay Real Programmers Don't Use Pascal to describe the TECO text editor system, and began to be abbreviated circa 1993.[28][29][30]

• Comparison of HTML editors
• Does exactly what it says on the tin
• DWIM
• Formatted text
• Plain text
• Tableless web design
• List of HTML editors

Look up WYSIWYG or what you see is what you get in Wiktionary, the free dictionary.

• The Jargon File entry for WYSIWYG
• What has WYSIWYG done to us? – Critical paper about the negative effects the introduction of WYSIWYG has had as of 1996.
• XML: WYSIWYG to WYSIWYM – A brief look at XML document authoring An article on existing XML authoring software (May 2005)
• ATPM.com's WYSIWYG: Is it What You Want?