From: Kevin Carhart <kevin@carhart.net>
To: Karl Dahlke <eklhad@comcast.net>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] tidy tree
Date: Fri, 28 Aug 2015 20:04:26 -0700 (PDT) [thread overview]
Message-ID: <alpine.LRH.2.03.1508281949410.10486@carhart.net> (raw)
In-Reply-To: <20150728222553.eklhad@comcast.net>
> If no one objects I will probably make some small tweaks and push this,
> it's just db5 prints so shouldn't hurt anything.
Sounds great! Yes, that one main example has been helpful. The library
documentation on htacg.org often doesn't have any actual notes or prose on
the functions, (it has that auto generated feel) but there seems to be an
adequate amount of tidy code around. For instance, I picked up from
someplace that the node name is this string type I know nothing about,
ctmbstr, but someone had cast it to a char *, so that's how I knew to try
that one.
Kevin
>
> There's no \r in your patch so I should have no trouble applyihng it.
>
> Once in, we'll want to test it on all sorts of html,
> especially embedded with javascript, to make sure the nodes are correct.
> After all, we don't know for sure that we can even use this yet,
> the conversion from html to nodes has to be almost perfect.
> Though I suppose we could report any bugs to the tidy5 team.
>
> Karl Dahlke
> _______________________________________________
> Edbrowse-dev mailing list
> Edbrowse-dev@lists.the-brannons.com
> http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev
>
--------
Kevin Carhart * 415 225 5306 * The Ten Ninety Nihilists
next prev parent reply other threads:[~2015-08-29 3:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-29 1:45 Kevin Carhart
2015-08-29 2:25 ` Karl Dahlke
2015-08-29 3:04 ` Kevin Carhart [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-08-28 2:55 [Edbrowse-dev] tidy and db5 Kevin Carhart
2015-08-28 21:35 ` [Edbrowse-dev] tidy tree Kevin Carhart
2015-08-28 21:55 ` Chris Brannon
2015-08-28 22:38 ` Kevin Carhart
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=alpine.LRH.2.03.1508281949410.10486@carhart.net \
--to=kevin@carhart.net \
--cc=Edbrowse-dev@lists.the-brannons.com \
--cc=eklhad@comcast.net \
/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).