On 1/19/10 9:26 PM, Nikolay Sivov wrote:
On 1/19/2010 19:36, Jacek Caban wrote:
Hi*Nikolay*,
> If I'm right then only solution is to link to libxml2 statically from
> each module. Is it an acceptable way?
>
> P.S. having a separate copy of libxml2 allows to tweak its namespace
> support (I
On 1/19/2010 19:36, Jacek Caban wrote:
Hi*Nikolay*,
> If I'm right then only solution is to link to libxml2 statically from
> each module. Is it an acceptable way?
>
> P.S. having a separate copy of libxml2 allows to tweak its namespace
> support (I believe there's some discussions of that
Hi*Nikolay*,
If I'm right then only solution is to link to libxml2 statically from
each module. Is it an acceptable way?
P.S. having a separate copy of libxml2 allows to tweak its namespace
support (I believe there's some discussions of that problem in bugzilla).
I think it would be bet
On 1/17/2010 00:11, Mike Kaplinskiy wrote:
While we're on the subject of libxml2, there is a small problem with
the way we use xmlAddChild. msxml doesn't automatically coalesce text
nodes when two are next to each other in the tree and keeps them as
two separate entities (you call normalize to co
On 1/17/2010 00:11, Mike Kaplinskiy wrote:
While we're on the subject of libxml2, there is a small problem with
the way we use xmlAddChild. msxml doesn't automatically coalesce text
nodes when two are next to each other in the tree and keeps them as
two separate entities (you call normalize to co
While we're on the subject of libxml2, there is a small problem with
the way we use xmlAddChild. msxml doesn't automatically coalesce text
nodes when two are next to each other in the tree and keeps them as
two separate entities (you call normalize to coalesce them). libxml2
does this automatically
On 1/16/2010 18:40, Dan Kegel wrote:
http://xmlsoft.org/threads.html says it's only a problem
if the same document is being parsed by both threads.
The trouble scenario seems unlikely, offhand.
Yes, it seems so. There should be a problem sharing documents cause
msxml and xmllite don't
have
http://xmlsoft.org/threads.html says it's only a problem
if the same document is being parsed by both threads.
The trouble scenario seems unlikely, offhand.
