lilypond.org has wrong HTML files for 2.19.84 (was: How do I change LOCALEDIR?)

[Werner LEMBERG]

> From: Marnen Laibow-Koser <address@hidden>
> Date: Wed, 4 Mar 2020 10:35:00 -0500
>
>> The search algorithm is actually documented in `usage.pdf`,
> 
> I’ve never seen that file.  Where would I find it?

Ouch.  It should be at

  http://lilypond.org/doc/v2.19/Documentation/usage-big-page.html#relocation

but it's missing!  The same for

  http://lilypond.org/doc/v2.19/Documentation/usage.pdf

which misses the whole section on relocation.

This means that the HTML files on lilypond.org are not reflecting
2.19.84 — I've added the documentation for relocation with commit
7200d7365be more than a year ago...

This is a serious problem IMHO.

> OMG this is documented?  I wish I’d known all this weeks ago when I
> was writing the Mac Makefile!

Sorry for that.  I only use my self-compiled PDF files and didn't
notice that it's missing on the web page.

> Sure, and I’d obviously *rather* that we have the localized strings
> as early as possible.  But to me, the most obvious way of doing that
> *correctly* would be to determine the *actual* locale path as early
> as possible, and to call bindtextdomain (once) as soon as possible
> after that.  After all, if LOCALEDIR has been changed, then it’s
> very likely that the early call to bindtextdomain (with the obsolete
> path) won’t *actually* load any usable strings, so what’s the point
> of having it?

Again: Patches are highly welcomed :-)


    Werner