On mardi 6 octobre 2020 14:36:44 CEST Brad Hards wrote: > While looking at some NITF test data, Ive found a problem in how we handle > ECS-A (and ECS) characters. BCS-A (essentially ASCII) is fine. However > MIL-STD-2500C CN2 allows some header fields to be ECS-A, and the test data > does this. > > Ive also hit TREs with µm, where the µ character is encoded as 0xB5 in > ECS-A (UTF-8 would be 0xCE 0xBC) > > > > Id appreciate some guidance on how to best address this. I can see two > options handle it internal to the NITF driver, or (somehow) modify > CPLRecode or iconv to handle this special case. Im currently planning the > former.
Brad, as I'm not sure we'd have other needs for ECS-A support elsewhere in the codebase, handling that in the NITF driver is probably fine Even -- Spatialys - Geospatial professional services http://www.spatialys.com
_______________________________________________ gdal-dev mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/gdal-dev
