typo fixes

frmts/hdf5/hdf5eosparser.cpp

@@ -244,7 +244,7 @@ void HDF5EOSParser::ParseGridStructure(const CPLJSONObject &oGridStructure)
             const int nYDim = oGrid.GetInteger("YDim", 0);
             if (poGridMetadata->aoDimensions.empty() && nXDim > 0 && nYDim > 0)
             {
-                // Check that all data fiels have a DimList=(YDim,XDim)
+                // Check that all data fields have a DimList=(YDim,XDim)
                 // property. This may be unneeded, but at least if we meet
                 // this condition, that should be a strong hint that the first
                 // dimension is Y, and the second X.

scripts/typos_allowlist.txt

@@ -312,6 +312,7 @@ either 2 or 4 comma separated values. The same rules apply for the source and de
 #define szMMNomCampNPoligonsDefecte "N_POLIG"
 #define MM_MIN_WIDTH_LONG 14  // For LONG_ARC and PERIMETRE
 #define MM_MIN_WIDTH_AREA 19  // For LONG_ARC and PERIMETRE
+    // of decimals to be used in the reserved fields as LONG_ARC, PERIMETRE,
     CPLStrlcpy(szPerimeterOfThePolygonCat, "Perimetre del poligon",
     CPLStrlcpy(szPerimeterOfThePolygonCat, "Perimetre del poligon",
     CPLStrlcpy(szAreaOfThePolygonCat, "Area del poligon",
@@ -328,6 +329,8 @@ either 2 or 4 comma separated values. The same rules apply for the source and de
     assert f.GetField("PERIMETRE") == pytest.approx(1289.866489495, abs=1e-5)
     assert f.GetField("PERIMETRE") == pytest.approx(1123.514024, abs=1e-5)
     assert f.GetField("PERIMETRE") == pytest.approx(680.544697, abs=1e-5)
-    assert f["PERIMETRE"] == [3.414213562, 3.414213562]
+    assert f["PERIMETRE"] == [3.414, 3.414]
     assert f["PERIMETRE"] == [32, 32]
 # Package substitutefont no longer exists since TeXLive 2023 later than August 2023
+        .GetFieldDefn(lyr.GetLayerDefn().GetFieldIndex("LOGICALY"))
+    assert f.GetField("LOGICALY") == 1