Report import POSyntaxWarnings to uploader
Bug #148425 reported by
Jeroen T. Vermeulen
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
High
|
Jeroen T. Vermeulen |
Bug Description
The PO parser can issue warnings about minor problems in translation files (see bug 1773 for an example). These warnings are currently logged, which is a nuisance to administrators (see bug 35430), but not reported back to the uploader.
The main source of pointless email to error-reports is "PO file header entry has a bad entry." Just getting rid of that log message would spare us a lot of noise on error-reports.
We should add a mechanism for parsers to return warnings to their callers, and check for and include any warnings in confirmation and error emails. This should replace the logging.
Changed in rosetta: | |
importance: | Undecided → High |
status: | New → Confirmed |
Changed in rosetta: | |
status: | Confirmed → Triaged |
summary: |
- Report import warnings to uploader + Report import POSyntaxWarnings to uploader |
description: | updated |
description: | updated |
tags: | added: rosetta-imports |
Changed in rosetta: | |
assignee: | nobody → Jeroen T. Vermeulen (jtv) |
milestone: | none → 2.2.7 |
status: | Triaged → In Progress |
Changed in rosetta: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
The same goes for actual syntax errors. A TranslationForm atSyntaxError results in a generic message referring the uploader to msgfmt. Not all syntax problems can be detected that way, e.g. http:// launchpadlibrar ian.net/ 11577117/ eYWndZBCUT3646o 1PW63ZEKi0OO. txt