You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Expansion of row and column spans: I am confident that this part of the code (span_body, span_header) is working as expected for spans in the header or the body. E.g.,
I also managed to make these functions quite robust to certain misspecifications in the HTML code. For example, in this table the last column has a span of 8, but it should be 6:
Identification of header and body elements: The identification of header and body elements is an
issue that I still have not completely solved. It's the cause of nearly all the fails right now. I tried to come up with some reasonable heuristics of how to identify these elements but it's not done yet and this still needs some more work as well as more testing with 'real-life' HTML tables. Ultimately, I think it's necessary to give users more control over identifying these elements -- or just fall back on very simple decision rules.
The text was updated successfully, but these errors were encountered:
I had to change the name for releasing it on CRAN. It's now htmltab. In the latest version, I changed the node of reference for the header and body argument. An XPath must now treat the table node as the root. E.g, for the above example, body = "//tr[./td[not(@colspan = '9')]]".
hadley
changed the title
htmltable package
Use insights from htmltab package
Mar 17, 2019
Expansion of row and column spans: I am confident that this part of the code (span_body, span_header) is working as expected for spans in the header or the body. E.g.,
I also managed to make these functions quite robust to certain misspecifications in the HTML code. For example, in this table the last column has a span of 8, but it should be 6:
Identification of header and body elements: The identification of header and body elements is an
issue that I still have not completely solved. It's the cause of nearly all the fails right now. I tried to come up with some reasonable heuristics of how to identify these elements but it's not done yet and this still needs some more work as well as more testing with 'real-life' HTML tables. Ultimately, I think it's necessary to give users more control over identifying these elements -- or just fall back on very simple decision rules.
The text was updated successfully, but these errors were encountered: