more and more packages need their locale to be set to something more sensible than C.
This hit me while switching packages over to Python 3. Python gets its encoding from locale, so by
default, it won't decode UTF-8 unless the appropriate encoding is set. Right now, when gtk-doc is
switched to use Python 3, it won't build UTF-8 documentation.
This could be changed in gtk-doc itself (although that is impractical), but perhaps a better way is
to change the default locale for spec scriptlets. Right now the macros set it to C. We could switch
that to "C.UTF-8", "en_US.UTF-8", or export a special RPM variable that could be overriden in your
spec file. Still, the default should be something with UTF-8 in it.
I'm now trying to build a Ring 1 staging project with this change. So far I have seen one failure
related to it: with en_US.UTF-8, bash ranges (like [a-z]) are case-insensitive and match more than
intended. That could be solved by changing the expression, or by setting locale to C.UTF-8.