Re: List of automatically imported translations?
Francesco Lodolo <[email protected]> Tue, 9 Jul 2019 07:02:06 +0200
| Newsgroups | gmane.comp.mozilla.localization |
|---|---|
| Message-ID | <CA+nXC=qrYWfRM-=0PJ6EU+WZXkeGP979jF9HEGODJxtH_ujVgA@mail.gmail.com> |
Turns out "fuzzy" is a very confusing concept for a lot of people. It's also borrowed from GetText (.po), and IMO it shouldn't be used elsewhere. As Romi pointed out, these are just strings "moving around", and they should remain approved, given that the original were. If there's a specific issue with one of the migrations, that's definitely code that we need to fix. Raising a warning for a missing term is also working by design. Think of a locale having "Pocket" or "Firefox" translated, the old string had an issue that simply becomes visible when moved to Fluent (and a lot of locales fixed them, thanks to that). The "needs editing" is an interesting concept, but not something that I would apply to this specific case, because it assumes the source of truth is the tool, and not the repository. And that makes working with more than one tool unreliable. Francesco Il giorno lun 8 lug 2019 alle ore 22:45 Michael Wolf <[email protected]> ha scritto: > > Francesco Lodolo schrieb: > > The same thing would happen if, for example, someone renames a file > > containing translations in a project. Those strings will show up as > > translated in Pontoon (i.e. approved), and "imported". > > > > Hi Eduardo, hi Francesco, > > couldn't they show up as "fuzzy"? I think it's similar to Pootle where > such imported translations are marked as "needs editing". > > > Michael > > _______________________________________________ > dev-l10n mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-l10n