Opened 2 years ago

Closed 2 years ago

#5073 closed defect (fixed)

Localized docs are broken structurally

Reported by: strk Owned by: robe
Priority: medium Milestone: PostGIS 3.3.0
Component: l18n Version: master
Keywords: Cc:

Description (last modified by strk)

Running make -C doc check-localized shows many errors in multiple languages.

Example:

make[2]: Entering directory '/home/src/postgis/postgis/doc/po/pt_BR'
/usr/bin/perl -lpe "s'@@LAST_RELEASE_VERSION@@'3.3.0dev'g;s'@@POSTGIS_DOWNLOAD_URL@@'http://postgis.net/stuff'g;" postgis.xml > postgis-out.xml
/usr/bin/xsltproc --novalid --path . xsl/postgis_aggs_mm.xml.xsl postgis-out.xml > postgis_aggs_mm.xml
/usr/bin/xmllint --loaddtd --path . --xinclude --valid postgis-out.xml > /dev/null
reference_management.xml:557: element funcprototype: validity error : Element funcprototype content does not follow the DTD, expecting (modifier* , funcdef , (void | varargs | (paramdef+ , varargs?)) , modifier*), got (funcprototype funcprototype )
> </funcprototype>
                  ^

Change History (7)

comment:1 by strk, 2 years ago

Description: modified (diff)

comment:2 by strk, 2 years ago

[d137d9d6b97258024b7a4f8f27ba7de7b589bf3e/git] fixed many structural issues in pt_BR translation. A lot more are due to IDREF attribute linkend references an unknown ID which are due to id strings not translated (should be copied verbatim). Not sure how to automate this, unless weblate allows automatically translating things that are in the Glossary, and we add all the ST_ function names and identifiers in the glossary

comment:3 by strk, 2 years ago

The IDREF attribute linkend references an unknown ID issue is already reported as #5059

comment:4 by Sandro Santilli <strk@…>, 2 years ago

In 8e829f9f/git:

Fix structural issues in es translations

References #5073

comment:5 by Sandro Santilli <strk@…>, 2 years ago

In 4db89f2/git:

Some verbatim translations

Fix japanese translation structure

References #5073

comment:6 by strk, 2 years ago

I found many translations having different tagset than source strings, in particular <para> tags being in the translation but NOT in the original string. I suspect these are inserted due to fuzzy-matching which we may want to disable to avoid these occurrences.

comment:7 by Sandro Santilli <strk@…>, 2 years ago

Resolution: fixed
Status: newclosed

In a9645b9/git:

Fix invalid translation in pt_BR

Closes #5073
Closes #5059

Note: See TracTickets for help on using tickets.