Description
Describe the bug
When I configure the same member group names in multibyte characters, these member groups are separately generated in the output html.
Expected behavior
The member groups with the same name should be integrated even though written in multibyte characters.
Screenshots
To Reproduce
When using @name commands in ascii, member groups are integrated correctly.
However, @name commands in multibyte characters cause separation.
The attachment MemberGroupSample.zip contains two header files that contain the same member groups.
/**
@file
@brief header1
*/
namespace common {
// (example of success)
//! @name Member group
//! @{
/**
@brief Function1_1
@param[in] arg1 This is arg1
@param[in] arg2 This is arg2
*/
void Function1_1(int arg1, int arg2);
//! @}
// (example of failure)
//! @name 成员分组
//! @{
/**
@brief Function1_2
@param[in] arg1 This is arg1
@param[in] arg2 This is arg2
*/
void Function1_2(int arg1, int arg2);
//! @}
// (example of failure)
//! @name メンバーグループ
//! @{
/**
@brief Function1_3
@param[in] arg1 This is arg1
@param[in] arg2 This is arg2
*/
void Function1_3(int arg1, int arg2);
//! @}
}
Version
1.9.5 and 1.9.4 on Windows 10 (64 bit) and MacOSX
Additional context
The change of qstricmp function in Refactoring: replace old style casts may cause this issue.
While changed qstrnicmp may not cause the issue.