[gdal-dev] Why does ogrinfo use backtics in the output?

[Even Rouault]

Hi Jukka,

those backtics are there from day one: 
https://github.com/OSGeo/gdal/commit/3359e3f9f2b1d4c1197ab14395efe652eded37da 
. I suppose this is just for aesthetics. I assume this should be fine to 
change that to single quotes (although some downstream consumers that 
would dump ogrinfo output and do exact comparison with reference files 
would probably be unhappy, but we have regularly do changes that affect 
the exact output of ogrinfo through the years).  If you want to do that, 
a few expected results in autotest/utilities/test_ogrinfo.py will need 
to be adapted as well as 
https://github.com/OSGeo/gdal/blob/master/apps/ogrinfo.cpp

Even

Le 21/03/2022 à 12:43, Rahkonen Jukka (MML) a écrit :
>
> Hi,
>
> I have been wondering for a long time why orginfo is using 
> backtics/backquotes in the output. In this example before “foo” and “ESRI”
>
> ogrinfo foo.shp
>
> INFO: Open of `foo.shp'
>
>       using driver `ESRI Shapefile' successful.
>
> Not so big problem but in markup the backtick means the beginning/end 
> of a code block and copy-pasting ogrinfo report may require some hand 
> editing. Would it make any harm to use single quotes at both ends?
>
> -Jukka Rahkonen-
>
>
> _______________________________________________
> gdal-dev mailing list
> gdal-dev at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/gdal-dev

-- 
http://www.spatialys.com
My software is free, but my time generally not.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20220321/7e7dacbf/attachment.html>