Opened 18 months ago
Closed 18 months ago
#5412 closed defect (fixed)
Manual support tags not being translated
Reported by: | strk | Owned by: | robe |
---|---|---|---|
Priority: | medium | Milestone: | PostGIS 3.4.0 |
Component: | l18n | Version: | master |
Keywords: | Cc: |
Description
The text of "compliant" tags found in postgis.xml is not being translated. There's no trace of the text in the po/templates/postgis.xml.pot so no opportunity for translating it.
See also #5055
Change History (5)
comment:1 by , 18 months ago
comment:2 by , 18 months ago
I've given the external .xml idea a try. In order to work it requires wrapping the entity into a <para> which in turns forces a new paragraph breaking the SQL-1.1 information integration in some functions, for example the SQLMM-3 7.2.4
specification you find in https://postgis.net/docs/manual-dev/ST_NumPoints.html
comment:3 by , 18 months ago
The reason for things breaking is this kind of usage in xml files:
<para>&sqlmm_compliant; SQL-MM: Topo-Geo and Topo-Net 3: Routine Details: X.3.12</para>
comment:4 by , 18 months ago
I've found that using a <remark> tag makes xml2pot capable of extracting the string to be translated. It makes the html slightly different (adds an <em> tag) but is acceptable to me. See https://git.osgeo.org/gitea/postgis/postgis/pulls/128
Regina: tests with that branch are welcome
I guess by using tag_*.xml files we would solve this