Last few translations missing
Bug #3190 reported by
Martin Meredith
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Fix Released
|
Medium
|
Carlos Perelló Marín | ||
Bug Description
When working through a translation of a package page by page, having completed a couple of ones that needed only a few (30 or so) translations, I got to the final page, and no translations showed up ... I had to reselect "untranslated" from the dropdown and click change to see them.
This makes it seem as if the translation for the product is done, when in fact it is not.
| Changed in rosetta: | |
| assignee: | nobody → launchpad |
Revision history for this message
| Dafydd Harries (daf) wrote | #1 |
| Changed in rosetta: | |
| assignee: | launchpad → nobody |
| status: | New → Accepted |
| description: | updated |
Revision history for this message
| Carlos Perelló Marín (carlos) wrote | #2 |
| Changed in rosetta: | |
| assignee: | nobody → carlos |
| status: | Confirmed → Fix Released |
To post a comment you must log in.
I imagine this happens under the following circumstances:
- The user asks Rosetta to only show untranslated items
- There are N (say 15) untranslated items
- The user translates some items on the first page (say 8)
- There are 7 untranslated items left, but when the user submits the page, Rosetta will attempt to display untranslated items starting from the 10th, because this is what the form POST requests
Rosetta should detect when the requested offset is out of range, and redirect the user to a range which actually contains some translations.
Perhaps the form should be changed so that, rather than passing the offset of what it thinks the next page is, it should pass the offsets of the current page. Rosetta can then use this to work out the offset of the next page. That's an implementation detail, though.