TABLE in PRE, why not?

Holger Wahlen (wahlen@ph-cip.Uni-Koeln.DE)
Tue, 23 Sep 1997 18:46:54 +0200

Date: Tue, 23 Sep 1997 18:46:54 +0200
Message-Id: <>
From: wahlen@ph-cip.Uni-Koeln.DE (Holger Wahlen)
Subject: TABLE in PRE, why not?

Would it be a bad idea to have
	(TABLE | (%inline;)*)
instead of just (%inline;)* as the content of PRE? This would
allow authors with not too complicated or too big tables to
have just one page for all kinds of browsers by carefully(!)
adding the necessary number of spaces in the table cells:
table-capable browsers should just render the table normally,
possibly even ignoring the PRE and using proportional fonts
for better results [1], while ones that ignore the table
markup still know how to deal with PRE and therefore display
the content with all spaces and line breaks, delivering a
decent layout.

I'm using this method on one of my pages for an example, so
see yourself what I have in mind:
Looks okay on all browsers I've used to look at it so far; if
there are any problems with other ones, I'd like to know.


[1] Apparently that's the behavior of most current browsers
already - see
for more information.

____  |__|   / Holger   //  ____
      |  |/|/  Wahlen  //