Just to close out my earlier posting, I have identified and resolved the
following odfWeave/XML error:
xmlParseStartTag: invalid element name
I used odfWeave to call various logistic regression models which
included the above mentioned variable. odfWeave failed to generate the
There is a function called odfTranslate that will help deal with
characters that might confound XML. You might need to use it on the
row/column names of your output.
Max
On Oct 10, 2009, at 11:33 AM, Rob James r...@aetiologic.ca wrote:
Just to close out my earlier posting, I have
Hi Rob.
Without the file content_1.xml or any information
from the R call stack (e.g. options(error = recover)
and then run the command and dynamically explore the
state of affairs when the error occurs), there is
no way for us to know what the problem might be.
Somehow, the XML parser appears
Just so we complete (partially) the web-record...
Some further hunting determined that the apos was an apostrophe -
obvious only in retrospect! Removal of this character has resolved the
Entity errors, but not the xmlParseStartTag: invalid element name errors.
I had assumed that the two
I've been happily building a file with odfWeave, and just as the hour
draws nigh for it to be sent off, odfWeave or XML throws the following
catastrophic error:
...this is the tail of entirely uneventful processing of input file.
31 : term xml(label=LR_Fall_Model_Results)
32 : term
5 matches
Mail list logo
