After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 596807 - Producing illegal LaTeX files when input contains eight-bit characters.
Producing illegal LaTeX files when input contains eight-bit characters.
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: general
1.6.1
Other Windows
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2009-09-30 03:46 UTC by Gisbert
Modified: 2009-12-30 13:39 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Config and input file for reproducing the problem. (3.30 KB, application/octet-stream)
2009-09-30 03:47 UTC, Gisbert
Details

Description Gisbert 2009-09-30 03:46:19 UTC
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.
Comment 1 Gisbert 2009-09-30 03:47:36 UTC
Created attachment 144339 [details]
Config and input file for reproducing the problem.
Comment 2 Dimitri van Heesch 2009-10-03 15:43:00 UTC
Confirmed, I'll correct this.
Comment 3 Dimitri van Heesch 2009-12-30 13:39:06 UTC
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).