Skip to content
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

UCS-2 encoding not supported by doxygen (Origin: bugzilla #593928) #3505

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

Comments

Projects
None yet
1 participant
@doxygen
Copy link
Owner

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-02 15:12:46 +0000, joris.timmermans@gmail.com wrote:

When I have a header file with a class declaration in one encoding (say ASCII), and the CPP file is in a different encoding (say UCS-2 Big Endian) Doxygen fails to match the two and does not generate any documentation for the CPP file.

On 2009-09-02 18:52:52 +0000, Dimitri van Heesch wrote:

Please attach a self-contained example (source + config file in a zip) that allows me to reproduce the problem.

On 2009-09-03 15:06:29 +0000, joris.timmermans@gmail.com wrote:

Created attachment 142413
Minimal example for recreating encoding bug

The good class has both header and cpp file in ASCII encoding. The bad class has an ASCII header but a unicode CPP file.
The generated documentation seems to indicate that the CPP file of the bad class is not parsed.

On 2009-09-21 18:21:43 +0000, Dimitri van Heesch wrote:

*** Bug 595861 has been marked as a duplicate of this bug. ***

On 2009-09-21 18:31:33 +0000, Sorin Sbarnea wrote:

This issue should be confirmed. Also I would mark it as critical because it does garbage the entire file.

I'm not able to edit the description, but adding Unicode to it would be a good idea.

On 2009-10-04 13:57:21 +0000, Dimitri van Heesch wrote:

Confirmed. UCS-2 support will be added to the next subversion update.
When the BOM is detected it will overwrite any setting for INPUT_ENCODING.

On 2009-12-30 13:38:45 +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
You can’t perform that action at this time.