You can also add an msgctxt to distinguish them. This makes them fuzzy. Best regards Ask El 02/06/2016 13:13, "Michael Gratton" <m...@vee.net> escribió:
> On Wed, Jun 1, 2016 at 4:51 PM, Baurzhan Muftakhidinov < > baurthefi...@gmail.com> wrote: > >> Mark those messages as fuzzy, and then ask translators to revisit them, >> > > Okay, thanks. So I assume the best way to do that is to simply add a "#, > fuzzy" to the problematic lines manually and commit them to the git repo, > so they show up as that on l10n.gnome.org? > > On Wed, Jun 1, 2016 at 8:51 PM, Ask Hjorth Larsen <asklar...@gmail.com> > wrote: > >> To fix the bug, validate the translated string and use the English one if >> necessary. >> >> I think this should always be done when translations have the potential >> to crash the application, particularly in complex cases like this. >> > > Yep, I agree. That's exactly what I ended up doing. > > //Mike > > -- > ⊨ Michael Gratton, Percept Wrangler. > ⚙ <http://mjog.vee.net/> > > > _______________________________________________ > gnome-i18n mailing list > gnome-i18n@gnome.org > https://mail.gnome.org/mailman/listinfo/gnome-i18n >
_______________________________________________ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
