| 2007-10-03 07:15:57 |
Jeroen T. Vermeulen |
bug |
|
|
added bug |
| 2008-08-07 07:39:30 |
Данило Шеган |
rosetta: status |
New |
Confirmed |
|
| 2008-08-07 07:39:30 |
Данило Шеган |
rosetta: importance |
Undecided |
High |
|
| 2008-08-07 07:39:30 |
Данило Шеган |
rosetta: statusexplanation |
|
|
|
| 2008-10-22 07:30:07 |
Jeroen T. Vermeulen |
rosetta: status |
Confirmed |
Triaged |
|
| 2009-04-03 08:12:52 |
Jeroen T. Vermeulen |
summary |
Report import warnings to uploader |
Report import POSyntaxWarnings to uploader |
|
| 2009-04-03 08:15:02 |
Jeroen T. Vermeulen |
description |
The PO parser (and presumably parsers for other formats as well) 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.
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. |
The PO parser (and presumably parsers for other formats as well) 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.warning(POSyntaxWarning(message)) construct.
|
|
| 2009-04-03 08:21:03 |
Jeroen T. Vermeulen |
description |
The PO parser (and presumably parsers for other formats as well) 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.warning(POSyntaxWarning(message)) construct.
|
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.warning(POSyntaxWarning(message)) construct.
|
|
| 2009-07-10 09:30:47 |
Henning Eggers |
tags |
|
rosetta-imports |
|
| 2009-07-10 13:25:37 |
Jeroen T. Vermeulen |
rosetta: status |
Triaged |
In Progress |
|
| 2009-07-10 13:25:37 |
Jeroen T. Vermeulen |
rosetta: milestone |
|
2.2.7 |
|
| 2009-07-10 13:25:37 |
Jeroen T. Vermeulen |
rosetta: assignee |
|
Jeroen T. Vermeulen (jtv) |
|
| 2009-07-13 12:24:20 |
Jeroen T. Vermeulen |
rosetta: status |
In Progress |
Fix Committed |
|
| 2009-07-23 06:01:50 |
Jeroen T. Vermeulen |
rosetta: status |
Fix Committed |
Fix Released |
|
