Currently, protecting a translatable only protects the page itself and protecting a translation page is disallowed by Translate extension. It should be possible to *completely* protect translatable and translation pages along with its units without having to resort to things like AbuseFilter or TitleBlacklist. We can either add a new checkbox to the existing ?action=protect interface or introduce a new page for it. Note that doing this sort of protections would report to the user if the page is protected when the user visits the tux for that group and disallow translating. Currently using TitleBlacklist and AbuseFilter doesn't actually disable tux editing but only prevents the edit after the edit has been requested.