Why not incorporate this into jq itself, like perhaps adding some command line arguments to switch to HTML mode?
Would probably be more useful to implement html2json, and pipe in html?
Htmlq: like jq, but for html
71–80 of 172 posts
Re: Htmlq: like jq, but for html
#72From examples, this is only like jq in the sense that the q stands for the same thing. Even the way it does that is different. An xmlq that was really like jq would be fun, about 20 years ago.
There is `xq` today, which parses XML like `jq`. I think that it is relatively unknown because it is part of the `yq` package for parsing YMAL. So just install `yq` via PIP and you'll get `xq` as well. There is also `xmlstarlet` for parsing XML in a similar fashion.
Just looked into this and I think it's worth mentioning that there are two different projects called `yq`. The first one that came up (written in go instead of python) is not the right one and doesn't have the `xq` tool.
Re: Htmlq: like jq, but for html
#73Maybe call it hq ?
My thoughts EXACTLY... but anyway, great new utility indeed!
Re: Htmlq: like jq, but for html
#74Re: Htmlq: like jq, but for html
#75"htmlq: like jq, but for HTML"
"jq is like sed for JSON data"
sed: "While in some ways similar to an editor which permits scripted edits (_such as ed_), sed works by making only one pass over the input(s)"
ed: "ed is a line-oriented text editor".
Software definition through a reference to another software is somewhat confusing. Potential users come from different backgrounds (I had no idea what is jq), and it is not clear what are the defining features of each project. Is jq line oriented? Is htmlq operating in a single pass?
Re: Htmlq: like jq, but for html
#76If you make the html well formed, xpath also works great. Great stuff if you ever need to pick html apart. Used this quite a bit when microformats were still a thing together with jtidy. Jq is very loosely inspired by that, I guess. Might come full circle here and use some XSL transformations ...
You can usually find a html parser for your language, that you can use xpath/xsl on. It will just make the same assumptions that the browser does, by adding missing closing tags etc.
I made a tool that extracted parts of web pages 10-15 years ago, and it worked well. There are of course cases where the html is so unstructured that the results were unpredictable, but it worked well in general.
Re: Htmlq: like jq, but for html
#77is anyone else using the https://github.com/json-path/JsonPath over the jq route?
I hope we standardize on some jq query language, like we have with a base set of SQL syntax
Re: Htmlq: like jq, but for html
#78"htmlq: like jq, but for HTML" "jq is like sed for JSON data" sed: "While in some ways similar to an editor which permits scripted edits (_such as ed_), sed works by making only one pass over the input(s)" ed: "ed is a line-oriented text editor". Software definition through a reference to another software is somewhat confusing. Potential users come from different backgrounds (I had no idea what is jq), and it is not…
What's this thing called a "computer" that people keep going on about, anyway?
Re: Htmlq: like jq, but for html
#79Just being that guy: is there a reason you didn't call it hq?
Re: Htmlq: like jq, but for html
#80"htmlq: like jq, but for HTML" "jq is like sed for JSON data" sed: "While in some ways similar to an editor which permits scripted edits (_such as ed_), sed works by making only one pass over the input(s)" ed: "ed is a line-oriented text editor". Software definition through a reference to another software is somewhat confusing. Potential users come from different backgrounds (I had no idea what is jq), and it is not…
The first three are not proper definitions per-se but kind of an advertisement, trying to familiarize by self-comparison with a tried & true tool that has proven its worth.
You know Jimmy the famous mechanic? I'm Timmy, _his brother_ but an electrician.
IMO, at least `jq` has proven itself as the indispensable tool for json-data manipulation.