@crossbind/port-proj-wasm 2.0.0-beta.56 → 2.0.0-beta.60

package/dist/prebuilt/wasm-wasm32-mt-release/share/man/man1/cs2cs.1

@@ -1,5 +1,4 @@
-.\" Man page generated from reStructuredText
-.\" by the Docutils 0.22.4 manpage writer.
+.\" Man page generated from reStructuredText.
 .
 .
 .nr rst2man-indent-level 0
@@ -28,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]]
 .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]]
 .in \\n[rst2man-indent\\n[rst2man-indent-level]]u
 ..
-.TH "CS2CS" "1" "10 avril 2026" "9.8" "PROJ"
+.TH "CS2CS" "1" "15 Sep 2026" "9.9" "PROJ"
 .SH NAME
 cs2cs \- Cartographic coordinate system filter
 .SH SYNOPSIS
@@ -48,7 +47,7 @@ file ...
 .sp
 .sp
 where {source_crs} or {target_crs} is one of the possibilities accepted
-by \fBproj_create()\fP \%<#\:c\:.proj_create>, provided it expresses a CRS
+by \fI\%proj_create()\fP, provided it expresses a CRS
 .INDENT 0.0
 .IP \(bu 2
 a proj\-string,
@@ -61,21 +60,21 @@ an object code (like \(dqEPSG:4326\(dq, \(dqurn:ogc:def:crs:EPSG::4326\(dq,
 an Object name. e.g \(dqWGS 84\(dq, \(dqWGS 84 / UTM zone 31N\(dq. In that case as
 uniqueness is not guaranteed, heuristics are applied to determine the appropriate best match.
 .IP \(bu 2
-a CRS name and a coordinate epoch, separated with \(aq@\(aq. For example \(dq\%<ITRF2014@\:2025.0>\(dq. (\fIadded in 9.2\fP)
+a CRS name and a coordinate epoch, separated with \(aq@\(aq. For example \(dq\X'tty: link mailto:ITRF2014@2025.0'\fI\%ITRF2014@2025.0\fP\X'tty: link'\(dq. (\fIadded in 9.2\fP)
 .IP \(bu 2
 a OGC URN combining references for compound coordinate reference systems
-(e.g \(dq\%<urn:ogc:def:crs,crs:EPSG::2393,crs:EPSG::5717>\(dq or custom abbreviated
+(e.g \(dq\fI\%urn:ogc:def:crs,crs:EPSG::2393,crs:EPSG::5717\fP\(dq or custom abbreviated
 syntax \(dqEPSG:2393+5717\(dq),
 .IP \(bu 2
 a OGC URN combining references for references for projected or derived CRSs
 e.g. for Projected 3D CRS \(dqUTM zone 31N / WGS 84 (3D)\(dq:
-\(dq\%<urn:ogc:def:crs,crs:EPSG::4979,cs:PROJ::ENh,coordinateOperation:EPSG::16031>\(dq
+\(dq\fI\%urn:ogc:def:crs,crs:EPSG::4979,cs:PROJ::ENh,coordinateOperation:EPSG::16031\fP\(dq
 (\fIadded in 6.2\fP)
 .IP \(bu 2
 a OGC URN combining references for concatenated operations
-(e.g. \(dq\%<urn:ogc:def:coordinateOperation,coordinateOperation:EPSG::3895,coordinateOperation:EPSG::1618>\(dq)
+(e.g. \(dq\fI\%urn:ogc:def:coordinateOperation,coordinateOperation:EPSG::3895,coordinateOperation:EPSG::1618\fP\(dq)
 .IP \(bu 2
-a PROJJSON string. The jsonschema is at \%<https://\:proj\:.org/\:schemas/\:v0\:.4/\:projjson\:.schema\:.json> (\fIadded in 6.2\fP)
+a PROJJSON string. The jsonschema is at \X'tty: link https://proj.org/schemas/v0.4/projjson.schema.json'\fI\%https://proj.org/schemas/v0.4/projjson.schema.json\fP\X'tty: link' (\fIadded in 6.2\fP)
 .IP \(bu 2
 a compound CRS made from two object names separated with \(dq + \(dq. e.g. \(dqWGS 84 + EGM96 height\(dq (\fIadded in 7.1\fP)
 .UNINDENT
@@ -83,7 +82,7 @@ a compound CRS made from two object names separated with \(dq + \(dq. e.g. \(dqW
 Added in version 6.0.0.
 
 .sp
-\fBNote:\fP
+\fBNOTE:\fP
 .INDENT 0.0
 .INDENT 3.5
 before 7.0.1, it was needed to add +to between {source_crs} and {target_crs}
@@ -94,7 +93,7 @@ when adding a filename
 .UNINDENT
 .SH DESCRIPTION
 .sp
-cs2cs performs transformation between the source and destination
+\fI\%cs2cs\fP performs transformation between the source and destination
 cartographic coordinate reference system on a set of input points. The coordinate
 reference system transformation can include translation between projected and
 geographic coordinates as well as the application of datum shifts.
@@ -221,7 +220,7 @@ Specify an area of interest to restrict the results when researching
 coordinate operations between 2 CRS. The area of interest can be specified either
 as a name (e.g \(dqDenmark \- onshore\(dq) or a AUTHORITY:CODE (EPSG:3237)
 .sp
-This option is mutually exclusive with \fB\-\-bbox\fP\&.
+This option is mutually exclusive with \fI\%\-\-bbox\fP\&.
 .UNINDENT
 .INDENT 0.0
 .TP
@@ -253,7 +252,7 @@ or through network).
 .sp
 Note that the default value for this option can be also set with the
 \fBPROJ_ONLY_BEST_DEFAULT\fP environment variable, or with the
-\fBonly_best_default\fP setting of proj.ini \%<#\:proj-ini> (\fB\-\-only\-best\fP
+\fBonly_best_default\fP setting of \fI\%proj.ini\fP (\fI\%\-\-only\-best\fP
 when specified overrides such default value).
 .UNINDENT
 .INDENT 0.0
@@ -263,7 +262,7 @@ Added in version 8.0.0.
 
 .sp
 Disallow any coordinate operation that is, or contains, a
-Ballpark transformation \%<#\:term-Ballpark-transformation>
+\fI\%Ballpark transformation\fP
 .UNINDENT
 .INDENT 0.0
 .TP
@@ -288,7 +287,7 @@ If authority is set to \fBany\fP, then coordinate operations from any authority
 If authority is a non\-empty string different of \fBany\fP, then coordinate operations
 will be searched only in that authority namespace (e.g \fBEPSG\fP).
 .sp
-This option is mutually exclusive with \fB\-\-bbox\fP\&.
+This option is mutually exclusive with \fI\%\-\-bbox\fP\&.
 .UNINDENT
 .INDENT 0.0
 .TP
@@ -325,7 +324,7 @@ Only applies to a dynamic CRS.
 The \fI+opt\fP run\-line arguments are associated with cartographic
 parameters.
 .sp
-The cs2cs program takes two coordinate reference system (CRS) definitions.
+The \fI\%cs2cs\fP program takes two coordinate reference system (CRS) definitions.
 These can be given in a variety of formats such as EPSG\-codes, WKT\-strings or legacy PROJ.4
 CRS descriptions.
 .sp
@@ -338,11 +337,11 @@ When using a WKT definition or a AUTHORITY:CODE, the axis order of the CRS will
 be enforced. So for example if using EPSG:4326, the first value expected (or
 returned) will be a latitude.
 .sp
-Internally, cs2cs uses the \fBproj_create_crs_to_crs()\fP \%<#\:c\:.proj_create_crs_to_crs> function
+Internally, \fI\%cs2cs\fP uses the \fI\%proj_create_crs_to_crs()\fP function
 to compute the appropriate coordinate operation, so implementation details of
 this function directly impact the results returned by the program.
 .sp
-The environment parameter \fBPROJ_DATA\fP \%<#\:envvar-PROJ_DATA> establishes the
+The environment parameter \fI\%PROJ_DATA\fP establishes the
 directory for resource files (database, datum shift grids, etc.)
 .sp
 One or more files (processed in left to right order) specify the source of
@@ -363,11 +362,11 @@ places), while projected (cartesian) coordinates will be in linear
 Added in version 7.0.0.
 
 .sp
-If the \fBPROJ_NETWORK\fP \%<#\:envvar-PROJ_NETWORK> environment variable is set to \fBON\fP,
-cs2cs will attempt to use remote grids stored on CDN (Content
+If the \fI\%PROJ_NETWORK\fP environment variable is set to \fBON\fP,
+\fI\%cs2cs\fP will attempt to use remote grids stored on CDN (Content
 Delivery Network) storage, when they are not available locally.
 .sp
-More details are available in the Network capabilities \%<#\:network> section.
+More details are available in the \fI\%Network capabilities\fP section.
 .SH EXAMPLES
 .SS Using EPSG CRS codes
 .sp
@@ -415,7 +414,7 @@ outputs
 .UNINDENT
 .UNINDENT
 .sp
-\fBNote:\fP
+\fBNOTE:\fP
 .INDENT 0.0
 .INDENT 3.5
 To get those exact values, you have need to have the EGM96 grid installed
@@ -455,7 +454,7 @@ To get those exact values, you have need to have all current grids installed
 (in that instance the NADCON5 \fBus_noaa_nadcon5_nad27_nad83_1986_conus.tif\fP grid)
 locally or use networking capabilities mentioned above.
 .sp
-To make sure you will get the optimal result, you may add \fB\-\-only\-best\fP\&.
+To make sure you will get the optimal result, you may add \fI\%\-\-only\-best\fP\&.
 Assuming the above mentioned grid is \fInot\fP available,
 .INDENT 0.0
 .INDENT 3.5
@@ -477,7 +476,7 @@ Attempt to use coordinate operation axis order change (2D) + Inverse of NAD27 to
 .UNINDENT
 .UNINDENT
 .sp
-Otherwise, if you don\(aqt have the grid available and you don\(aqt specify \fB\-\-only\-best\fP:
+Otherwise, if you don\(aqt have the grid available and you don\(aqt specify \fI\%\-\-only\-best\fP:
 .INDENT 0.0
 .INDENT 3.5
 .sp
@@ -504,13 +503,14 @@ which is an approximation at a level of several tens of metres.
 \fBproj(1)\fP, \fBcct(1)\fP, \fBgeod(1)\fP, \fBgie(1)\fP, \fBprojinfo(1)\fP, \fBprojsync(1)\fP
 .SH BUGS
 .sp
-A list of known bugs can be found at \%<https://\:github\:.com/\:OSGeo/\:PROJ/\:issues>
+A list of known bugs can be found at \X'tty: link https://github.com/OSGeo/PROJ/issues'\fI\%https://github.com/OSGeo/PROJ/issues\fP\X'tty: link'
 where new bug reports can be submitted to.
 .SH HOME PAGE
 .sp
-\%<https://\:proj\:.org/>
-.SH Author
+\X'tty: link https://proj.org/'\fI\%https://proj.org/\fP\X'tty: link'
+.SH AUTHOR
 Frank Warmerdam
-.SH Copyright
+.SH COPYRIGHT
 1983-2026, PROJ contributors
-.\" End of generated man page.
+.\" Generated by docutils manpage writer.
+.

package/dist/prebuilt/wasm-wasm32-mt-release/share/man/man1/geod.1

@@ -1,5 +1,4 @@
-.\" Man page generated from reStructuredText
-.\" by the Docutils 0.22.4 manpage writer.
+.\" Man page generated from reStructuredText.
 .
 .
 .nr rst2man-indent-level 0
@@ -28,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]]
 .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]]
 .in \\n[rst2man-indent\\n[rst2man-indent-level]]u
 ..
-.TH "GEOD" "1" "10 avril 2026" "9.8" "PROJ"
+.TH "GEOD" "1" "15 Sep 2026" "9.9" "PROJ"
 .SH NAME
 geod \- Geodesic computations
 .SH SYNOPSIS
@@ -41,7 +40,7 @@ geod \- Geodesic computations
 .UNINDENT
 .SH DESCRIPTION
 .sp
-geod (direct) and invgeod (inverse) perform geodesic
+\fI\%geod\fP (direct) and \fI\%invgeod\fP (inverse) perform geodesic
 (Great Circle) computations for determining latitude, longitude and back
 azimuth of a terminus point given a initial point latitude, longitude,
 azimuth and distance (direct) or the forward and back azimuths and distance
@@ -49,15 +48,15 @@ between an initial and terminus point latitudes and longitudes (inverse).
 The results are accurate to round off for |f| < 1/50, where
 f is flattening.
 .sp
-invgeod may not be available on all platforms; in this case
-use \fBgeod \-I\fP instead.
+\fI\%invgeod\fP may not be available on all platforms; in this case
+use \fI\%geod \-I\fP instead.
 .sp
 The following command\-line options can appear in any order:
 .INDENT 0.0
 .TP
 .B \-I
 Specifies that the inverse geodesic computation is to be performed. May be
-used with execution of geod as an alternative to invgeod execution.
+used with execution of \fI\%geod\fP as an alternative to \fI\%invgeod\fP execution.
 .UNINDENT
 .INDENT 0.0
 .TP
@@ -112,7 +111,7 @@ with leading zeroes.
 .TP
 .B \-p
 This option causes the azimuthal values to be output as unsigned DMS
-numbers between 0 and 360 degrees. Also note \fB\-f\fP\&.
+numbers between 0 and 360 degrees. Also note \fI\%\-f\fP\&.
 .UNINDENT
 .sp
 The \fI+opt\fP command\-line options are associated with geodetic
@@ -142,15 +141,15 @@ azimuthal data must be in decimal degrees or DMS format and
 input distance data must be in units consistent with the ellipsoid
 major axis or sphere radius units. The latitude must lie
 in the range [\-90d,90d]. Output geographic coordinates and azimuths will be
-in DMS (if the \fB\-f\fP switch is not employed) to 0.001\(dq with trailing,
+in DMS (if the \fI\%\-f\fP switch is not employed) to 0.001\(dq with trailing,
 zero\-valued minute\-second fields deleted. Output distance
 data will be in the same units as the ellipsoid or sphere
 radius.
 .sp
 The Earth\(aqs ellipsoidal figure may be selected in the same manner
-as program proj \%<#\:proj> by using \fI+ellps=\fP, \fI+a=\fP, \fI+es=\fP, etc.
+as program \fI\%proj\fP by using \fI+ellps=\fP, \fI+a=\fP, \fI+es=\fP, etc.
 .sp
-geod may also be used to determine intermediate points along
+\fI\%geod\fP may also be used to determine intermediate points along
 either a geodesic line between two points or along an arc of
 specified distance from a geographic point. In both cases an
 initial point must be specified with \fI+lat_1=lat\fP and \fI+lon_1=long\fP
@@ -221,7 +220,7 @@ which gives:
 i.e., the latitude and longitude of Portland, and the
 back azimuth from Portland to Boston.
 .sp
-\fBNote:\fP
+\fBNOTE:\fP
 .INDENT 0.0
 .INDENT 3.5
 Lack of precision in the distance value compromises the
@@ -231,25 +230,26 @@ precision of the Portland location.
 .SH FURTHER READING
 .INDENT 0.0
 .IP 1. 3
-GeographicLib \%<https://\:geographiclib\:.sourceforge\:.io>\&.
+\X'tty: link https://geographiclib.sourceforge.io'\fI\%GeographicLib\fP\X'tty: link'\&.
 .IP 2. 3
-C. F. F. Karney, Algorithms for Geodesics \%<https://\:doi\:.org/\:10\:.1007/\:s00190-012-0578-z>, J. Geodesy \fB87\fP(1), 43–55 (2013);
-addenda \%<https://\:geographiclib\:.sourceforge\:.io/\:geod-addenda\:.html>\&.
+C. F. F. Karney, \X'tty: link https://doi.org/10.1007/s00190-012-0578-z'\fI\%Algorithms for Geodesics\fP\X'tty: link', J. Geodesy \fB87\fP(1), 43–55 (2013);
+\X'tty: link https://geographiclib.sourceforge.io/geod-addenda.html'\fI\%addenda\fP\X'tty: link'\&.
 .IP 3. 3
-A geodesic bibliography \%<https://\:geographiclib\:.sourceforge\:.io/\:geodesic-papers/\:biblio\:.html>\&.
+\X'tty: link https://geographiclib.sourceforge.io/geodesic-papers/biblio.html'\fI\%A geodesic bibliography\fP\X'tty: link'\&.
 .UNINDENT
 .SH SEE ALSO
 .sp
 \fBproj(1)\fP, \fBcs2cs(1)\fP, \fBcct(1)\fP, \fBgie(1)\fP, \fBprojinfo(1)\fP, \fBprojsync(1)\fP
 .SH BUGS
 .sp
-A list of known bugs can be found at \%<https://\:github\:.com/\:OSGeo/\:PROJ/\:issues>
+A list of known bugs can be found at \X'tty: link https://github.com/OSGeo/PROJ/issues'\fI\%https://github.com/OSGeo/PROJ/issues\fP\X'tty: link'
 where new bug reports can be submitted to.
 .SH HOME PAGE
 .sp
-\%<https://\:proj\:.org/>
-.SH Author
+\X'tty: link https://proj.org/'\fI\%https://proj.org/\fP\X'tty: link'
+.SH AUTHOR
 Charles Karney
-.SH Copyright
+.SH COPYRIGHT
 1983-2026, PROJ contributors
-.\" End of generated man page.
+.\" Generated by docutils manpage writer.
+.

package/dist/prebuilt/wasm-wasm32-mt-release/share/man/man1/gie.1

@@ -1,5 +1,4 @@
-.\" Man page generated from reStructuredText
-.\" by the Docutils 0.22.4 manpage writer.
+.\" Man page generated from reStructuredText.
 .
 .
 .nr rst2man-indent-level 0
@@ -28,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]]
 .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]]
 .in \\n[rst2man-indent\\n[rst2man-indent-level]]u
 ..
-.TH "GIE" "1" "10 avril 2026" "9.8" "PROJ"
+.TH "GIE" "1" "15 Sep 2026" "9.9" "PROJ"
 .SH NAME
 gie \- The Geospatial Integrity Investigation Environment
 .SH SYNOPSIS
@@ -39,7 +38,7 @@ gie \- The Geospatial Integrity Investigation Environment
 .UNINDENT
 .SH DESCRIPTION
 .sp
-gie, the Geospatial Integrity Investigation Environment, is a
+\fI\%gie\fP, the Geospatial Integrity Investigation Environment, is a
 regression testing environment for the PROJ transformation library. Its primary
 design goal is to be able to perform regression testing of code that are a part
 of PROJ, while not requiring any other kind of tooling than the same C compiler
@@ -57,7 +56,7 @@ Specify output file name
 .INDENT 0.0
 .TP
 .B \-v, \-\-verbose
-Verbose: Provide non\-essential informational output. Repeat \fB\-v\fP for
+Verbose: Provide non\-essential informational output. Repeat \fI\%\-v\fP for
 more verbosity (e.g. \fB\-vv\fP)
 .UNINDENT
 .INDENT 0.0
@@ -78,14 +77,14 @@ List the PROJ internal system error codes
 Print version number
 .UNINDENT
 .sp
-Tests for gie are defined in simple text files. Usually having the
-extension \fB\&.gie\fP\&. Test for gie are written in the purpose\-build command language for gie.
+Tests for \fI\%gie\fP are defined in simple text files. Usually having the
+extension \fB\&.gie\fP\&. Test for \fI\%gie\fP are written in the purpose\-build command language for gie.
 The basic functionality of the gie command language is implemented through just
 3 command verbs: \fBoperation\fP, which defines the PROJ operation to test,
 \fBaccept\fP, which defines the input coordinate to read, and \fBexpect\fP, which
 defines the result to expect.
 .sp
-A sample test file for gie that uses the three above basic commands looks
+A sample test file for \fI\%gie\fP that uses the three above basic commands looks
 like:
 .INDENT 0.0
 .INDENT 3.5
@@ -106,26 +105,26 @@ expect     691_875.632_14   6_098_907.825_05
 .UNINDENT
 .UNINDENT
 .sp
-Parsing of a gie file starts at \fB<gie>\fP and ends when \fB</gie>\fP
+Parsing of a \fI\%gie\fP file starts at \fB<gie>\fP and ends when \fB</gie>\fP
 is reached. Anything before \fB<gie>\fP and after \fB</gie>\fP is not considered.
-Test cases are created by defining an \fBoperation\fP which
-\fBaccept\fP an input coordinate and \fBexpect\fP an output
+Test cases are created by defining an \fI\%operation\fP which
+\fI\%accept\fP an input coordinate and \fI\%expect\fP an output
 coordinate.
 .sp
-Because gie tests are wrapped in the \fB<gie>\fP/\fB</gie>\fP tags it is
-also possible to add test cases to custom made init files \%<#\:init-files>\&.
+Because \fI\%gie\fP tests are wrapped in the \fB<gie>\fP/\fB</gie>\fP tags it is
+also possible to add test cases to custom made \fI\%init files\fP\&.
 The tests will be ignore by PROJ when reading the init file with \fI+init\fP and
-gie ignores anything not wrapped in \fB<gie>\fP/\fB</gie>\fP\&.
+\fI\%gie\fP ignores anything not wrapped in \fB<gie>\fP/\fB</gie>\fP\&.
 .sp
-gie tests are defined by a set of commands like \fBoperation\fP,
-\fBaccept\fP and \fBexpect\fP in the example above. Together the
-commands make out the gie command language. Any line in a
-gie file that does not start with a command is ignored. In the
+\fI\%gie\fP tests are defined by a set of commands like \fI\%operation\fP,
+\fI\%accept\fP and \fI\%expect\fP in the example above. Together the
+commands make out the \fI\%gie\fP command language. Any line in a
+\fI\%gie\fP file that does not start with a command is ignored. In the
 example above it is seen how this can be used to add comments and styling to
-gie test files in order to make them more readable as well as
+\fI\%gie\fP test files in order to make them more readable as well as
 documenting what the purpose of the various tests are.
 .sp
-Below the gie command language is explained in details.
+Below the \fI\%gie command language\fP is explained in details.
 .SH EXAMPLES
 .INDENT 0.0
 .IP 1. 3
@@ -180,26 +179,26 @@ can be defined by either 2, 3 or 4 values, where the first two values are
 the x\- and y\-components, the 3rd is the z\-component and the 4th is the time
 component. The number of components in the coordinate determines which
 version of the operation is tested (2D, 3D or 4D). Many coordinates can be
-accepted for one \fBoperation\fP\&. For each \fBaccept\fP an
-accompanying \fBexpect\fP is needed.
+accepted for one \fI\%operation\fP\&. For each \fI\%accept\fP an
+accompanying \fI\%expect\fP is needed.
 .sp
-Note that gie accepts the underscore (\fB_\fP) as a thousands
+Note that \fI\%gie\fP accepts the underscore (\fB_\fP) as a thousands
 separator. It is not required (in fact, it is entirely ignored by the
 input routine), but it significantly improves the readability of the very
 long strings of numbers typically required in projected coordinates.
 .sp
-See \fBoperation\fP for an example.
+See \fI\%operation\fP for an example.
 .UNINDENT
 .INDENT 0.0
 .TP
 .B expect <x y [z [t]]> | <error code>
 Define the expected coordinate that will be returned from accepted
 coordinate passed though an operation. The expected coordinate can be
-defined by either 2, 3 or 4 components, similarly to \fBaccept\fP\&.
-Many coordinates can be expected for one \fBoperation\fP\&. For each
-\fBexpect\fP an accompanying \fBaccept\fP is needed.
+defined by either 2, 3 or 4 components, similarly to \fI\%accept\fP\&.
+Many coordinates can be expected for one \fI\%operation\fP\&. For each
+\fI\%expect\fP an accompanying \fI\%accept\fP is needed.
 .sp
-See \fBoperation\fP for an example.
+See \fI\%operation\fP for an example.
 .sp
 In addition to expecting a coordinate it is also possible to expect a
 PROJ error code in case an operation can\(aqt be created. This is useful when
@@ -217,16 +216,16 @@ expect      failure pjd_err_malformed_pipeline
 .UNINDENT
 .UNINDENT
 .sp
-See \fBgie \-\-list\fP for a list of error codes that can be expected.
+See \fI\%gie \-\-list\fP for a list of error codes that can be expected.
 .UNINDENT
 .INDENT 0.0
 .TP
 .B tolerance <tolerance>
-The \fBtolerance\fP command controls how much accepted coordinates
+The \fI\%tolerance\fP command controls how much accepted coordinates
 can deviate from the expected coordinate. This is handy to test that an
 operation meets a certain numerical tolerance threshold. Some operations
 are expected to be accurate within millimeters where others might only be
-accurate within a few meters. \fBtolerance\fP should
+accurate within a few meters. \fI\%tolerance\fP should
 .INDENT 7.0
 .INDENT 3.5
 .sp
@@ -247,14 +246,14 @@ expect          1335883.89  7326837.72
 .UNINDENT
 .UNINDENT
 .sp
-The default tolerance is 0.5 mm. See \fBproj \-lu\fP \%<#\:cmdoption-proj-lu> for a list of possible
+The default tolerance is 0.5 mm. See \fI\%proj \-lu\fP for a list of possible
 units.
 .UNINDENT
 .INDENT 0.0
 .TP
 .B roundtrip <n> <tolerance>
-Do a roundtrip test of an operation. \fBroundtrip\fP needs a
-\fBoperation\fP and a \fBaccept\fP command
+Do a roundtrip test of an operation. \fI\%roundtrip\fP needs a
+\fI\%operation\fP and a \fI\%accept\fP command
 to function. The accepted coordinate is passed to the operation first in
 it\(aqs forward mode, then the output from the forward operation is passed
 back to the inverse operation. This procedure is done \fBn\fP times. If the
@@ -300,7 +299,7 @@ roundtrip       10000 5 mm
 .INDENT 0.0
 .TP
 .B direction <direction>
-The \fBdirection\fP command specifies in which direction an operation
+The \fI\%direction\fP command specifies in which direction an operation
 is performed. This can either be \fBforward\fP or \fBinverse\fP\&. An example of
 this is seen below where it is tested that a symmetrical transformation
 pipeline returns the same results in both directions.
@@ -345,15 +344,15 @@ expect    173                 \-45
 .UNINDENT
 .UNINDENT
 .sp
-See \fBgie \-\-list\fP for a list of error codes that can be ignored.
+See \fI\%gie \-\-list\fP for a list of error codes that can be ignored.
 .UNINDENT
 .INDENT 0.0
 .TP
 .B require_grid <grid_name>
 Checks the availability of the grid <grid_name>. If it is not found, then
-all \fBaccept\fP/\fBexpect\fP pairs until the next
-\fBoperation\fP will be skipped.
-\fBrequire_grid\fP can be repeated several times to specify several grids whose
+all \fI\%accept\fP/\fI\%expect\fP pairs until the next
+\fI\%operation\fP will be skipped.
+\fI\%require_grid\fP can be repeated several times to specify several grids whose
 presence is required.
 .UNINDENT
 .INDENT 0.0
@@ -392,7 +391,7 @@ total:  1 tests succeeded,  0 tests skipped,  0 tests failed.
 .INDENT 0.0
 .TP
 .B skip
-Skip any test after the first occurrence of \fBskip\fP\&. In the example below only
+Skip any test after the first occurrence of \fI\%skip\fP\&. In the example below only
 the first test will be performed. The second test is skipped. This feature is mostly
 relevant for debugging when writing new test cases.
 .INDENT 7.0
@@ -461,7 +460,7 @@ to use\fP, for a programmer, than the \fBsin()\fP\(aqs, \fBtan()\fP\(aqs and
 .sp
 Gerald\(aqs ingenuity also showed in the implementation of the vision, where
 he devised a comprehensive, yet simple, system of key\-value pairs for
-parameterising a map projection, and the highly flexible \fBPJ\fP \%<#\:c\:.PJ> struct, storing
+parameterising a map projection, and the highly flexible \fI\%PJ\fP struct, storing
 run\-time compiled versions of those key\-value pairs, hence making a map
 projection function call, \fBpj_fwd(PJ, point)\fP, as easy as a traditional function
 call like \fBhypot(x,y)\fP\&.
@@ -482,13 +481,14 @@ So in honour, and hopefully also in the spirit, of Gerald Ian Evenden
 \fBproj(1)\fP, \fBcs2cs(1)\fP, \fBcct(1)\fP, \fBgeod(1)\fP, \fBprojinfo(1)\fP, \fBprojsync(1)\fP
 .SH BUGS
 .sp
-A list of known bugs can be found at \%<https://\:github\:.com/\:OSGeo/\:PROJ/\:issues>
+A list of known bugs can be found at \X'tty: link https://github.com/OSGeo/PROJ/issues'\fI\%https://github.com/OSGeo/PROJ/issues\fP\X'tty: link'
 where new bug reports can be submitted to.
 .SH HOME PAGE
 .sp
-\%<https://\:proj\:.org/>
-.SH Author
+\X'tty: link https://proj.org/'\fI\%https://proj.org/\fP\X'tty: link'
+.SH AUTHOR
 Thomas Knudsen
-.SH Copyright
+.SH COPYRIGHT
 1983-2026, PROJ contributors
-.\" End of generated man page.
+.\" Generated by docutils manpage writer.
+.

package/dist/prebuilt/wasm-wasm32-mt-release/share/man/man1/proj.1

@@ -1,5 +1,4 @@
-.\" Man page generated from reStructuredText
-.\" by the Docutils 0.22.4 manpage writer.
+.\" Man page generated from reStructuredText.
 .
 .
 .nr rst2man-indent-level 0
@@ -28,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]]
 .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]]
 .in \\n[rst2man-indent\\n[rst2man-indent-level]]u
 ..
-.TH "PROJ" "1" "10 avril 2026" "9.8" "PROJ"
+.TH "PROJ" "1" "15 Sep 2026" "9.9" "PROJ"
 .SH NAME
 proj \- Cartographic projection filter
 .SH SYNOPSIS
@@ -41,12 +40,12 @@ proj \- Cartographic projection filter
 .UNINDENT
 .SH DESCRIPTION
 .sp
-proj and invproj perform respective forward and inverse
+\fI\%proj\fP and \fI\%invproj\fP perform respective forward and inverse
 conversion of cartographic data to or from cartesian data with a wide
 range of selectable projection functions.
 .sp
-invproj may not be available on all platforms; in this case
-use \fBproj \-I\fP instead.
+\fI\%invproj\fP may not be available on all platforms; in this case
+use \fI\%proj \-I\fP instead.
 .sp
 The following control parameters can appear in any order
 .INDENT 0.0
@@ -54,7 +53,7 @@ The following control parameters can appear in any order
 .B \-b
 Special option for binary coordinate data input and output through standard
 input and standard output. Data is assumed to be in system type double
-floating point words. This option is to be used when proj is a child process
+floating point words. This option is to be used when \fI\%proj\fP is a child process
 and allows bypassing formatting operations.
 .UNINDENT
 .INDENT 0.0
@@ -67,18 +66,18 @@ Added in version 5.2.0: Specify the number of decimals to round to in the output
 .INDENT 0.0
 .TP
 .B \-i
-Selects binary input only (see \fB\-b\fP).
+Selects binary input only (see \fI\%\-b\fP).
 .UNINDENT
 .INDENT 0.0
 .TP
 .B \-I
 Alternate method to specify inverse projection. Redundant when used with
-invproj\&.
+\fI\%invproj\fP\&.
 .UNINDENT
 .INDENT 0.0
 .TP
 .B \-o
-Selects binary output only (see \fB\-b\fP).
+Selects binary output only (see \fI\%\-b\fP).
 .UNINDENT
 .INDENT 0.0
 .TP
@@ -92,7 +91,7 @@ applicable to ASCII input only. (# is the default value).
 .B \-e <string>
 Where \fIstring\fP is an arbitrary string to be output if an error is detected during
 data transformations. The default value is a three character string: \fB*\et*\fP\&.
-Note that if the \fB\-b\fP, \fB\-i\fP or \fB\-o\fP options are employed, an error
+Note that if the \fI\%\-b\fP, \fI\%\-i\fP or \fI\%\-o\fP options are employed, an error
 is returned as HUGE_VAL value for both return values.
 .UNINDENT
 .INDENT 0.0
@@ -190,7 +189,7 @@ the program to be printed prior to input data.
 .TP
 .B \-V
 This option causes an expanded annotated listing of the characteristics of
-the projected point. \fB\-v\fP is implied with this option.
+the projected point. \fI\%\-v\fP is implied with this option.
 .UNINDENT
 .sp
 The \fI+opt\fP run\-line arguments are associated with cartographic parameters.
@@ -198,7 +197,7 @@ Additional projection control parameters may be contained in two auxiliary
 control files: the first is optionally referenced with the
 \fI+init=file:id\fP and the second is always processed after the name of the
 projection has been established from either the run\-line or the contents of
-+init file. The environment parameter \fBPROJ_DATA\fP \%<#\:envvar-PROJ_DATA> establishes the
++init file. The environment parameter \fI\%PROJ_DATA\fP establishes the
 default directory for a file reference without an absolute path. This is
 also used for supporting files like datum shift files.
 .sp
@@ -295,10 +294,10 @@ Max\-min (Tissot axis a\-b) scale error: 1.00004 1.00004
 .UNINDENT
 .SH OTHER PROGRAMS
 .sp
-The proj program is limited to converting between geographic and
+The \fI\%proj\fP program is limited to converting between geographic and
 projected coordinates within one datum.
 .sp
-The cs2cs \%<#\:cs2cs> program operates similarly, but allows translation
+The \fI\%cs2cs\fP program operates similarly, but allows translation
 between any pair of definable coordinate reference systems, including
 support for datum translation.
 .SH SEE ALSO
@@ -306,13 +305,14 @@ support for datum translation.
 \fBcs2cs(1)\fP, \fBcct(1)\fP, \fBgeod(1)\fP, \fBgie(1)\fP, \fBprojinfo(1)\fP, \fBprojsync(1)\fP
 .SH BUGS
 .sp
-A list of known bugs can be found at \%<https://\:github\:.com/\:OSGeo/\:PROJ/\:issues>
+A list of known bugs can be found at \X'tty: link https://github.com/OSGeo/PROJ/issues'\fI\%https://github.com/OSGeo/PROJ/issues\fP\X'tty: link'
 where new bug reports can be submitted to.
 .SH HOME PAGE
 .sp
-\%<https://\:proj\:.org/>
-.SH Author
+\X'tty: link https://proj.org/'\fI\%https://proj.org/\fP\X'tty: link'
+.SH AUTHOR
 Gerald I. Evenden
-.SH Copyright
+.SH COPYRIGHT
 1983-2026, PROJ contributors
-.\" End of generated man page.
+.\" Generated by docutils manpage writer.
+.