Article View: net.text
Article #113Re: embedded-command text systems [vs WYSIWYG, support for Reid]
From: Bob Felt
Date: Thu, 12 Dec 1985 14:14
Date: Thu, 12 Dec 1985 14:14
63 lines
3903 bytes
3903 bytes
The WSIWYG postings have been the most interesting I
have read in the short time I have read this group.
WSIWYG software combines the document production and
editor functions. There are some good reasons to separate
the editing and formatting functions. WSIWYG features are a
distraction when you are using software to compose text,
edit a document that requires multiple passes, or re-write.
While you are writing, multiple buffers, a wide variety of
commands, good recovery features, and powerful global com-
mands are much more useful than WYSIWYG. Even copy editing
is easier with a powerful editor, as compared to a less
functional editor that also formats. Any editor function
lost in favor of WSIWYG is too much.
In all types of effective writing format follows con-
tent. While it is true that you know that the material you
are writing is narrative text that will be in paragraphs of
some kind, or that you are drafting material that will
result in a technical format, no one writes final drafts.
Paragraphs move, sections move, sentences move, and words
change place. The document divisions, at as low a level as
the paragraph, change as you add or delete text. It is
easier to use an editor that imposes no style until you are
ready to work with style. I know some writers who format
their work one phrase to a line, because it is easier to
play with the sentence structure.
The fact that your software is showing you a styled
paragraph makes second pass work more difficult. For exam-
ple, when you are working with paragraphs you are checking
the relationship of the ideas in the text. You are looking
for a logical transition made by the language, not a line
break and an indent. The importance of the line break and
indent is that this is a visual cue to the reader that you
have completed a presentation. This is why it is a a typo-
graphical convention. This is harder to do when the text
``looks'' finished; the formatting is working against what
it is that you need to do to improve your work.
The document divisions you create when composing often
have more to do with state of your thought about the subject
at a particular time than with a finished structure. Embed-
ded commands may be more difficult to visualize; they are
easier to use as notes, hooks and place markers. It is also
very handy to have references or working notes in the text
where you can use them. Since the commands can be redfined,
you can have as many different hardcopy styles as you need
without even opening the file. The format that is best for
working with the text is not the production format.
Bob Felt
*********************************************************************
I use troff and tplus when making money, I don't make money with either.
--
Bob Felt
East West Journal
{harvard,seismo}!bbnccv!ewj01!bob
Technical Details
Message-ID:
<206@ewj01.UUCP>Path:
arc1-ca.pugleaf.net!utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!think!harvard!bbnccv!ewj01!ljReferences:
<471@harvard.ARPA> <773@mmintl.UUCP> <734@tpvax.fluke.UUCP>Show Full Headers
Complete Article Headers
Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.2 9/18/84; site ewj01.UUCP Path: arc1-ca.pugleaf.net!utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!think!harvard!bbnccv!ewj01!lj From: bob@ewj01.UUCP (Bob Felt) Newsgroups: net.text Subject: Re: embedded-command text systems [vs WYSIWYG, support for Reid] Message-ID: <206@ewj01.UUCP> Date: Thu, 12-Dec-85 09:14:10 EST Article-I.D.: ewj01.206 Posted: Thu Dec 12 09:14:10 1985 Date-Received: Sat, 14-Dec-85 08:03:53 EST References: <471@harvard.ARPA> <773@mmintl.UUCP> <734@tpvax.fluke.UUCP> Distribution: net Organization: East West Journal, Brookline, Mass. Lines: 63