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

Producing illegal LaTeX files when input contains eight-bit characters. (Origin: bugzilla #596807) #3536

doxygen opened this Issue Jul 2, 2018 · 0 comments


None yet
1 participant

doxygen commented Jul 2, 2018

status RESOLVED severity normal 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 03:46:19 +0000, Gisbert wrote:

I have input files in ISO-8859-1 and have set INPUT_ENCODING accordingly. Doxygen output is in UTF-8, which is, in principle, OK. However, the generated LaTeX files seem to wrap at column 306, chopping in two whatever word happens to fall on that boundary. In the worst case, the first half of a UTF-8 two-byte sequence will be still on the "old" line, while the second half will go to the next. This is no longer valid UTF-8, and consequently, LaTeX will choke when trying to handle this.

To reproduce, use the attached files. The problem will show up in doc/latex/test_8h_source.tex, lines 11/12.

As a side note, there seem to be remains of a config parameter "LATEX_OUTPUT_ENCODING" in the sources for LaTeX output, but the corresponding lines n the LaTeX output handler are commented out via "#if 0". I have found no way to ask doxygen for non-UTF-8 output (which might circumvent the problem), but I may have overlooked an option to achieve this.

On 2009-09-30 03:47:36 +0000, Gisbert wrote:

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

On 2009-10-03 15:43:00 +0000, Dimitri van Heesch wrote:

Confirmed, I'll correct this.

On 2009-12-30 13:39:06 +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