topic Re: File Geodatabase API to support Unicode ? in File Geodatabase API Questions https://community.esri.com/t5/file-geodatabase-api-questions/file-geodatabase-api-to-support-unicode/m-p/679119#M1101 <HTML><HEAD></HEAD><BODY><SPAN>Yes. In general wstring is used for all character parameters in the API. This implies that we are using wchar_t. But in addition to that, we are using UTF-16 encoded characters in the wchar array. Our contract is that the wstrings that we provide as output are always UTF-16 encoded characters, and we require that developers supply the same for input strings that they use in any API function call.</SPAN><BR /><BR /><SPAN>The exception is XML data. For XML, we use std::string, not wstring. The reason is that our XML is required to use UTF-8 encoded characters. XML is general supplied in UTF-8, and the std::string class is a better fit for working with UTF-8. We have found that using std::string to contain UTF-8 encoded XML strings is very commonly done in the C++ development community.</SPAN></BODY></HTML> Wed, 14 Sep 2011 17:21:28 GMT LanceShipman 2011-09-14T17:21:28Z File Geodatabase API to support Unicode ? https://community.esri.com/t5/file-geodatabase-api-questions/file-geodatabase-api-to-support-unicode/m-p/679118#M1100 <HTML><HEAD></HEAD><BODY><SPAN>Does File Geodatabase API to support Unicode ?</SPAN><BR /><BR /><SPAN>Thanks.</SPAN></BODY></HTML> Wed, 14 Sep 2011 17:07:36 GMT https://community.esri.com/t5/file-geodatabase-api-questions/file-geodatabase-api-to-support-unicode/m-p/679118#M1100 JasonChen1 2011-09-14T17:07:36Z Re: File Geodatabase API to support Unicode ? https://community.esri.com/t5/file-geodatabase-api-questions/file-geodatabase-api-to-support-unicode/m-p/679119#M1101 <HTML><HEAD></HEAD><BODY><SPAN>Yes. In general wstring is used for all character parameters in the API. This implies that we are using wchar_t. But in addition to that, we are using UTF-16 encoded characters in the wchar array. Our contract is that the wstrings that we provide as output are always UTF-16 encoded characters, and we require that developers supply the same for input strings that they use in any API function call.</SPAN><BR /><BR /><SPAN>The exception is XML data. For XML, we use std::string, not wstring. The reason is that our XML is required to use UTF-8 encoded characters. XML is general supplied in UTF-8, and the std::string class is a better fit for working with UTF-8. We have found that using std::string to contain UTF-8 encoded XML strings is very commonly done in the C++ development community.</SPAN></BODY></HTML> Wed, 14 Sep 2011 17:21:28 GMT https://community.esri.com/t5/file-geodatabase-api-questions/file-geodatabase-api-to-support-unicode/m-p/679119#M1101 LanceShipman 2011-09-14T17:21:28Z