TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:Re: Front Page Fussy From:Scott McClare <smcclare -at- DY4 -dot- COM> Date:Wed, 13 Jan 1999 16:31:13 -0500
> -----Original Message-----
> From: Kris Olberg [SMTP:kjolberg -at- IX -dot- NETCOM -dot- COM]
> Sent: Wednesday, January 13, 1999 3:29 PM
> To: TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU
> Subject: Re: Front Page Fussy
>
> From: Tracy Boyington
> >I'm not sure anyone has said FrontPage creates invalid HTML. What it
> >*does* create is really crappy HTML that gives wildly different results
> >on different browsers, while making the novice user think that what you
> >see really is what you get. Which is just as bad, if not worse.
>
> HTML is a standard. "Crappy" can only describe something that does not
> conform to the standard. Ergo, because FP creates standard HTML, it cannot
> be described as "crappy." Find a different argument.
>
This is the first time I've heard that crappy == noncompliant. If it's
obfuscated, inefficient, or redundant, then it's crappy, no matter how
"legal" it is. Over the course of this thread, I've seen someone say FP
changed his IMG tags to point to absolute files, rather than relative ones;
I've seen someone else say it's turned <b>efficiently bolded text</b> into a
<b>b</b><b>i</b><b>g</b> <b>m</b><b>e</b><b>s</b><b>s</b>. I don't care how
many HTML validators pass this, it's unreadable and obfuscated.
While I've not used FP personally, I've seen other editors - Adobe PageMill
and Netscape Composer - do similar things to my own pages. Usually they
reformat the page or add unnecessary tags or entities, such as closing
</P>'s, superfluous 's, and "'s in the body text (where plain old
"" will suffice). Just today Composer re-HTMLized an entire page into a
hardly-editable mess, just because I wanted to correct a single spelling
error. No wonder people are recommending Notepad.