[GoLUG] Hideous HTML

Steve Litt slitt at troubleshooters.com
Mon Jan 13 16:26:33 EST 2025


David Billsbrough said on Mon, 13 Jan 2025 16:57:36 +0000

>Steve and all,
>
>> There's a simple explanation for this abysmal quality: Back in 2009 I
>> was still using those insane WYSIWYG HTML authoring tools.  
>
> or WYSIWYSRL
>
>What-you-see-is-what-you'll-seriously-regret-later!
>
> :-(
>
><in_a_purple-haze>
>  --  Let's program like it's 1999 all over again!
></in_a_purple-haze>
>
>Looking at the HTML4 stuff ... just strip out the content and start
>with a fresh HTML5 template.

Nope, I'm trying to convert it. The more familiar I become with the
stupid pidgin html output by the stupid wysiwysrl, the more I can use
Vim to do a lot of the repetitive work or at least break up million
word lines in an intelligent way.

Never have I been so grateful for HTML5 and CSS.

That wysiwyg thing outputs HTML confusing both to the browser and the
human. The sad thing is that I'd still be using wysiwyg today if it
weren't for the fact that at some point both wysiwyg programs broke, so
I regretfully turned to zen-coding, HTML syntax aware Bluefish, and
learned how to do HTML right. Then, when HTML5 came along, everything
became crystal clear.

If I haven't fixed the page within 2 days, yeah, I'll reconstruct it by
screen scraping its output. I think I'll need to do screen scraping for
the <pre>s anyway: They're absolutely inscrutable as output by the
wysiaspos.

SteveT

Steve Litt 

http://444domains.com



More information about the GoLUG mailing list