On Wednesday at 14:28, Matthew East wrote: > The best way to report an error in the original language of a program > would seem to be to file a bug on the product or package being > translated. > > This is already relatively easy to do but could I suppose be made even > easier by including a link in the translation interface to the bug > section. Indeed, it's easy, except for creating a proper UI in the already over-crowded translate UI. :) > Where the translation is being done on a package, it would then be up > to the bug triagers for the distribution to filter the report > upstream, if appropriate. Not all strings will be introduced by > upstream, so it's appropriate for that decision to be made at that > stage, in my opinion. Yeah, agreed. And clicking on the 'Bugs' tab also takes you directly to that sourcepackage bug listing page, and you get a 'Report a bug' button right there. It's indeed a two (or three, see below) step process, but it's not that hard. However, documenting and making it more obvious would certainly be useful. It'd also help if you could directly copy a faulty string to the bug report as well, but that's another step which is not too hard: manually copy and paste it into the bug report. > Where we're talking about a product which uses Launchpad for > translations but not for bug reporting, that obviously needs to be > made clear by the interface (but then again, it should be anyway). "Bugs" is greyed out in cases like that. Of course, getting a one-step process would be nice, but I am not sure it's worth crowding the UI for a rarely used feature. Cheers, Danilo
This is the launchpad-users mailing list archive — see also the general help for Launchpad.net mailing lists.
(Formatted by MHonArc.)