If I understand correctly, the cause is the loading order of initialization
files.
The current `make doc' behavior of invoking texi2html is the following:
First, texi2html loads the LilyPond's initialization file.
Then, texi2html loads the its i18n settings.
In this case, some LilyPond's messages are overwritten by texi2html's i18n
settings.
The LilyPond's Japanese messages for texi2html are UTF-8 flagged strings.
However, the texi2html's default i18n messages are not UTF-8 flagged strings.
Therefore, Japanese navigation bar is broken.
On the other hand, in the GUB environment, texi2html can not locate i18n
setting files due to another problem.
Therefore, fortunately, LilyPond's messages are not overwritten.
So Japanese navigation bar is not broken.
Moreover, in the case of other languages, the both LilyPond's and texi2html's
strings are ASCII.
Therefore, even if the messages are overwritten, the navigation bar is not
broken.
---
** [issues:#4713] texi2html generated Japanese html navigation bars are broken**
**Status:** Accepted
**Created:** Thu Dec 24, 2015 12:57 PM UTC by Masamichi Hosoda
**Last Updated:** Thu Dec 24, 2015 01:08 PM UTC
**Owner:** Masamichi Hosoda
In a non-GUB environment, `make doc' generates Japanese html document which has
broken navigation bar.
In a GUB environment, it is not broken.
---
Sent from sourceforge.net because [email protected] is
subscribed to https://sourceforge.net/p/testlilyissues/issues/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is
a mailing list, you can unsubscribe from the mailing list.
------------------------------------------------------------------------------
_______________________________________________
Testlilyissues-auto mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
