Opened 2 years ago
Closed 2 years ago
#5059 closed defect (fixed)
Error: no ID for constraint linkend
| Reported by: | strk | Owned by: | robe |
|---|---|---|---|
| Priority: | medium | Milestone: | PostGIS 3.3.0 |
| Component: | l18n | Version: | master |
| Keywords: | Cc: |
Description
Some translations end up with errors about XREF being somehow broken. The error is printed on screen but does not result in xsltproc returning witn an error code.
Affected translations are: de, ja, ko_KR, pt_BR These translation are fine: es, fr, it_IT, pl, ru
Change History (4)
comment:1 by , 2 years ago
| Milestone: | → PostGIS 3.3.0 |
|---|---|
| Version: | → master |
comment:2 by , 2 years ago
comment:3 by , 2 years ago
These issues are due to obsoleted translations. I wonder if we should NEVER keep obsoleted translations (ie: —no-fuzzy-matching switch of msgmerge, both in our Makefile and in Weblate). It would be the safest choice. What's your take on it Regina ?
Note:
See TracTickets
for help on using tickets.
I've fixed it_IT and es You can read more here: https://dronie.osgeo.org/postgis/postgis/2643/1/7
Still broken: de,fr,ja,ko_KR,pt_BR (I'll skip testing them for now with dronie)