[ 
https://issues.apache.org/jira/browse/XERCESC-1941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alberto Massari closed XERCESC-1941.
------------------------------------

    Resolution: Cannot Reproduce

You can build Xerces against ICU simply by picking the "ICU Debug" or "ICU 
Release" configuration. Changing the MSGLOADER macro does a different thing (it 
is used to load language-specific error messages) and requires building a 
separate library
                
> Xercesc-c++ does not build with ICU 4.0 when XERCES_USE_WIN32_MSGLOADER is 
> replaced with  XERCES_USE_MSGLOADER_ICU proprocessor 
> --------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: XERCESC-1941
>                 URL: https://issues.apache.org/jira/browse/XERCESC-1941
>             Project: Xerces-C++
>          Issue Type: Bug
>          Components: Build
>    Affects Versions: 3.1.1
>            Reporter: dinesh kumar
>
> I was to test the ICU build if that works fine. I created a  sample 
> application which reads utf-8 encoding doc and while trying to write the 
> cached document in to a seperate doc with different encoding (ICU supported 
> encding  e.g big5). 
> I am getting error that Xerces is unabke to create the converter for Big5. I 
> build the xerces 3.1 with ICU, i used the default settings of the 
> Xerces-all.vcproj with ICU build settings.   Ideally Xerces should be able to 
> create the converter.
> Looking at the vcproj configurations , i found that 
> XERCES_USE_WIN32_MSGLOADER is used as an pre-processor and in the code we 
> have a special handling of XERCES_USE_MSGLOADER_ICU. On replacing 
> XERCES_USE_WIN32_MSGLOADER  with XERCES_USE_MSGLOADER_ICU, Xerces fails to 
> compile completely and ask for providing the path for 
> __imp__Xercesc_messages_3_1 dat.
> How to verify that ICU build of xerces works fine.? 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to