the required attribute ("ID") from the schema
> and the document, this behavior is not observed.
Not what I am seeing:
paphio:~/XML -> xmllint --noblanks test.xml
paphio:~/XML ->
Well, don't rely on this option, really.
Daniel
--
Daniel Veillard | Red Hat
On Thu, Apr 13, 2006 at 05:05:59PM -0400, Jason Viers wrote:
> Is there any reason that xmlWriterEndPI doesn't put a line break on the
> end if it's indenting?
Probably an oversight,
> If not, here's a patch for it.
thanks, applied !
Daniel
--
Daniel Veil
On Wed, Apr 26, 2006 at 09:14:10AM +0200, Roland Schwingel wrote:
> Hi Daniel...
>
> Daniel Veillard wrote:
> >
> > The patch looks fine to me, but I can't speak for the Windows users out
> there.
> > So I'm inclined to accept and apply it, bu
bly, I am not the first one to encounter this issue and it only happens
> rarely. If I have missed something somewhere, please let me know.
possibly a bug in your code to load the document in memory, libxml2
is fine with it here.
Daniel
--
Daniel Veillard | Red Hat http://re
r a structured error handler, see xmlSetStructuredErrorFunc
http://xmlsoft.org/html/libxml-xmlerror.html#xmlSetStructuredErrorFunc
Daniel
--
Daniel Veillard | Red Hat http://redhat.com/
[EMAIL PROTECTED] | libxml GNOME XML XSLT toolkit http://xmlsoft.org/
http://veillard.com/ | Rpmfind RP
depending on how fast I
go on other workload), and if this fails next tuesday or wednesday.
So hopefully svery soon, but don't hold your breath :-)
Daniel
--
Daniel Veillard | Red Hat http://redhat.com/
[EMAIL PROTECTED] | libxml GNOME XML XSLT toolkit http://xmlsoft.org/
http:
end PI (Jason Viers).
* Documentation:
- man pages updates and cleanups (Daniel Leidert).
* New features:
- Relax NG structure error handlers.
- xmlDOMWrapReconcileNamespaces xmlDOMWrapCloneNode (Kasimier Buchcik)
Thanks to everybody who helped for this release !
Daniel
--
Daniel Veil
I was wondering if
> there is any way to tell xml parser to ignore xml comments?
Get an handle to the parser context, and set a null SAX comment callback
function. Better yet, fix your app because comments are legit !
Daniel
--
Daniel Veillard | Red Hat http://redhat.com/
[EMAIL PROTECTED
On Fri, Apr 28, 2006 at 10:50:34PM +0200, Mike Hommey wrote:
> On Fri, Apr 28, 2006 at 01:09:24PM -0400, Daniel Veillard <[EMAIL PROTECTED]>
> wrote:
> > Last release was 3 months ago, and I will be in vacations most of May so
> > a release was in order ! Available as
ay
Then you can't use an XML parser, by definition. You must reject those
feeds or stop pretending being XML compliant.
Daniel
--
Daniel Veillard | Red Hat http://redhat.com/
[EMAIL PROTECTED] | libxml GNOME XML XSLT toolkit http://xmlsoft.org/
http://veillard.com/ | Rpmfind RPM
On Tue, May 02, 2006 at 02:25:00PM +0200, Olivier Sirven wrote:
> Le Mardi 2 Mai 2006 14:02, Daniel Veillard a écrit :
> > Then you can't use an XML parser, by definition. You must reject those
> > feeds or stop pretending being XML compliant.
> Ok...just to make sure I am
tware this is
especially true) is to force the error to get the input fixed, unless you
have some information which tells you what the encoding really is and
then you can still preprocess.
Daniel
--
Daniel Veillard | Red Hat http://redhat.com/
[EMAIL PROTECTED] | libxml GNOME XML XSLT toolkit
ttle to fight unfortunately, but it's the right
thing to do :-\
Daniel
--
Daniel Veillard | Red Hat http://redhat.com/
[EMAIL PROTECTED] | libxml GNOME XML XSLT toolkit http://xmlsoft.org/
http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/
___
ve counters.
they don't have a regexp serialization form in general, that might be
doable, it may as well been unreadable (e.g. xs:all), and I don't see how
you would express rules about attributes, content, and namespaces.
Daniel
--
Daniel Veillard | Red Hat http://redhat.com/
[E
Bill told me he already commited your patch to CVS, thanks :-)
Daniel
P.S.: I'm currently on vacations, do don't try to rely too much on quick answers
from me :-)
--
Daniel Veillard | Red Hat http://redhat.com/
[EMAIL PROTECTED] | libxml GNOME XML XSLT toolkit http://xmlsoft.o
t now and unable to really work on this ATM,
thanks !
Daniel
--
Daniel Veillard | Red Hat http://redhat.com/
[EMAIL PROTECTED] | libxml GNOME XML XSLT toolkit http://xmlsoft.org/
http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/
est-team for this
> enhancement ;-)
Okay, remind me this when I'm back next Monday, I will have a huge pile of
stuff to go though and helping me remember this might be a good idea :-)
Daniel
--
Daniel Veillard | Red Hat http://redhat.com/
[EMAIL PROTECTED] | libxml GNOME XML XSLT to
s to use xmlSetNsProp with a NULL namespace.
Agreed, we should not need a new interface,
Daniel
--
Daniel Veillard | Red Hat http://redhat.com/
[EMAIL PROTECTED] | libxml GNOME XML XSLT toolkit http://xmlsoft.org/
http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/
idation point is about
checking a document for conformance to *something* if you start by trusting
the document information itself, well you don't really gain much in term
of trust, or garantee of purpose for the next processing steps.
Daniel
--
Daniel Veillard | Red Hat http
want to output it as well-formed HTML, preferably with the HTML4
> > transitonal DTD but no xml declaration, eg:
It's possible, use the xmlsave.h APIs with the XML_SAVE_NO_DECL option.
Daniel
--
Daniel Veillard | Red Hat http://redhat.com/
[EMAIL PROTECTED] | libxml GNOME XML
one
else (Kasimier or Bill ?) commits it first :-)
Daniel
--
Daniel Veillard | Red Hat http://redhat.com/
[EMAIL PROTECTED] | libxml GNOME XML XSLT toolkit http://xmlsoft.org/
http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/
__
s like the xmlsave API is slightly more generic than the stuff
> the Python layer uses.
and yes, sorry
Daniel
--
Daniel Veillard | Red Hat http://redhat.com/
[EMAIL PROTECTED] | libxml GNOME XML XSLT toolkit http://xmlsoft.org/
http://veillard.com/ | Rpmfind RPM search engine http://rp
Hat to handle too,but yes TODO list for
this week.
Daniel
--
Daniel Veillard | Red Hat http://redhat.com/
[EMAIL PROTECTED] | libxml GNOME XML XSLT toolkit http://xmlsoft.org/
http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/
_
>context->lastError);
>
> Any objection if I make this change?
No objection, that sounds right !
Daniel
--
Daniel Veillard | Red Hat http://redhat.com/
[EMAIL PROTECTED] | libxml GNOME XML XSLT toolkit http://xmlsoft.org/
http://veillard.com/ | Rpmfind RPM search engine http:
On Wed, May 24, 2006 at 05:10:15PM +0200, Bjorn Reese wrote:
> Daniel Veillard wrote:
>
> > the first part of the patch looks fine to me, the second part
> >touches trio headers, it looks fine to me too but Bjorn Reese
> >should certainly have a look to see if it fits t
On Tue, Jun 06, 2006 at 09:37:25AM +0100, rachit goel wrote:
> i would like to know what all options i can give in kioskrc file
Completely unrelated to libxml2 which is the topic of this list.
Daniel
--
Daniel Veillard | Red Hat http://redhat.com/
[EMAIL PROTECTED] | libxml GNOME
if this doesn't work, check all tour compilers and flags.
Not being a Windows user I still noticed that people tend to report
those problems if the library they link together to produce the final
executable have not being compiled in the exact same environment with the
exact same flags. Mak
XSLT 1.0
written on the top page of xmlsoft.org
also support for most of EXSLT 1.0, and if needed you can hook your own
implementations at runtime.
Daniel
--
Daniel Veillard | Red Hat http://redhat.com/
[EMAIL PROTECTED] | libxml GNOME XML XSLT toolkit http://xmlsoft.org/
http://veillar
is for it. I don't know what's the best approach, and I don't have that much
time right now (though a slow but reliable implementation should not be too
hard based on the existing code).
Daniel
--
Daniel Veillard | Red Hat http://redhat.com/
[EMAIL PROTECTED] | libxml GNOME
correctness of the implementation would be
to drop the streaming node selection of the current implementation,
go back to good old raw XPath evaluation for a) and then fixe the remaining
edge bugs which are gonna pop-up.
Of course a prerequisite would be to have a final version of the ISO
spec if t
ount of allocated
blocks possibly significantly if you have short strings (or are running
on a 64 bits platform). If you don't modify the resulting tree this should
be perfectly safe.
Daniel
--
Daniel Veillard | Red Hat http://redhat.com/
[EMAIL PROTECTED] | libxml GNOME XML XSLT tool
eta-1.3.1.rng
> schema references many character entity references. Your RELAXNG schema may
> not do that so you may not have to set the SGML_CATALOG_FILES environment
> variable.
and xmllint.c code can be looked at to see how RelaxNG was used.
Daniel
--
Daniel Veillard | Red H
for this release !
And for the curious minds who wonder where 2.6.25 is, you may find it
if you dig around, but please don't use it, and for the full story ask
Kasimier ;-)
Daniel
--
Daniel Veillard | Red Hat http://redhat.com/
[EMAIL PROTECTED] | libxml GNOME XML XSLT toolkit
amaya to edit the central page xml.html and it generated
all those changes. Hopefully it's maintained in CVS, so it's was easy
to fix.
Thanks for the heads up !
Daniel
--
Daniel Veillard | Red Hat http://redhat.com/
[EMAIL PROTECTED] | libxml GNOME XML XSLT toolkit htt
se them when transforming
multiple small documents.
Maybe DocBook/TEI like stylesheets are changing that balance.
Daniel
--
Daniel Veillard | Red Hat http://redhat.com/
[EMAIL PROTECTED] | libxml GNOME XML XSLT toolkit http://xmlsoft.org/
http://veillard.com/ | Rpmfind RPM search
er,
> otherwise libxml2 won't compile.
>
> That's with the latest version, 2.6.26, is that the desired behaviour?
Hum, no, the reader should not be dependant on sax1/schemas/xptr/writer
and the tree bit could be cleaned up too. So there is something broken.
Daniel
--
D
ad or tempt file
but you have to select which parser to use.
Daniel
--
Daniel Veillard | Red Hat http://redhat.com/
[EMAIL PROTECTED] | libxml GNOME XML XSLT toolkit http://xmlsoft.org/
http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/
___
he error output does, the overall test passes. I've attempted to fix
> this.
>
> hope that makes sense,
Yes, I don't fully understand the VMS side but it's well contained so :-)
and it's good to know tests pass on another platform !
thanks for the patch, applied and comm
On Wed, Jun 14, 2006 at 03:40:38PM -0500, Felipe Contreras wrote:
> On 6/9/06, Daniel Veillard <[EMAIL PROTECTED]> wrote:
> >On Fri, Jun 09, 2006 at 02:45:06PM -0500, Felipe Contreras wrote:
> >> Hi everybody,
> >>
> >> I had a problem when trying --with-
was incrementally added and
I didn't kept track. Sometime also it's about avoiding direct dependancies
between libxml2 and libxslt (especially when adding entry point).
Daniel
--
Daniel Veillard | Red Hat http://redhat.com/
[EMAIL PROTECTED] | libxml GNOME XML XSLT toolkit http:
reader1.c:93
> #0 0x00386e21 in xmlPushInput () from /usr/lib/libxml2.so.2
> The program is running. Exit anyway? (y or n)
The crash does not happen if you remove the XML_PARSE_RECOVER option.
I will remove the crash in CVS, but I'm also thinking about ways to
allow XML_PARSE_RECO
DE and other node types are internal C values, they
got exported by the bindings generator but are not accessible from
Python.
Those 'arbitrary' strings are I think the string I saw the first
time I checked existing XML python bindings so I reus
On Mon, Jun 19, 2006 at 09:07:16PM -0700, Ryan Phillips wrote:
> Daniel Veillard wrote:
> >>[Switching to Thread -1208514336 (LWP 26163)]
> >>0x00386e21 in xmlPushInput () from /usr/lib/libxml2.so.2
> >>#0 0x00386e21 in xmlPushInput () from /usr/lib/libx
g a node type to libxml2 is not something I would do lightly.
I don't really understand what it is aiming at honnestly, nor the extend
of your question. You can always add up a function in the _private field
of a node, but that will only be interpreted by non-libxml2 code by
definition.
Dan
ECOVER only in exceptional cases.
> >
> > Daniel
> >
>
> Daniel:
>
> Was my patch going to be committed to CVS? or a derivative of it?
yes see http://xmlsoft.org/ChangeLog.html
But I will make sure this option is not used systematically before the
next release too, so
s in without
changes all other the code, a very risky business.
>
> FWIW SXML already has an understanding of lazy XML I believe:
>
> http://okmij.org/ftp/Scheme/SXML.html
first time I heard of SXML. Well they use high level language to
process the content, adding this kind of extens
is failed, the ns
> member of the nodes are empty. Is it correct that the ns member should
> be empty? How to check in a parse when and if I reach a particular
> namespace?
All the element nodes here should have a namespace, so their ->ns
should not be NULL. No idea how you
point me to the definition of replace() in the XPath or XSLT 1.0
specifications ?
http://www.w3.org/TR/xpath
http://www.w3.org/TR/xslt
Daniel
--
Daniel Veillard | Red Hat http://redhat.com/
[EMAIL PROTECTED] | libxml GNOME XML XSLT toolkit http://xmlsoft.org/
http://veillard.co
paphio:~/XML ->
> However, I am pursuing the idea of directly expressed lazyness managed
> by the dyn:evaluate function, eg:
>
>
>
>
> I'm pretty sure I can achieve what I want with only this.
At that level this might be easier, but I'm afraid
seScript().
Not sure it's much better
> Possibility a) looks better to me and might try to implement a patch
> example.
You can try, but it's all very messy IMHO, I will take patches if not
obviously broken (could be a good idea to provide examples for the test
suite too
((htmlParseLookupSequence(ctxt, '<', '/', 0, 0) < 0) ||
(avail < 8)))
goto done;
in that "Handle SCRIPT/STYLE separately" section and report ? If positive
provide a contextual patch :-)
> P
at htmlParseScript() either reaches its breaking condition
> or just consumes normal CDATA. If there are other elements after the
> script/style block, they will be parsed correctly once htmlParseScript()
> breaks, wouldn't they?
Hum, okay after thinking a bit more about it, ye
gt; appropriate checkIndex being set instead of looking for the chars
> manually. On the other hand that seems to be an overhead.
I would prefer the patch to use a second htmlParseLookupSequence() yes
that would be cleaner,
thanks,
Daniel
--
Daniel Veillard | Red Hat http://redh
currently
> pointed node is a root.
> I'd appreciate any suggestions/examples on how this can be acomplished.
use the associated xmlSave function:
http://xmlsoft.org/html/libxml-xmlsave.html#xmlSaveTree
Daniel
P.S.: and please subscribe to the list if you need further in
e to that buffer with xmlSaveToBuffer
3/ as already explained use xmlSaveTree to save to the context
the result will be in the buffer in teh encoding indicated in 2/
and with the options passed there too
Daniel
--
Daniel Veillard | Red Hat http://redhat.com/
[EMAIL PROTEC
x27;m afraid you need to go down to the C level and
check the 2 pointers, they aren't seen at the python level. Should be
a fairly easy change to python/libxml.c to add this equality entry point
and then add a method in the node class in libxml.py to be used for
comparison.
Daniel
--
Da
;t suggest to change the
default because you're just :
1/ entering MS compilation mess, for which only a few people
really answer on that list
2/ generate your own version of the package which can lead to
different behaviour, and unless you're on embedded systems
On Sat, Jun 24, 2006 at 12:26:47AM +0200, Andreas Pakulat wrote:
> On 23.06.06 17:05:08, Daniel Veillard wrote:
> > On Fri, Jun 23, 2006 at 10:07:20PM +0200, Andreas Pakulat wrote:
> > > Anybody with a hint, how to check wether 2 nodes are the same?
> >
> > unfort
On Sat, Jun 24, 2006 at 11:18:43AM +0100, David Kelvin wrote:
> If data is in a CData block, is it passed to the xmlSAX2Characters routine,
> to the xmlSAX2CDataBlock routine or both?
xmlSAX2CDataBlock if not null, to xmlSAX2Characters otherwise.
Daniel
--
Daniel Veillard | Red Ha
eral w.r.t. to doc and code example, there are some:
http://xmlsoft.org/examples/index.html
they don't cover everything, I take patches or new examples. We don't have
the manpower of the Microsoft or IBM teams to do this, heck nobody is paid
full time to work on libxml2, if that s
On Sun, Jun 25, 2006 at 10:46:18AM +0100, David Kelvin wrote:
> On 24/06/06, Daniel Veillard <[EMAIL PROTECTED]> wrote:
>
> >
> >
> >Okay. To me your approach sounds exactly like this:
> > "I don't want to invest learning libxml2 API, it's ju
On Mon, Jun 26, 2006 at 10:39:05AM +0200, Andreas Pakulat wrote:
> On 24.06.06 09:12:47, Daniel Veillard wrote:
> > On Sat, Jun 24, 2006 at 12:26:47AM +0200, Andreas Pakulat wrote:
> > > (though I'm not familiar with libxml2's C Interface, nor the
> >
gt;
if that's the case there is nothing specific to do.
Daniel
--
Daniel Veillard | Red Hat http://redhat.com/
[EMAIL PROTECTED] | libxml GNOME XML XSLT toolkit http://xmlsoft.org/
http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/
___
e of the *printf functions which tends to be broken on some libcs.
Have fun !
Daniel
--
Daniel Veillard | Red Hat http://redhat.com/
[EMAIL PROTECTED] | libxml GNOME XML XSLT toolkit http://xmlsoft.org/
http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/
__
ou need to find "GB2312" there ? This makes absolutely
no sense. If the support is in libiconv why do you expect libxml2 would have to
handle it directly ? It delegate the work to libiconv, precisely!
> Please help!
Sorry, I can't debug your proxy.
Daniel
--
Daniel Veill
,
>is added.
>
> Absent pthread_cond_destroy() produces memory leak under FreeBSD
> (~4 bytes per each xmlNewRMutex() call). Whether memory leaks on the other
> systems depends on pthread implementation.
That's commited to CVS now, thanks !
Daniel
--
Daniel Veillar
g
uuencoded string in attributes is a completely broken design.
I guess you don't find informations because it's something to avoid.
Third, no need to post things twice.
Daniel
--
Daniel Veillard | Red Hat http://redhat.com/
[EMAIL PROTECTED] | libxml GNOME XML XSLT toolk
omenamespace";>
>
>
>
>
>
> And the bit I don't understand is why the child element is marked with
> the ns namespace.
>
>
> Can anyone explain this?
Well basically xmlNewChild() create a new node in the parent namespace if
no
lParseBalancedChunkMemory
and
http://xmlsoft.org/html/libxml-parser.html#xmlParseInNodeContext
but really it's outside the definition of normal document parsing as
defined in XML-1.0
> The doc is not very extensive on libxml,
> and so good sample code is kinda required.
We take p
On Sat, Jul 01, 2006 at 10:35:48PM +0100, Nic James Ferrier wrote:
> Daniel Veillard <[EMAIL PROTECTED]> writes:
>
> > On Sat, Jul 01, 2006 at 08:34:38PM +0100, Nic James Ferrier wrote:
> >
> > Well basically xmlNewChild() create a new node in the parent na
ciated
schemas, I don't think you can fix it from the API since the reader
RNG validation context is not accessible, so please bugzilla this, this
should be easy to fix.
thanks,
Daniel
--
Daniel Veillard | Red Hat http://redhat.com/
[EMAIL PROTECTED] | libxml GNOME XML XSLT to
in a recent framework, I really don't expect this to be
a common case. The most common when you create a child of a namespaced element
is to reuse the same namespace (i.e. same vocabulary) unless you switch
to another namespaced vocabulary.
Daniel
--
Daniel Veillard | Red Hat http://re
at state will
stop processing further templates, and the processing will gracefully pop
up all template contexts.
If you experience leaks there (assuming you freed up all resources when
done) then that means there is a bug, but this really should not happen.
Daniel
--
Daniel Veillard | Red
interface.
> --> For example default attributes will not be inserted
> --> Fixed attributes will not be set
It's a concious default handling. PSVI is not part of the original document
and libxml2 is an editing toolkit initially. Now to be constructive one
could suggest
andler associated to
the reader.
But it's good that you found the workaround in the more recent versions
as it's not a completely trivial change (though it should not be hard to do).
Daniel
--
Daniel Veillard | Red Hat http://redhat.com/
[EMAIL PROTECTED] | libxml GNOME XM
behaviour is really peanuts compared to the real
problem.
> What is important for our project
which project ?
Daniel
--
Daniel Veillard | Red Hat http://redhat.com/
[EMAIL PROTECTED] | libxml GNOME XML XSLT toolkit http://xmlsoft.org/
http://veillard.com/ | Rpmfind RPM search engin
running Python regression tests
> -- thread2.py
> FAILED to obtain correct value for lineNumbersDefault in thread 56966064
>
> Is this failing ok? I might be, because the 'without-threads' flag.
compiling without threads support is risky, especially when using with
python,
r output for that special case.
Daniel
--
Daniel Veillard | Red Hat http://redhat.com/
[EMAIL PROTECTED] | libxml GNOME XML XSLT toolkit http://xmlsoft.org/
http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/
___
xml mailing list, p
Does someone know if we can safely remove the test for
> "fake node libxslt" and only leave the name[0] = ' ' test?
> Traversing the affected axes without the need for a string comparison
> would be more efficient.
That should be fine by now, I just ope people wo
sage:
pkg-config may not be correctly setup everywhere. If libxml2 is correctly
installed then xml2-config should be present.
http://xmlsoft.org/FAQ.html#Developer
Developper FAQ #1
Daniel
--
Daniel Veillard | Red Hat http://redhat.com/
[EMAIL PROTECTED] | libxml GNOME XML XSLT too
course ! But I would like to know if there is a way
> of preventing this change anyway, and keep it`s original format.
Use the functions from the xmlsave module and create the context
with the XML_SAVE_NO_EMPTY flag:
http://xmlsoft.org/html/libxml-xmlsave.html#xmlSaveOption
Daniel
-
use the new APIs
which are easier to maintain in the long term,
Daniel
--
Daniel Veillard | Red Hat http://redhat.com/
[EMAIL PROTECTED] | libxml GNOME XML XSLT toolkit http://xmlsoft.org/
http://veillard.com/ | Rpmfind RPM search engine http://rpm
xml-xmlsave.html#xmlSaveClose
> xmlThrDefSaveNoEmptyTags ?
Very bad idea it's just an accessor for the thread global variable
in thread local storage used internally.
Daniel
--
Daniel Veillard | Red Hat http://redhat.com/
[EMAIL PROTECTED] | libxml GNOME XML XSLT toolkit http://
On Fri, Jul 07, 2006 at 07:59:50AM +0200, Mike Hommey wrote:
> On Thu, Jul 06, 2006 at 03:44:14PM -0400, Daniel Veillard <[EMAIL PROTECTED]>
> wrote:
> > On Thu, Jul 06, 2006 at 03:03:12PM -0400, Jean-Francois Dupont-Viel
> > (QA/EMC) wrote:
> > > Ok it seems to
eally do what you want, it might be optimized out.
XML recommendation was issued in 1998, 8 years ago, if they still use
non-compliant tools, then as your customer they force you to develop custom
code, hence more expensive I assume, make them pay the difference, they
will end up fixing their stac
not that extra buffering layer introduced by
the encoding conversion. Check in a debugger for things like
ctxt->input->base, ctxt->input->cur and potential overflows there,
it's weird...
Daniel
--
Daniel Veillard | Red Hat http://redhat.com/
[EMAIL PROT
On Fri, Jul 07, 2006 at 05:10:52PM +0200, Kris Breuker wrote:
> Op 7-7-2006 15:51 heeft Daniel Veillard het volgende geschreven:
> >paphio:~/XML -> xmllint --noout fotoarchief.xml
> >paphio:~/XML -> /usr/bin/xmllint --noout fotoarchief.xml
> >paphio:~/XML
aming) when it seems you
need full tree informations ?
Modifying a node or document being processed by a reader is not
proper, that should be considered read-only really.
Daniel
--
Daniel Veillard | Red Hat http://redhat.com/
[EMAIL PROTECTED] | libxml GNOME XML XSLT toolkit http://
> uses libc or similar.
>
>
>
> My platform I redhat ES 3.0
I have used successully valgrind on libxml2 . For purify problems
ask their support line, there is no reason this should fail.
Daniel
--
Daniel Veillard | Red Hat http://redhat.com/
[EMAIL PROTECTED] | libxml
; xmlOutputBuffer structure, which is defined thusly:
>
http://xmlsoft.org/html/libxml-xmlIO.html#xmlOutputBufferCreateFd
Create a buffered output for the progressive saving to a file descriptor
That's what you need.
Daniel
--
Daniel Veillard | Red Hat http://redhat.com/
[EMAIL P
sage in German. Has anybody an idea how
> this could work?
Hum, not trivial, you would need to look at the exact error numbers
and depending on the error either rebuild a localized error based on the
extra inforamtions given, or apply a transformation to the string (based
for example on ss
an change that node temporary for your operation and restore
its state back before any further call to the reader, that should work,
Daniel
--
Daniel Veillard | Red Hat http://redhat.com/
[EMAIL PROTECTED] | libxml GNOME XML XSLT toolkit http://xmlsoft.org/
http://veillard.com/ | Rpmfind RPM
o idea except in that function it's the library which allocates the
output, and if you have allocator or binding problems that could very well
show up at that point.
Try to use xmlSaveToBuffer and then copy the buffer content, that
should garantee that memory allocation don't cross
lIOParseDTD (NULL, buf, XML_CHAR_ENCODING_ASCII);
> //xmlFreeParserInputBuffer(buf); <--- HERE
[...]
> But maybe could be a problem for other or maybe the mistake is mine
> (in the use of the API).
I believe xmlIOParseDTD consumes the xmlParserInputBufferPtr so it
should not be freed after the
feature which may generate
unexpected behaviour if not available, so being able to check the support
statically or at runtime is important.
Patch looks fine, applied and commited to CVS,
thanks a lot !
Daniel
--
Daniel Veillard | Red Hat http://redhat.com/
[EMAIL PROTECTED] | libxml GN
x27;s hard for me to make any serious guess on what may actually
happen in that case.
Concerning multithreading, yes libxml2 should work fine as long as 2
different threads don't access to the same document concurrently, and that
the multithread support of libxml2 was compiled in.
Daniel
--
checkouts should convert their tree. I will have to fix the tarball
snapshot generation on xmlsoft.org at some point too.
Daniel
--
Daniel Veillard | Red Hat http://redhat.com/
[EMAIL PROTECTED] | libxml GNOME XML XSLT toolkit http://xmlsoft.org/
http://veillard.com/ | Rpmfind RPM search
t is from memory)
it is not 100% garanteed to provide a correct XPath path, we had some
errors reported recently but they were fixed. Try it and report if you
have troubles (as usual :-)
Daniel
--
Daniel Veillard | Red Hat http://redhat.com/
[EMAIL PROTECTED] | libxml GNOME XML XSLT tool
the benefit
>of standardized and fully localized error messages
>
> *runs away before Daniel can grab me and force me to provide a patch*
And a patch which doesn't get in the way for those without gettext()
Daniel
--
Daniel Veillard | Red Hat http://redhat.com/
[E
e been
> fixed, and things have been re-tested satisfactorily.
>
> http://live.gnome.org/Subversion
>
> --
> Ross
--
Daniel Veillard | Red Hat http://redhat.com/
[EMAIL PROTECTED] | libxml GNOME XML XSLT toolkit http://xmlsoft.org/
http://vei
801 - 900 of 2663 matches
Mail list logo
