Support Unicode encoding in the Categories




Jerry Faust
January 6, 2019, 9:29 PM

This was an extensive change. Starting at the innermost functions of the Categories, the changes cascaded out quite a ways. The extent of these changes is beneficial in the long run because it brings us closer to being fully Unicode capable.

As categories involve function processing, the changes affected various Function classes, Expression and Parser classes, and Label and Field classes. I thought it necessary to include not only the Field contents (absolutely necessary) but also the Field Names, since they are displayed in various ways (e.g. Column headers and Error messages).

And finally, changes to the Field collections affected the Table class and a couple Ogr classes. I wanted to be careful to minimize changes to these classes since they are so fundamental to this project.

Most of the changes were simply replacing CString with CStringW classes as the container for the field names and values. This in turn forced replacement of the various conversion macros (e.g. A2BSTR replaced with W2BSTR, and OLE2A replaced with OLE2W).

And although the resulting component successfully handles the Russian Category unit test, we need to monitor the general processing of both Shapefiles and OGR datasets for proper handling and display of the data.

Jerry Faust
November 28, 2018, 6:21 PM

I will have a look and get back to you.

Paul Meems
November 28, 2018, 4:44 PM

Hi any suggestion on this one?
It would be nice if we could include this in the next release as well.
I already created a unit test for this: D:\dev\MapwinGIS\unittests\MapWinGISTests\ShapefileTests.cs CreateRussianCategories



Jerry Faust


Paul Meems



Epic Link

Affects versions

Fix versions