I'm working on a pylint plugin that will allow us to enforce our
translation checks. For instance, one we're all guilty of is doing
_("blah blah %s blah" % "blah") which of course results in bad
translations. It turns out, we have all the technology needed to catch
that. I've written a brief piece of code that does so.
What I'm wondering is what else along these lines I could catch.
* x = _("blah blah blah") at the module level?
* _("%s fs on %s") instead of _("%(fsType)s fs on %(deviceName)")?
* Your favorite ideas here.
- Chris
_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
