New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Names with eight-bit characters for \page break HTML links and LaTeX includes (Origin: bugzilla #596809) #3537

doxygen opened this Issue Jul 2, 2018 · 0 comments


None yet
1 participant

doxygen commented Jul 2, 2018

status RESOLVED severity minor in component general for ---
Reported in version 1.6.1 on platform Other
Assigned to: Dimitri van Heesch

Original attachment names and IDs:

On 2009-09-30 04:10:27 +0000, Gisbert wrote:

I have input files in ISO-8859-1 and have set INPUT_ENCODING accordingly. As the for \page (first argument) I chose a name containing characters with the high bit set. (Probably not a clever thing to do...) doxygen processes this alright at first sight, producing amongst others a HTML file for this page, using as a file name the UTF-8 version of my . The HTML file containing a link to this file also correctly contains that UTF-8 form of the name. But my browser (Firefox 3.5.x), when trying to follow the link, assumes that the name of target file will be encoded according to Windows rules (non-UTF-8). So the link is broken.

The attached files will exhibit the problem: In the generated docs, in the tree view, click on the link "This is a page.". This will yield a "file not found" error (at least under Windows). (The culprit is line 101 in tree.html.)

On 2009-09-30 04:11:03 +0000, Gisbert wrote:

Created attachment 144349
Config and input file for reproducing the problem.

On 2009-09-30 04:23:13 +0000, Gisbert wrote:

The generated LaTeX files will also reference a file witha name encoded in UTF-8, which will make LaTeX choke, too.

On 2009-10-03 15:52:54 +0000, Dimitri van Heesch wrote:

Confirmed. Should be fixed in the next subversion update.

On 2009-12-30 13:38:59 +0000, Dimitri van Heesch wrote:

This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.6.2. Please verify if this is indeed the case and reopen the
bug if you think it is not fixed (include any additional information that you
think can be relevant).

@doxygen doxygen closed this Jul 2, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment