<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
Hi,<br>
<br>
<br>
<blockquote type="cite">Anyway this would be more a topic for an
issue at <a class="moz-txt-link-freetext"
href="https://github.com/opengeospatial/geotiff/issues">https://github.com/opengeospatial/geotiff/issues</a>
. I've added a note to the existing
<a class="moz-txt-link-freetext"
href="https://github.com/opengeospatial/geotiff/issues/56#issuecomment-2039505940">https://github.com/opengeospatial/geotiff/issues/56#issuecomment-2039505940</a></blockquote>
Understood, but before jumping there with my opinionated ideas, let
me point out that the root of the problem is the TIFF6.0 standard
that continues to define field type 2 as ASCII. Their exact wording
is: "8-bit byte that contains a 7-bit ASCII code; the last byte must
be NUL (binary zero)" (page 15)<br>
<br>
IMO everything would work just fine if this would be replaced with
"8-bit byte that contains UTF8 code units; the last byte must be NUL
(binary zero)". Given that UTF-8 is an extension of ASCII, backwards
compatibility wouldn't be so bad.<br>
<br>
<pre class="moz-signature" cols="72">Mircea Neacsu
On 4/5/2024 6:59 AM, Even Rouault wrote:</pre>
<blockquote type="cite"
cite="mid:8bee250e-88ee-4e9f-a16e-c8b122f84d90@spatialys.com">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<p>Hi,</p>
<p>OGC GeoTIFF mostly formalizes the historical GeoTIFF 1.0
specification from 1995, and UTF-8 at that time was still in its
youth years. Not to be mentioned that GeoTIFF was initially
developed by NASA' JPL, so I assume ASCII was good enough at
that time for their purpose. As far as I can see all EPSG CRS
names as currently only use ASCII. It is true though that WKT
CRS potentially allows for more than ASCII for CRS name, but
only in the Latin1 character set.<br>
</p>
<p>Anyway this would be more a topic for an issue at <a
class="moz-txt-link-freetext"
href="https://github.com/opengeospatial/geotiff/issues"
moz-do-not-send="true">https://github.com/opengeospatial/geotiff/issues</a>
. I've added a note to the existing
<a class="moz-txt-link-freetext"
href="https://github.com/opengeospatial/geotiff/issues/56#issuecomment-2039505940"
moz-do-not-send="true">https://github.com/opengeospatial/geotiff/issues/56#issuecomment-2039505940</a><br>
</p>
<p>Even<br>
</p>
<div class="moz-cite-prefix">Le 05/04/2024 à 12:44, Mircea Neacsu
via PROJ a écrit :<br>
</div>
<blockquote type="cite"
cite="mid:18eaddbd3a4.11b6738052717020.5186738563340338530@neacsu.net">
<meta content="text/html; charset=UTF-8"
http-equiv="Content-Type">
<div
style="font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 10pt;">
<div>Hello,<br>
</div>
<div><br>
</div>
<div>I had to read a bit deeper the Geo TIFF 1.1 standard and
I was quite surprised to see that in doesn't allow any
character representation outside the 7-bit ASCII text. Am I
missing something?<br>
</div>
<div><br>
</div>
<div>In particular CitationGeoKeys that are mandatory in
certain cases do not allow for anything other than ASCII
text. Seems a bit strange for an international standard.<br>
</div>
<div><br>
</div>
<div class="zmail_signature_below">
<div id="" data-zbluepencil-ignore="true"
data-sigid="5934168000004827002">
<div>-- <br>
</div>
<div><br>
</div>
<div>Mircea Neacsu <br>
</div>
</div>
</div>
<div><br>
</div>
</div>
<br>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
PROJ mailing list
<a class="moz-txt-link-abbreviated moz-txt-link-freetext"
href="mailto:PROJ@lists.osgeo.org" moz-do-not-send="true">PROJ@lists.osgeo.org</a>
<a class="moz-txt-link-freetext"
href="https://lists.osgeo.org/mailman/listinfo/proj"
moz-do-not-send="true">https://lists.osgeo.org/mailman/listinfo/proj</a>
</pre>
</blockquote>
<pre class="moz-signature" cols="72">--
<a class="moz-txt-link-freetext" href="http://www.spatialys.com"
moz-do-not-send="true">http://www.spatialys.com</a>
My software is free, but my time generally not.</pre>
</blockquote>
<br>
<div id="grammalecte_menu_main_button_shadow_host"
style="width: 0px; height: 0px;"></div>
</body>
</html>