How about using XMLString::compareIString()?

Dave



                                                                                       
                                  
                      <[EMAIL PROTECTED]                                               
                                    
                      ngcast.com>              To:      <[EMAIL PROTECTED]>            
                        
                                               cc:      (bcc: David N 
Bertoni/Cambridge/IBM)                             
                      03/25/2003 03:38         Subject: string comparisons in xerces   
                                  
                      PM                                                               
                                  
                      Please respond                                                   
                                  
                      to xerces-c-dev                                                  
                                  
                                                                                       
                                  



This is a simple question. Asking as I cannot access the xerces mailing
list archives.

The XMLString::compareString fn performs case sensitive compares. So, for
eg., if the xml has an attribute named "Attrib" and I invoke the
getAttribute fn with a param of "attrib", then the fn will fail.

What is the suggested method of making xerces treat our xml in a
case-insensitive manner ?

I dont think it is something as simple as a flag because it all boils down
to the XMLString::compareString fn and it has no provision for case
insensitive compares...


Regards,
-Vinayak

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to