Visual Studio Developer Center > Visual Studio Forums > Developer Documentation and Help System > The non-Unicode Program setting must be the same with the language in sandcastle?

Answered The non-Unicode Program setting must be the same with the language in sandcastle?

  • Wednesday, August 08, 2007 12:11 PM
     
     

    Hi,

    When I build localized help file, I found that the non-Unicode Program setting in control panel must be the same with the language in sandcastle. If not, the text in the left pane (the contents) of chm file will become junk codes, but the text in the right pane are all right. The xml/html files I used are all UTF8 encoded.

    Is this a bug? I need to build localized documents for several languages, it will take lots of time to change the settings and reboot my machine.

     

    Thanks,

    Luther

Answers

  • Wednesday, August 08, 2007 1:29 PM
     
     Answered

    Hi Luther,

     

    Unfortunately, it appears to be a bug.  I'm not sure if they are referring to the same thing, but the PackageThis team states the following on their project's home page under Limitations:

     

    There is a bug in HTML Help that will cause the index tab to show incorrect character encodings depending on your default locale. For example, you'll see this problem if you build a Japanese .chm file on a machine with the default locale set to English. If you change the default locale to Japanese (which requires a reboot) and rebuild the .chm file, it won't show this problem (even on an English machine).

    HTH

     

    - Dave

All Replies

  • Wednesday, August 08, 2007 1:29 PM
     
     Answered

    Hi Luther,

     

    Unfortunately, it appears to be a bug.  I'm not sure if they are referring to the same thing, but the PackageThis team states the following on their project's home page under Limitations:

     

    There is a bug in HTML Help that will cause the index tab to show incorrect character encodings depending on your default locale. For example, you'll see this problem if you build a Japanese .chm file on a machine with the default locale set to English. If you change the default locale to Japanese (which requires a reboot) and rebuild the .chm file, it won't show this problem (even on an English machine).

    HTH

     

    - Dave

  • Thursday, August 09, 2007 2:26 AM
     
     

    Yes, that's the same problem I met. Hope they can fix this bug in next release...

     

    Thanks,

    Luther