id summary reporter owner description type status priority milestone component version severity resolution keywords cc 2339 ODBC WVARCHAR Access Lacking warmerdam warmerdam "Currently SQL Server NVARCHAR and similar native language fields are requested as SQL_C_CHAR by OGR which appears to trigger a translation to the current locale's encoding. If the field contains something like Arabic text this results in the text being corrupted (mostly turned to '?' characters). The desirable solution would be to fetch the text as UCS-2 wchar_t and translate to UTF-8 for returning from OGR. This bug is broadly address by rfc23_ogr_unicode but a more narrow fix will be required for OGR 1.5.2. " defect closed normal 1.5.3 OGR_SF unspecified normal fixed odbc WCHAR NVARCHAR UTF-8