It doesn't appear to me that the flag on XML::Parser
'default_load_external_dtd" works.
Looking at the source:
VALUE
ruby_xml_parser_default_load_external_dtd_get(VALUE class) {
if (xmlSubstituteEntitiesDefaultValue)
return(Qtrue);
else
return(Qfalse);
}
I think the variable to
d is a possible bug with XPath
on documents that have DTD's specifying namespaces. This may be the
same as another thread I just saw so I'll post my reply to that one.
Thanks,
Paul
> On Nov 26, 2007, at 16:18, Paul Dlug wrote:
>
>> It doesn't appear to me that the
I think I have a related bug that your patch doesn't fix. If I have a
document with a DTD declaration specifying a namespace and an
identical document without it the XPath expression finds the node in
the document w/o DTD but not with the DTD. The attached test case
illustrates the problem,
On Nov 27, 2007, at 11:05 AM, Dan Janowski wrote:
> The method mapping was transposed and is fixed in svn #220
>
> See if that works now.
It's working great now. Thanks!
--Paul
> On Nov 27, 2007, at 10:17, Paul Dlug wrote:
>
>>
>> On Nov 26, 2007, at 9:34 P
There is a serious inconsistency when "round tripping" XML containing
UTF-8 characters. If you output the document to a string after parsing
you get the UTF-8 back out, if you just grab a node and convert to a
string you get UTF-8 characters substituted with entities:
utf8test.rb:
require '
I see patch #7758 hasn't been worked on or updated since submission
(long ago):
http://rubyforge.org/tracker/index.php?func=detail&aid=7758&group_id=494&atid=1973
This seems like a great idea and the new parse method solves
eliminates the need for part of the patch I submitted (#15807). Is
use.
--Paul
> On Nov 27, 2007, at 11:41, Paul Dlug wrote:
>
>> There is a serious inconsistency when "round tripping" XML containing
>> UTF-8 characters. If you output the document to a string after
>> parsing
>> you get the UTF-8 back out, if you ju
is since I'm not the
familiar with the namespace code at this point.
Thanks,
Paul
libxml-patched.tar.gz
Description: GNU Zip compressed data
On Nov 27, 2007, at 13:48, Paul Dlug wrote:
I see patch #7758 hasn't been worked on or updated since submission
(long ago):
http://ru
Dan,
Just wondering, any feedback on this?
Thanks,
Paul
On Nov 27, 2007, at 11:41 PM, Paul Dlug wrote:
>
> On Nov 27, 2007, at 3:26 PM, Dan Janowski wrote:
>
>> I see the merit in this kind of approach but it cannot conflict with
>> the libxml work flow. I.e.:
est
cases that are actually descriptive, the current structure is too
cryptic to be really useful.
--Paul
> On Dec 3, 2007, at 14:52, Paul Dlug wrote:
>
>> Dan,
>>
>> Just wondering, any feedback on this?
>>
>>
>> Thanks,
>> Paul
>>
>>
Even if XML::Parser.default_load_external_dtd is set to false the
parser loads the DTD, see test script:
require 'xml/libxml'
xml =
On Dec 8, 2008, at 2:09 AM, Charlie Savage wrote:
Hi everyone,
Over the last month there I've put out a series of libxml 0.9.x
releases with the aim of reaching 1.0 by the end of the year.
These releases have made a number of improvements to libxml-ruby,
including:
* Fix all known segm
Is anyone in the process of updating the libxslt-ruby bindings for the
latest libxml? The current bindings are based on 0.9.x and segfault if
passed a node from libxml-ruby > 1.0. I'm happy to hack up an update
if no one else is working on it.
--Paul
___
13 matches
Mail list logo
