[ekhtml-devel] missing feature
Brought to you by:
jick
|
From: Dave D. <dd...@re...> - 2011-07-29 20:27:29
|
I'm using ekhtml to parse the text from javascript HTML editor. My problem is that when processing the parsed text, if something interesting occurs (for example, an overset line or an illegal attribute value) there's no good way to get back to the raw html that corresponds to the problem. I can do a sort of "dead reckoning" by counting the characters in all the tags that are presented through the callbacks, but this is both cumbersome and not completely accurate. What I would like to see is a third field in every "ekhtml_string_t" table, which is the index in the original text of the tag being presented. |