Hi, The named maintainer thing may reflect this thread Re: [gdal-dev] C# bindings compilation<https://www.mail-archive.com/gdal-dev@lists.osgeo.org/msg35936.html> from 2021.
-Jukka Rahkonen- Lähettäjä: gdal-dev <gdal-dev-boun...@lists.osgeo.org> Puolesta Paul Harwood via gdal-dev Lähetetty: keskiviikko 29. tammikuuta 2025 10.14 Vastaanottaja: Even Rouault <even.roua...@spatialys.com> Kopio: gdal-dev <gdal-dev@lists.osgeo.org> Aihe: Re: [gdal-dev] CSharp bindings queued for removal (was Re: GDAL CSharp bindings maintainers/contributors listening... ?) It seems to be a hyper aggressive move to go from a highly technical question about UTF-8 to "remove C# totally". If the question is "We need a named maintainer for C# or we remove it" then I will step forward since I have an app that depends on it. However, I don't feel competent enough in SWIG to address detailed changes such as UTF-8 without help. I seem to remember saying the same thing a few years ago and did not even get an acknowledgement that I had responded. Paul On Wed, 29 Jan 2025, 04:32 Even Rouault via gdal-dev, <gdal-dev@lists.osgeo.org<mailto:gdal-dev@lists.osgeo.org>> wrote: Hearing silence, the only logical conclusion is that there is no interest ==> https://github.com/OSGeo/gdal/pull/11746 Le 27/09/2024 à 20:15, Even Rouault via gdal-dev a écrit : Hi, This is your regular remainder that nobody in the core GDAL maintainer team is a CSharp aficionado (we don't have a personal grief against it, just that we are blatantly ignorant, at least speaking for myself !), so related tickets about it will definitely result in no action. See https://github.com/OSGeo/gdal/issues?q=is%3Aissue+is%3Aopen+label%3A%22csharp+bindings%22 The current trend is that people seem to be annoyed by UTF-8 related issues. The issue is likely that our methods that accept or take a const char* in the SWIG bindings should use a specific typemap to map to CSharp Unicode strings instead of the "C" one or whatever those concepts are called in CSharp. There is an existing "utf8_path" typemap that is used in method that accept filenames, that should probably be renamed to utf8_string and be used more extensively. And probably with a version of the methods to also return a raw C string / bytearray in the cases where drivers don't know the encoding and might return "random" stuff. Cf pull request #10652 where I did something for Java that suffered from that later issue. Happy pull requests! Even -- http://www.spatialys.com<http://www.spatialys.com/> My software is free, but my time generally not. _______________________________________________ gdal-dev mailing list gdal-dev@lists.osgeo.org<mailto:gdal-dev@lists.osgeo.org> https://lists.osgeo.org/mailman/listinfo/gdal-dev -- http://www.spatialys.com<http://www.spatialys.com/> My software is free, but my time generally not. Grumpy maintainer. "De l'égo à l'égoût, il n'y a qu'une bouche mal refermée", André Isaac _______________________________________________ gdal-dev mailing list gdal-dev@lists.osgeo.org<mailto:gdal-dev@lists.osgeo.org> https://lists.osgeo.org/mailman/listinfo/gdal-dev
_______________________________________________ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
