2 ms·

I understand what you're talking about re: < and '<' -- the json -looks- page (terminal in my case) displayable, barring the &#xhhhh; encoding. cURL has f

by bch 12y ago

I understand what you're talking about re: < and '<' -- the json -looks- page (terminal in my case) displayable, barring the &#xhhhh; encoding. cURL has facilities for decoding %20 (for example), but not what we're getting back w/ this json. You've given me an idea though, so back to vi for me. Thx.

mh- 12y ago
not sure if you figured something out already, but just saw your comment and remembered that this exists in PHP: http://us1.php.net/manual/en/function.get-html-translation-table.php http://us1.php.net/manual/en/function.get-html-translation-t... absent another source, you could dump it out for your usage elsewhere. % php -r 'print_r(get_html_translation_table(HTML_ENTITIES, ENT_QUOTES|ENT_HTML5));' or % php -r 'print json_encode(get_html_translation_table(HTML_ENTITIES, ENT_QUOTES|ENT_HTML5));' | jq . edit: just found http://dev.w3.org/html5/html-author/charref http://dev.w3.org/html5/html-author/charref (but might be harder to parse..)
- deleted 12y ago
  [deleted]

I understand what you're talking about re: &#x3c; and '<' -- the json -looks- page (terminal in my case) displayable, barring the &#xhhhh; encoding. cURL has f

I understand what you're talking about re: &#x3c; and '<' -- the json -looks- page (terminal in my case) displayable, barring the &#xhhhh; encoding. cURL has f

I understand what you're talking about re: < and '<' -- the json -looks- page (terminal in my case) displayable, barring the &#xhhhh; encoding. cURL has f

I understand what you're talking about re: < and '<' -- the json -looks- page (terminal in my case) displayable, barring the &#xhhhh; encoding. cURL has f