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

High-bit ISO-8859-1 characters are not always converted to UTF-8 in the output (Origin: bugzilla #596819) #3542

Closed
doxygen opened this Issue Jul 2, 2018 · 0 comments

Comments

Projects
None yet
1 participant
@doxygen
Owner

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:48:00 +0000, Gisbert wrote:

I have an input file in ISO-859-1 and have set INPUT_ENCODING accordingly. The output is, in general, in UTF-8, as expected. Occasionally, however, an ISO-85-1 character with its high bit set will be copied unchanged to the output. This occurs in HTML (which will just show up as a funny glyph), in LaTeX (which will make LaTeX choke because it expects clean UTF-8) and in Perlmod.

The attached file exhibits the problem: input line 33 of test.h, output in section "Macro definitions" of test_8h.html.

On 2009-09-30 04:48:46 +0000, Gisbert wrote:

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

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

The main problem here is that in Latex source code output is reformatted (to prevent page overflows) and the reformatted is not UTF8 aware. As a result it could insert characters in the middle of a multibyte character.
I'll correct this.

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

Actually Comment 2 above is more in line with what you reported in bug # 596807.
I actually didn't see any invalid characters in test_8h.html anymore (they were there in the official 1.6.1 release though)

On 2009-10-05 11:59:03 +0000, Gisbert wrote:

OK, I'll re-test when I get the next release. Thnx, Dimitri!
(Btw: great response on all accounts! This is a marvellous job. And I mean all of doxygen.)

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