Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.linux.development.apps > #720
| From | Lew Pitcher <lew.pitcher@digitalfreehold.ca> |
|---|---|
| Subject | re: Failure to extract information using mini-XML v2.8 |
| Newsgroups | comp.os.linux.development.apps |
| Organization | The Pitcher Digital Freehold |
| Message-ID | <MeS6v.365018$M93.361238@fx18.iad> (permalink) |
| Date | 2014-04-26 13:43 -0400 |
OK, I've added some details to minixml bug #502
It appears that there are two problems, of which one /might/ be my
misunderstanding of how the miniXML api is supposed to be used.
The primary problem seems to be that the
MXML_TEXT_CALLBACK
(defined by miniXML for use in the mxmlLoad* functions) does /not/ actually
tell miniXML to recognize text elements. When replaced with an
explicit "this node is a MXML_TEXT type" callback, I can get text back from
the XML element nodes that /should have/ text.
Now, a secondary problem has cropped up. In an XML element that looks like
<document>Hello, World</document>
with the element containing text only, and no intervening subordinate XML
elements at all, the mxmlGetText() call (when applied to the element,
loaded by mxmlLoadFile() with the explicit text callback) /only/ retrieves
the first non-blank text ("Hello,").
--
Lew Pitcher
"In Skills, We Trust"
PGP public key available upon request
Back to comp.os.linux.development.apps | Previous | Next — Next in thread | Find similar
re: Failure to extract information using mini-XML v2.8 Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2014-04-26 13:43 -0400 Re: Failure to extract information using mini-XML v2.8 vanderheijden.mark@gmail.com - 2014-07-30 07:03 -0700
csiph-web