The basic user understands whitelist_from and blacklist_from. But when he encounters the locales, he wonders why cannot there be whitelist_locales and blacklist_locales. He does not want to learn the superior logic of why his wish is not smart. He just wants to find the commands for whitelist_locales and blacklist_locales, and can only find half.
MK> The answer is to read the Conf manpage and understand it. It MK> doesn't mention it in the exact wording you want, but there is an MK> answer and ok_locales is exactly the answer you want. But the basic user is not in the business of understanding things. He is just looking for the pair whitelist_locales and blacklist_locales, or whatever devious name they are called, and can only find half of the pair. Perhaps deep down some macro could be made so the user can finally find such a pair, without having to understand anything. MK> Quite frankly, a "not_ok_locales" option doesn't make any useful sense MK> anyway. If you want to restrict the locales, restrict it to the ones you MK> speak. Don't bother singling out just ones you dislike... ...just because the software can't do it yet. MK> Let's say you speak English and Chinese, and hate Russian because you MK> get lots of spam in that text format and don't speak it. That's me, English and Chinese, and hate Russian. MK> In this situation, why would you want "not_ok_localles ru" instead of MK> "ok_locales en zh"? Is there a reason you'd want to allow character sets MK> like Thai, Korean, etc, even though you don't understand them any better MK> than Russian? No. You make assumptions about peoples lifestyles. And what if they did?
