Hans Åberg <[email protected]> writes: >> On 12 Jun 2016, at 16:34, David Kastrup <[email protected]> wrote: >> >> Hans Åberg <[email protected]> writes: >> >>>> On 11 Jun 2016, at 23:55, Hans Åberg <[email protected]> wrote: >>>> >>>> The code below produces, using lilypond-2.19.43-1.darwin-x86 on OS X >>>> 10.11.6, the diagnostic: >>>> Finding the ideal number of pages...Fontconfig warning: ignoring >>>> UTF-8: not a valid region tag >>>> >>>> And the title fonts becomes sans-serif. It happens also in 2.19.42, >>>> but not in 2.19.18. >>> >>> It occurs first in LilyPond 2.19.26. (And not in LilyPond 2.19.25.) >> >> Between 2.19.25 and 2.19.26 there is a whole wagonload of font-related >> commits, defaults, and configuration scripts bouncing around with Linux >> Libertine, URW fonts and others. > > The solution: the UTF-8 locale has not been set as it wishes [1]. OS X > 10.11.6 has no leading language “en”, only > LC_CTYPE=UTF-8 > > It suffices with any single one of: > export LC_CTYPE=en.UTF-8 > export LC_CTYPE=en_US.UTF-8 > export LC_ALL=en_US.UTF-8 > > 1. https://github.com/ariya/phantomjs/issues/13433
In my experience, just calling "perl" is a reasonably reliable way to get complaints about unsupported locale settings. Apparently it tries calling setlocale and does extensive error reporting when that fails. Many other programs just continue without complaint and may run into trouble later. -- David Kastrup _______________________________________________ bug-lilypond mailing list [email protected] https://lists.gnu.org/mailman/listinfo/bug-lilypond
