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

problems with charset using plantuml (Origin: bugzilla #759622) #5919

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 normal in component general for ---
Reported in version 1.8.10 on platform Other
Assigned to: Dimitri van Heesch

Original attachment names and IDs:

On 2015-12-18 10:57:16 +0000, fjdepedro wrote:

Created attachment 317621
example to show the bug

The charset of my source files is windows-1252.
I have PlantUML diagrams descriptions in the source file, inside doxygen comments.
In the doxygen configuration, I set INPUT_ENCODING to windows-1252.

The doxygen documentation is generated well, but PlantUML diagrams have bad characteres.

Looking for the problem, I have found that the file generated with the PlantUML diagram description (inline_umlgraph_1.pu) uses UTF-8 encoding.

But PlantUML is executed with the charset defined in INPUT_ENCODING (windows-1252 in my case), generating a bad graph.

( line 82 in file src/plantuml.cpp :

pumlArgs+="-charset " + Config_getString("INPUT_ENCODING") + " ";

)

If intermediate files *.pu are generated in UTF-8, then PlantUML must be executed with the option -charset UTF-8, not with the INPUT_ENCODING

On 2015-12-20 14:39:43 +0000, Dimitri van Heesch wrote:

Confirmed. Should be fixed in the next GIT update.

On 2015-12-30 10:19:42 +0000, Dimitri van Heesch wrote:

This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.11. Please verify if this is indeed the case. Reopen the
bug if you think it is not fixed and please include any additional information
that you think can be relevant (preferably in the form of a self-contained example).

@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