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 759622 - problems with charset using plantuml
problems with charset using plantuml
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: general
1.8.10
Other Windows
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2015-12-18 10:57 UTC by fjdepedro
Modified: 2015-12-30 10:19 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
example to show the bug (113.33 KB, application/zip)
2015-12-18 10:57 UTC, fjdepedro 		Details

Description fjdepedro 2015-12-18 10:57:16 UTC 
Created attachment 317621 [details]
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
Comment 1 Dimitri van Heesch 2015-12-20 14:39:43 UTC 
Confirmed. Should be fixed in the next GIT update.
Comment 2 Dimitri van Heesch 2015-12-30 10:19:42 UTC 
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).