On Tue, Mar 3, 2020 at 7:40 AM Werner LEMBERG <w...@gnu.org> wrote:
> >> If I understand the code correctly (in file `relocate.cc`), the two
> >> calls to `bindtextdomain` happen before relocation files are
> >> read.[*] In other words, the `LILYPOND_LOCALEDIR` environment
> >> variable is honoured but a corresponding assignment in relocation
> >> files are ignored (for the lilypond binary itself – child programs
> >> do get the updated environment variable).
> >>
> >> Maybe this approach should be changed?
> >
> > Perhaps! What is the point of overriding the environment setting
> > for LOCALEDIR? Does LilyPond itself use that setting, or do only
> > the child programs use it?
>
> Please try the attached patch. It now calls `bindtextdomain` a third
> time to take care of setting `LILYPOND_LOCALEDIR` in the relocation
> files.
I’d really rather not patch the code if I don’t have to, and three attempts
to do anything seems smelly to me (it suggests that the logic flow is in
the wrong order), but I’ll give the patch a try and see if it fixes the
proximate issue. Thanks.
Werner
Best,
>
> --
Marnen Laibow-Koser mar...@marnen.org http://www.marnen.org Sent from Gmail
Mobile
