So I'm trying to parse school's website for some info. I'm trying to get some values using xpath. So I found a html 5 parser and it can't properly parse the first line. Then I figure you it's actually XHTML and not HTML. After quick Google search I found out XHTML can be properly parsed using any XML parser and so I found one and... It can't parse the first line. So I ask LLama3.1 (like a real programmer) why I can't parse the first line with any parser. It explained so nicely that I did not destroy my keyboard when I was told that this document is "XHTML 1.0 Transitional" and it's a mix of HTML 4 and XHTML and can't be parsed with HTML nor XML parser. I hate the guy that invented that so much...

So I can't find a crate to parse XHTML 1.0 transitional? Or a crate to convert xhtml to something else? Any advice?

top 7 comments

sorted by: hot top controversial new old

[–] gsfraley@lemmy.world 3 points 2 weeks ago (1 children)

I would try another HTML 5 parser. HTML 5 is somewhat of a unification of HTML and XHTML, getting into syntax-specifics between the two with XML parsing is probably going to be an uphill battle. That said, I'm curious what the first line is, it could just be malformed entirely.

[–] chevy9294@monero.town 2 points 2 weeks ago (1 children)

Thats the first line:

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

I thought it was html because it everything on the web is html. But because of the first line I figured out it was xhtml which should be parsed with xml parser, but I did not know the transitional is a mix which cant be parsed with anything.

[–] gsfraley@lemmy.world 2 points 2 weeks ago (1 children)

Hmm, doctype declarations are sort of like the markup equivalent of headers. Usually parsers read them to know what flavor to expect and then go parse the rest of the page separately. You shouldn't have to do this, but if you chop off that first line and run it through a standard HTML parser it might work fine.

[–] chevy9294@monero.town 1 points 2 weeks ago* (last edited 2 weeks ago)

Thats the first thing that I tried and still failes somewhere deep in the html where I probably shouldn't skip a line.

[–] calcopiritus@lemmy.world 2 points 1 week ago

HTML is hard to parse because it allows mistakes.

I don't know the answer to your question. But if it was me, I'd run the HTML parser until it encounters an error, manually fix the error, then try to parse again. Until it parses correctly.

[–] taladar@sh.itjust.works 2 points 1 week ago

Have you tried some tag soup parser? That should work as a last resort even if the ones building a tree structure don't.

[–] webbureaucrat@programming.dev 1 points 1 week ago* (last edited 1 week ago)

I wish I could be more help. My advice is you need a better grade of general purpose HTML parsing library, possibly even a browser emulator, rather than a lib specifically for XHTML 1.0 transitional or a converter.

In my Python web automation course in college we used BeautifulSoup and I think maybe mechanize. I think either of those would probably be robust enough to do what you’re trying to do, but if it has to be Rust I’m not sure what’s out there. Otherwise you could upgrade to Selenium or something.

Or if you’re trying to do something fairly simple and you don’t need to parse the whole thing but it’s still a little too complex for plain old regular expressions, you might be able to build a simple parser with the rust pest crate, but of course I would absolutely not recommend trying to build your own full-featured XHTML parser.