Eric Blake wrote: > > variable > > gl_cv_func_wcwidth_works=no > > at configure time. > > ... it is not a wise idea to codify > that into libvirt's configure.ac (or any other project).
Yes, I agree. > Rather, if libvirt is hitting test failures due solely to the difference > of Unicode version that the underlying libc complies with, it might be > better to rewrite the failing tests to instead use different Unicode > characters that were available since the oldest supported version of > Unicode across any platform being targetted by libvirt, instead of > testing the behavior of problematic characters that were only recently > added in newer Unicode. Yes. In other words, if you care about a distro that uses a glibc released in 2012 (and the fonts in a distro are often several years older than the glibc), you should limit your expectations regarding Unicode characters to the state of ca. 2005. Bruno
