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 599128 - Studio 12 built-in iconv doesn't know Windows-1250 HtmlHelp::initialize
Studio 12 built-in iconv doesn't know Windows-1250 HtmlHelp::initialize
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: general
1.6.1
Other Solaris
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2009-10-20 23:41 UTC by Lou Hafer
Modified: 2009-12-30 13:38 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Lou Hafer 2009-10-20 23:41:20 UTC
In HtmlHelp::initialize, if CHM_INDEX_ENCODING is undefined, it defaults to Windows-1250. The Studio 12 iconv_open builtin doesn't know this encoding name and returns -1. A core dump follows shortly after from HtmlHelp::recode during index generation. CP1250 works ok, and is listed as a synonym, but I have no idea if that's an acceptable equivalent --- I just don't have much knowledge of what's being generated here. The generated HTML looks ok in a casual inspection with Firefox.

I'm forcing the solaris-cc build environment. CC version info is Sun C++ 5.9 SunOS_sparc Patch 124863-01 2007/07/25

const char *str = Config_getString("CHM_INDEX_ENCODING");
  /*
    In the Solaris CC environment, the builtin iconv doesn't grok Windows-1250.
    It does understand the (supposedly equivalent) CP1250.

    if(!str) str = "Windows-1250";
  */
  if(!str) str = "CP1250";
  m_fromUtf8 = portable_iconv_open(str,"UTF-8");
Comment 1 Dimitri van Heesch 2009-10-25 14:49:28 UTC
Thanks, I'll include this patch.
Comment 2 Dimitri van Heesch 2009-12-30 13:38:48 UTC
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).