Changes between Initial Version and Version 3 of Ticket #2965


Ignore:
Timestamp:
Apr 6, 2009, 7:32:50 AM (15 years ago)
Author:
warmerdam
Comment:

Hi,

Could you please use the command "ogrinfo test.ovr test" so that ogrinfo actually reports on the features of the test layer? We are wanting to check if ogrinfo reports the umlautes properly (in which case this is a mapserver problem) or if the problem is with OGR itself. It would also be helpful to confirm the GDAL/OGR version, which you can do with the command "ogrinfo --version".

There were significant changes in GDAL 1.6.0 with regard to the ODBC driver and NVARCHAR fields - to ensure that they are captures as UTF-8. If the problem turns out to be with the ODBC driver we will need more details on how to create an ODBC datasource which demonstrates this problem.

Adding Chaitanya as a cc: as I'll likely ask him to review the problem if it turns out to be OGR's ODBC driver.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #2965

    • Property Cc warmerdam chaitanya added
    • Property Milestone → 6.0 release

  • Ticket #2965 – Description

    initial v3  
    11Moin,
    2 in MapServer 5.0.0 the ovf-file works well with Umlaute (e.g. ü, ä, ...). In MS 5.2.x the VirtualSpatialData connection supplies no result if there are Umlaute.
     2in MapServer 5.0.0 the ovf-file works well with Umlaute (e.g. ü, ä, ...). In MS 5.2.x the VirtualSpatialData connection supplies no result if there are Umlaute. 
    33
    44