MantisBT - CMake
View Issue Details
0013164CMakeCTestpublic2012-04-24 09:152016-06-10 14:31
Zog Zog 
Kitware Robot 
normalminoralways
closedmoved 
CMake 2.8.8 
 
0013164: UTF-8 characters of C++ source files appear wrong in CDash viewCoverageFile
Hello,

I have UTF-8 encoded C++ source files.
When I look at the test coverage in CDash, they are not what they should be.

Example :

Source file contains "répertoire" which in UTF-8 is "répertoire".

In CDash, it appears like "répertoire" and in the HTML source code it is "répertoire".
CharacterSet, Unicode
Issue History
2012-04-24 09:15Zog ZogNew Issue
2012-04-24 09:22Zog ZogNote Added: 0029322
2012-04-24 09:27Zog ZogTag Attached: CharacterSet
2012-04-24 09:27Zog ZogTag Attached: Unicode
2012-04-24 09:29Zog ZogNote Added: 0029323
2012-04-25 11:30Zog ZogNote Edited: 0029323bug_revision_view_page.php?bugnote_id=29323#r629
2012-08-11 21:35David ColeStatusnew => backlog
2012-08-11 21:35David ColeNote Added: 0030408
2016-06-10 14:28Kitware RobotNote Added: 0042032
2016-06-10 14:28Kitware RobotStatusbacklog => resolved
2016-06-10 14:28Kitware RobotResolutionopen => moved
2016-06-10 14:28Kitware RobotAssigned To => Kitware Robot
2016-06-10 14:31Kitware RobotStatusresolved => closed

Notes
(0029322)
Zog Zog   
2012-04-24 09:22   
Note :

gcov file in ${BUILD_DIR}/Testing/CoverageInfo is well encoded.
(0029323)
Zog Zog   
2012-04-24 09:29   
(edited on: 2012-04-25 11:30)
Note 2 :

the last line of the description should be :

In CDash, it appears like "répertoire" and in the HTML source code it is "r& Atilde;& copy;pertoire" instead of "r& ecute;pertoire".

(0030408)
David Cole   
2012-08-11 21:35   
Sending old, never assigned issues to the backlog.

(The age of the bug, plus the fact that it's never been assigned to anyone means that nobody is actively working on it...)

If an issue you care about is sent to the backlog when you feel it should have been addressed in a different manner, please bring it up on the CMake mailing list for discussion. Sign up for the mailing list here, if you're not already on it: http://www.cmake.org/mailman/listinfo/cmake [^]

It's easy to re-activate a bug here if you can find a CMake developer who has the bandwidth to take it on, and ferry a fix through to our 'next' branch for dashboard testing.
(0042032)
Kitware Robot   
2016-06-10 14:28   
Resolving issue as `moved`.

This issue tracker is no longer used. Further discussion of this issue may take place in the current CMake Issues page linked in the banner at the top of this page.