Sophia, I just got Jesse's address. Thanks!
'Safe'
Buffistas Building a Better Board
Do you have problems, concerns or recommendations about the technical side of the Phoenix? Air them here. Compliments also welcome.
Hostrocket has told me they can't offer CVS for our purposes. I've replied asking them for what purposes it's usable.
I'll be over here, setting something up in case hostrocket doesn't work out. ita, profile addy is good if you need anything from me.
I think we should just go with Karl's machine.
Karl, yell when you have something set up we can poke, can you?
they can't offer CVS for our purposes
I think in this case that "for your purposes" is just one of those meaningless strings that businesses add to the end of sentences so they won't just say "No.".
In other news, the last approach to parsing HTML, where I processed all end tags against start tags, is fatally flawed, as it will pass this:
</i><i>
as perfectly good code, what with the matching and the cancelling and the flavin.
Order is important. So, here's the new theory. We count all troublesome starting tags, and if there's a matching end-tag for them, we delete both. That won't find really curly problems but it will at least make a cursory inspection and identify unclosed tags.
Is it just me, or does that seem too easy? It would find unclosed table tags and unmatched TD tags.
Is it just me, or does that seem too easy?
It seems like it will have the same problem you're having now.
I think we need to process the tags in order, so we have to figure out how iteratate over all the tags in order in PHP. If we can do that, the current algorithm will work fine.
we have to figure out how iteratate over all the tags in order in PHP
Like
foreach ($taglist as $tag) { dojohnhmagic(); }or has my skimming impaired my understanding of where we are right now?
Hmm, actually, if we can change the regex to collect both open and close tags, and if they are returned in the order they appear in the text, ita's suggestion is right on the nose.
if we can change the regex to collect both open and close tags, and if they are returned in the order they appear in the text
You mean that wasn't implicit in my post above, which doesn't mention the idea at all?
I certainly thought it...