0

Chm file TOC and index not displaying characters properly

freakcircus

25 June 2009 06:05

None

Follow

Maybe this is related to this post? http://www.innovasys.com/cs/forums/t/467.aspx However you wrote that it only affected plain HTML output, but I have problems with "non-english" characters (æøå) when generating a .chm file. It gets displayed as something like Ã,k instead. This is in the Contents and index, the content page displays it fine.

• Facebook
• Twitter
• LinkedIn

3 comments

• 0
  
  Permanently deleted user 25 June 2009 14:34

  The Microsoft Html Help 1.x compiler and viewer do not fully support unicode, so there is a option you need to set if you are creating content containing non-english characters. The option you need to set is the "Encoding" value in the Build Profile editor - set this to match the language you are authoring your help system is in and you will see the issue with invalid characters will go away.

  This problem doesn't apply to web output or to Help 2.x output, it's just Html Help 1.x that needs this setting defined to match your content as it doesn't fully support unicode content in the way browsers and the Help 2.x viewer does.

  Let me know if you have any further problems.

• 0
  
  freakcircus 26 June 2009 02:39

  The "Content Encoding" in the build profile was set to UTF-8, which is de-facto standard for international content on the web, so (from an end users perspective) it should be a correct setting when writing non-english content. However, when I set it to e.g. Norwegian bokmål (which is the language I am currently writing in), it displays correctly. Strange... Comments?
• 0
  
  Permanently deleted user 26 June 2009 02:50

  All modern browsers fully support unicode and UTF-8. Unfortunately, the Microsoft Html Help 1.x compiler and viewer (which are both more than 10 years old now and haven't been changed for many years) do not support unicode or UTF-8 encoding for the Table of Contents, Index or full text search (UTF-8 is supported in the actual content pane because that is an embedded IE instance). Therefore when you are targetting Html Help 1.x with non-latin character content you need to identify the specific encoding to use.

  Hope that helps.