Hi,
Goran Hasse wrote:
> When a xmlParseMemory( ... ) i called a xml processing tag
> is inserted in the document.
Definitely not. I think you are mixing this up with the serialisation function
you are using.
Stefan
___
xml mailing list, project pag
Hello all,
Sorry if I missed a section in the FAQ where this should be explained...
When a xmlParseMemory( ... ) i called a xml processing tag
is inserted
in the document. This is most anoying. Is it possible to disable this
in some way?
I dont se the rationale for this. Can someone put up a s
Hi,
The changes around line 266 in dict.c which relate to
xmlDictComputeBigKey, at least on solaris, require the inclusion
of to pick up the defintion of uint8_t and uint16_t.
Thanks,
Matt
--
Matthew Goebel : [EMAIL PROTECTED] : Unix Jockey @ EMU : Hail Eris
Neo-Student, Net Lurker, Donut
Rob Richards wrote:
Can you report this as a PHP bug?
For reference:
http://bugs.php.net/bug.php?id=45996
Col
--
Colin Guthrie
gmane(at)colin.guthr.ie
http://colin.guthr.ie/
Day Job:
Tribalogic Limited [http://www.tribalogic.net/]
Open Source:
Mandriva Linux Contributor [http://www.mand
Rob Richards wrote:
Colin Guthrie wrote:
Hi Daniel,
Daniel Veillard wrote:
Python serialization code was broken in 2.7.0 so here is a new release
with a cleanup of that code, even more isolation of the new buffer type
from user code and a couple of fixes:
* Portability fix:
- Borland C fix
Colin Guthrie wrote:
Hi Daniel,
Daniel Veillard wrote:
Python serialization code was broken in 2.7.0 so here is a new release
with a cleanup of that code, even more isolation of the new buffer type
from user code and a couple of fixes:
* Portability fix:
- Borland C fix (Moritz Both)
* Bug
Hi Daniel,
Daniel Veillard wrote:
Python serialization code was broken in 2.7.0 so here is a new release
with a cleanup of that code, even more isolation of the new buffer type
from user code and a couple of fixes:
* Portability fix:
- Borland C fix (Moritz Both)
* Bug fixes:
- python seria
