Issue 1036 in lilypond: Links to accented anchors

[lilypond]

Status: Accepted
Owner: ----
Labels: Type-Build Priority-Postponed

New issue 1036 by percival.music.ca: Links to accented anchors
http://code.google.com/p/lilypond/issues/detail?id=1036

%% report from Francisco about doc translation build.
%% current lilypond version: 2.13.15.

Hello. This is for perl gurus or people who know texi2html well. My
aim is to state the existence of a bug, as a remainder for the future.
I myself would fix it if I knew how to.

Currently, some links to anchors in bigpage HTML docs, in all three
es/fr/de languages, v2.13, do not work as expected, these are the
symptoms.

for example in  
out-www/offline-root////Documentation/notation-big-page.es.html
, let's go to NR1 from the index to appreciate the problem.

To generate anchor and links, different methods seem to exist:

- index entries and menus link to translated section names, but a bug
makes these names to crop two characters shorter if the original has
an accented letter. This smells to an utf-8 confusion between
characters and bytes.

for example

  
out-www/offline-root////Documentation/notation-big-page.es.html#Notacion-music

for NR 1 Notación Musical

- in the page itself, each section has two anchors, and sometimes none
of them match the link as explained above. One is just before the
next/previous menu for that section, and has accented characters hex
encoded, as in

 notation-big-page.es.html#Notaci_00f3n-musical

The other is in English, just after the section next/previous menu, as in

 notation-big-page.es.html#Musical-notation


To summarize, the HTML code is in our example

<a name="Notaci_00f3n-musical"></a>
<table class="nav_table"> ...</table>
<a name="Musical-notation"></a>
<h1 class="chapter">1. Notación musical</h1>

but the link from the index is

<a name="toc-Notacion-musical"
href="notation-big-page.es.html#Notacion-music">1. Notación
musical</a> etc.

Same for every node with accented characters.  Split HTML docs do not
suffer from this in such a bad way, because the html file is correctly
 specified from the link; therefore, only accented anchors into an
HTML file show the problem.

Also, 2.12 docs are OK but all links and anchors are in English, so no
problem here.

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings