Hey all
My apologies for posting this to the devel mailing list, but there
didnt seem to be any other type of list for libxml.
I have a schema that I want to read it using XML::Schema.new('path/to/
file.xsd') however when I do that with this particular schema it eats
about 2GB of RAM and 2.5G
Thats interesting, so you think the issue lay with ruby and not
libxml? Ive done stuff with cocoa on OSX, but not straight C. Any
pointers how I might be able to test if its the ruby binding? I am
afraid im not familiar with straight C. I've done stuff with
objective-c on OSX however if tha
In terms of whats going on under the hood with Schema.new()... XSD is
obviously just xml so I would imagine its parsed as per any other
file? Is there anything additional that goes on when you call
Schema.new?
Also, I have had other people tell me that the problem is due to
libxml-ruby try
Hey Chaps
Excuse my ignorance, but ive been reading the posts on the list and
the MEM2 branch seems to be a great improvement from where we were.
Now its in the trunk, what's the ETA for it being rolled out as an
official gem?
Cheers
Tim
On 14 Nov 2007, at 08:56, Dan Janowski wrote:
> Al
Hey Chaps
There seems to be some kind of issue with UTF-16 encoding in libxml-
ruby version 0.5.2.0.
When I do this:
doc = XML::Document.new()
# doc.encoding = 'utf-16'
doc.root = XML::Node.new('root_node')
root = doc.root
puts doc
## =>
Uncomment the encoding however and you get this:
doc =
Interesting stuff. Just changed back to utf-16, and using doc.dump I
see the byte order mark and the rest of the xml - result :)
Cheers guys
Tim
On 27 Nov 2007, at 04:39, Dan Janowski wrote:
> I have modified Document#to_s to permit the inclusion of a second
> encoding argument (didn't know t
Hey guys,
Im trying to install the libxsl gem on OSX, but keep getting this error:
ldruby_xslt_transform_context.o:
symbolld(:s )symbol (nots )found notfor foundarchitecture forppc
architecture i386
collect2: collect2: ld returned 1 exit statusld returned 1 exit status
lipo: can't open in
