From: Karl Dahlke <email@example.com>
Subject: I don't know shit about xml
Date: Wed, 19 Oct 2022 05:13:34 -0400 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
Others have also pointed me to sgml, just, you know, if we want to
understand the evolution of things.
> garbage which people wrote (and continue to write) and browsers
> into something sane.
Yes tidy did a lot of this for us, I didn't realize how much until I
wrote my own html scanner. Ugh.
I'm still making tweaks now and then.
And yet, my scanner isn't much bigger than the interface code that
connected to the tidy library, so there ya go.
> the current direction seems to make sense.
Yes I think so. Thank you.
xml as received through xhr is now parsed as xml, and that may make a
difference to some websites.
We also do some of the cdata parsing and representation, which tidy
would not be able to do for us.
So this is the right path.
prev parent reply other threads:[~2022-10-19 9:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-12 22:51 Karl Dahlke
2022-10-13 0:08 ` Dominique Martinet
2022-10-13 0:32 ` Karl Dahlke
2022-10-19 8:14 ` Adam Thompson
2022-10-19 9:13 ` Karl Dahlke [this message]
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).