Comment 9 for bug 107737
Revision history for this message
| Jannick Kuhr (jakuhr-deactivatedaccount) wrote | #9 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
I thought it would be also in your interest to figure out what happened last year and caused this problem of Rosetta, not just to fix the results. And I still hope that we could ensure that this issue is already fixed and won't happen again. Perhaps it would be also possible to detect affected strings and only reset this ones?
If you told us that you know what happened, the bug is already fixed and you don't see any other possibility than resetting the whole translation, you could close this bug.
I hope you understood my point.
Kind regards, Jannick