Opened 6 months ago

Last modified 3 months ago

#32650 new defect

Check translations for bogus characters

Reported by: gk Owned by: emmapeel
Priority: Medium Milestone:
Component: Community/Translations Version:
Severity: Normal Keywords:
Cc: sysrqb, ggus, tbb-team Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description (last modified by gk)

This ticket is a cousin of #30054. We need some script that checks translations for bogus characters *before* they get merged to our translations repository. Not doing so risks that entire bundles are non-functional up to the point that not even updates to newer versions work anymore (see: #31886 for such a case, although the update still seemed to work I think). We should check for escaping issues like #31929 as well. Any maybe more.

Child Tickets

Change History (5)

comment:1 Changed 6 months ago by gk

Description: modified (diff)

comment:2 Changed 6 months ago by emmapeel

maybe it could use i18nspector like in tails:

https://git-tails.immerda.ch/jenkins-tools/tree/slaves/lint_po

comment:3 Changed 4 months ago by emmapeel

i need help for this

comment:4 Changed 4 months ago by pili

Cc: tbb-team added

comment:5 in reply to:  2 Changed 3 months ago by boklm

Replying to emmapeel:

maybe it could use i18nspector like in tails:

https://git-tails.immerda.ch/jenkins-tools/tree/slaves/lint_po

It seems this script is only for checking po file. But the issue with #31886 and #31929 was in dtd files.

In the script to import translations, maybe we can try to parse the dtd files before we commit them?

Maybe dtdinst is a tool we can use for that: XML DTD to XML instance format converter
https://packages.debian.org/buster/dtdinst

Note: See TracTickets for help on using tickets.