List Info

Thread: libxml2 on zos.
libxml2 on zos.
user name
 2006-09-13 20:10:20 

  


  

    

Thankyou gentlemen for you're interesting 
ideas.
What I've done today is:


    
  
  • recompiled 
  the libxml2 code with preparser option CONV(UTF-8) to keep the embedded 
  constants as ascii/utf-8 chars.
    • 
  
  • Because this breaks the IO code (file open mode 
  strings like "rb" no longer ebcdic), I frontended the samples with some code 
  to read the xml documents into a char buffer.  (I didn't experiment with 
  not using the conv option on the io files because mixing the encodings would 
  have gotten confusing...
    • 
  
  • Then I parsed a utf-8 encoded document 
  successfully!


I copied the group so that this info would be 
available to the community at large.


 


thanks again..


wcn




-----Original 
Message-----
From: Daniel Veillard [redhat.com">mailto:veillardredhat.com]
Sent: 
Wednesday, September 13, 2006 12:44 PM
To: Wendell Nichols
Cc: 
xmlgnome.org
Subject: Re: [xml] libxml2 on zos.

On Wed, Sep 13, 2006 
at 09:06:06AM -0700, Wendell Nichols wrote:
>; I see that the configure 
scripts are set up to recognize zos as a
> platform for this 
library.  I've compiled it on zos 1.4 but it doesn't
> seem to be 
functional there.  Because the parser.c file has embedded
> literals 
for things like '<' and '>' and the source has been compiled
&gt; on an 
ebcdic machine it fails to parse a utf8 document.
> The only way I can 
think of to deal with this is to turn conversion of
> literals off in the 
compilation ... to see what happens.&nbsp; I'll try
> that today, but in 
the meantime I'm curious if anyone out there is
> using this library on 
zos?
> Your feed back would be appreciated.

  My recollection 
is that a similar problem was raised once when compiling on MVS and the solution 
turned out to update the compiler to get a compiler flag support. But it was a 
few years ago and I don't remember the exact 
details.

Daniel

--
Red Hat Virtualization group http://redhat.com/virtualization/
Daniel 
Veillard&nbsp;   ;  | virtualization library&nbsp; http://libvirt.org/
veillardredhat.com  
| libxml GNOME XML XSLT toolkit&nbsp; http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search 
engine&nbsp; http://rpmfind.net/

  

  
  
   
     
    

  

    libxml2 on zos.
  


  

     user name

     2006-09-14 01:37:18
  


  

    
On Wed, Sep 13, 2006 at 01:10:20PM -0700, Wendell Nichols
wrote:
> Thankyou gentlemen for you're interesting ideas.
> What I've done today is:
> 
> *	recompiled the libxml2 code with preparser option
CONV(UTF-8) to
> keep the embedded constants as ascii/utf-8 chars.

  okay,

> *	Because this breaks the IO code (file open mode
strings like
> "rb" no longer ebcdic), I frontended the
samples with some code to read

  Well if you have specific zos patches for those parts that
can be isolated 
cleanly (for exemple with #ifdef ZOS or another symbol) then
submit them
so we can keep an unified code.

> the xml documents into a char buffer.  (I didn't
experiment with not
> using the conv option on the io files because mixing
the encodings would
> have gotten confusing...
> *	Then I parsed a utf-8 encoded document successfully!
> 
> I copied the group so that this info would be available
to the community
> at large.

  Thanks, but a patch correcting the problem directly at the
code level
would be more convenient if someone else ever decide to run
libxml2 in
your environment.

Daniel

-- 
Red Hat Virtualization group http://redhat.com/v
irtualization/
Daniel Veillard      | virtualization library  http://libvirt.org/
veillardredhat.com  | libxml GNOME XML XSLT toolkit  http://xmlsoft.org/
http://veillard.com/ |
Rpmfind RPM search engine  http://rpmfind.net/
_______________________________________________
xml mailing list, project page  http://xmlsoft.org/
xmlgnome.org
http://mai
l.gnome.org/mailman/listinfo/xml


  


  

    
  

  
  
   
     
    

  

    libxml2 on zos.
  


  

     user name

     2006-09-14 16:33:47
  


  

    
Daniel Veillard wrote:

>   Well if you have specific zos patches for those parts
that can be isolated 
> cleanly (for exemple with #ifdef ZOS or another symbol)
then submit them
> so we can keep an unified code.

FYI, the symbol is __MVS__ (assuming the IBM XL compiler is
used).
_______________________________________________
xml mailing list, project page  http://xmlsoft.org/
xmlgnome.org
http://mai
l.gnome.org/mailman/listinfo/xml


  


  

    
  

  
  
   
     
    

  

    libxml2 on zos.
  


  

     user name

     2006-09-14 16:33:47
  


  

    
Daniel Veillard wrote:

>   Well if you have specific zos patches for those parts
that can be isolated 
> cleanly (for exemple with #ifdef ZOS or another symbol)
then submit them
> so we can keep an unified code.

FYI, the symbol is __MVS__ (assuming the IBM XL compiler is
used).
_______________________________________________
xml mailing list, project page  http://xmlsoft.org/
xmlgnome.org
http://mai
l.gnome.org/mailman/listinfo/xml


  


  

    
  

  
  
   
     
    






 [1-4]











   
 





about | contact  Other archives ( Real Estate discussion Medical topics )