Reporting a bug in untranslated strings is tricky and error prone
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
Low
|
Unassigned | ||
Bug Description
There should be a quick way to report a mistake , a typo or an obscure string. Currently, you have to go to the single viewof the string.
copy the unique url of the string
Click on bugs
Report a new bug.
Name it Typo, Another Typo, Yet Another Typo...
Paste the URL
The maintainer then has to do a debdiff
Forwards it upstream if necessary.
Half the time, it has already been reported upstream (due to not so frequent updating of the templates).
We should have a button to report a mistake in the original string that would do all of that work (the only remaining manual work for the typo reporter would be to give precision as to the mistake, or even propose a corrected version of the string)
This could be not only for typos, but also for poorly phrased strings.
| Matthew Paul Thomas (mpt) wrote | #1 |
| Changed in rosetta: | |
| status: | New → Confirmed |
| Jeroen T. Vermeulen (jtv) wrote | #2 |
| Matthew Paul Thomas (mpt) wrote | #3 |
| Jeroen T. Vermeulen (jtv) wrote | #4 |
| Changed in rosetta: | |
| importance: | Undecided → Medium |
| status: | Confirmed → Triaged |
| Данило Шеган (danilo) wrote | #5 |
| David Nielsen (davidnielsen-deactivatedaccount) wrote | #6 |
| Changed in launchpad: | |
| importance: | Medium → Low |
| summary: |
- Easily report a bug from a string + Reporting a bug in untranslated strings is tricky and error prone |
Excellent idea!