> Next time you need to extract some data from an xml file, please (for
> your own good) don't do whatever you did in that code -- note that the
> unicode equivalent of "<" is u"\u003c", NOT u"\u3c00"; I wasn't joking
> when I said it had been FU.
Is that perhaps the doing of going from littleEnd
On Mar 5, 8:57 am, JT wrote:
> On Mar 4, 9:30 pm, John Machin wrote:
>
> > Your data has been FUABARred (the first A being for Almost) -- the
> > "\u3c00" and "\u3e00" were once "<" and ">" respectively. You will
>
> Hi John,
>
> I realized that a few minutes after posting. I then realized th
On Mar 4, 9:30 pm, John Machin wrote:
> Your data has been FUABARred (the first A being for Almost) -- the
> "\u3c00" and "\u3e00" were once "<" and ">" respectively. You will
Hi John,
I realized that a few minutes after posting. I then realized that
I could just extract the text between th
On Mar 5, 6:53 am, JT wrote:
> Yo,
>
> So I have almost convinced a small program to do what I want it to
> do. One thing remains (at least, one thing I know of at the moment):
> I am converting xml to some other format, and there are strings in the
> xml like this.
>
> The python:
>
> elif v ==
Yo,
So I have almost convinced a small program to do what I want it to
do. One thing remains (at least, one thing I know of at the moment):
I am converting xml to some other format, and there are strings in the
xml like this.
The python:
elif v == "content":
print "content", a.
