From: "Federico G. Benavento" <benavento@gmail.com>
To: trickey@lucent.com, 9fans@cse.psu.edu
Subject: RE: [9fans] libhtml vs. <pre> tags
Date: Fri, 21 Oct 2005 11:02:21 -0300 [thread overview]
Message-ID: <b67622ebbe0880588f48f8cd980145a9@yourdomain.dom> (raw)
>> ...I knew that this was easy to fix, but I didn't
>> because, right now, <table> is my problem.
>And I predict <table> will remain your problem for quite some time.
yep
>I wrote charon and did the abortive attempt to convert it to c (i).
yes, but you made libhtml in the process, which is what I'm using :)
>Tables have always been a complete bitch in rendering HTML. Part of the problem is that it is easy to inconsistently overspecify a table (e.g., the whole table must have width 3in but there are only two columns each of which must have width 2 in), and you have to experiment with, say, Internet Explorer, to see how it resolves the problem.
>I'm pretty sure Tom Duff stopped work on mothra because he hit the table wall and couldn't think of an elegant way to get past it. I stopped work on i because I had another more important project, but I was fighting table bugs, mostly, at the end.
yeah, it is not about just rendering tables, but doing it in elegantly,
well if I can't do it this way, I'll have to do it in another one,
time will tell :)
>Good luck!
thanks
>- Howard
Federico G.Benavento
---
/bin/fortune:
We are changing the alignment, not the membership. -John Mayo
next reply other threads:[~2005-10-21 14:02 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-21 14:02 Federico G. Benavento [this message]
2005-10-21 14:16 ` rog
2005-10-21 14:20 ` LiteStar numnums
2005-10-21 15:09 ` Wes Kussmaul
-- strict thread matches above, loose matches on Subject: below --
2005-10-21 18:16 Trickey, Howard W (Howard)
2005-10-21 14:37 Federico G. Benavento
2005-10-21 14:21 Federico G. Benavento
2005-10-21 14:40 ` C H Forsyth
2005-10-21 13:47 Trickey, Howard W (Howard)
2005-10-21 13:55 ` erik quanstrom
2005-10-21 14:06 ` Wes Kussmaul
2005-10-21 14:16 ` C H Forsyth
2005-10-21 15:04 ` Uriel
2005-10-21 18:45 ` Wes Kussmaul
2005-10-21 19:12 ` Uriel
2005-10-21 19:20 ` Wes Kussmaul
2005-10-21 17:35 ` Skip Tavakkolian
2005-10-21 17:51 ` David Tolpin
2005-10-21 13:40 Federico G. Benavento
2005-10-21 13:51 ` erik quanstrom
2005-10-21 4:34 Federico G. Benavento
2005-10-21 5:09 ` Federico Benavento
2005-10-21 9:49 ` Kenji Okamoto
2005-10-21 9:51 ` Kenji Okamoto
2005-10-21 13:19 ` erik quanstrom
2005-10-21 13:25 ` erik quanstrom
2005-10-20 1:56 erik quanstrom
2005-10-20 2:17 ` erik quanstrom
2005-10-20 17:04 ` Federico Benavento
2005-10-21 4:01 ` erik quanstrom
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b67622ebbe0880588f48f8cd980145a9@yourdomain.dom \
--to=benavento@gmail.com \
--cc=9fans@cse.psu.edu \
--cc=trickey@lucent.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).