OT: HTML Help Related Topics control and character
> When you compiled the Arabic CHM, did you do it on an Arabic system? NOT just one with the > locale set? That's what HTML Help requires for Search to work; always has. Not just for > Arabic, but for any other locale. My experience is that it's OK to use English Windows when compiling a localized CHM. I have not done Arabic, but I have done Hebrew (also an RTL language), Russian, Greek, and Asian languages. The critical aspect is to set the Windows system locale to the target language. The system locale is an internal code page that Windows uses for non-Unicode applications. It is different from the user locale, which controls the date formats and so forth. To set the system locale on Windows 7, open Control Panel > Clock, Language, and Region > Region and Language > Administrative > Language for Non-Unicode Programs. After you set the system locale, Windows prompts you to restart the computer. For more information, see: http://wiki.webworks.com/DavidShaked/LocalizingWWePProjects Most of the article is about WebWorks ePublisher, but I think the information about the system locale is relevant to all tools. David Shaked (Wernick) AlmondWeb Ltd. http://www.almondweb.com Technical Documentation * Web Development * Word and WebWorks Consultants
OT: HTML Help Related Topics control and character
Jeremy has provided information about SBAppLocale.exe, which spares you the reboot. http://mif2go.com/xhtml/htmlhelp_0073_9133compilinginadifferentlanguage.htm On 2013-02-13 14:41, David Shaked wrote: >> When you compiled the Arabic CHM, did you do it on an Arabic system? NOT > just one with the >> locale set? That's what HTML Help requires for Search to work; always has. > Not just for >> Arabic, but for any other locale. > My experience is that it's OK to use English Windows when compiling a > localized CHM. I have not done Arabic, but I have done Hebrew (also an RTL > language), Russian, Greek, and Asian languages. > > The critical aspect is to set the Windows system locale to the target > language. The system locale is an internal code page that Windows uses for > non-Unicode applications. It is different from the user locale, which > controls the date formats and so forth. > > To set the system locale on Windows 7, open Control Panel > Clock, Language, > and Region > Region and Language > Administrative > Language for Non-Unicode > Programs. After you set the system locale, Windows prompts you to restart > the computer. > > For more information, see: > > http://wiki.webworks.com/DavidShaked/LocalizingWWePProjects > > Most of the article is about WebWorks ePublisher, but I think the > information about the system locale is relevant to all tools. > > David Shaked (Wernick) > > AlmondWeb Ltd. > http://www.almondweb.com > Technical Documentation * Web Development * Word and WebWorks Consultants > > ___ > > > You are currently subscribed to framers as jowens at magma.ca. > > Send list messages to framers at lists.frameusers.com. > > To unsubscribe send a blank email to > framers-unsubscribe at lists.frameusers.com > or visit http://lists.frameusers.com/mailman/options/framers/jowens%40magma.ca > > Send administrative questions to listadmin at frameusers.com. Visit > http://www.frameusers.com/ for more resources and info. > > __ Information from ESET NOD32 Antivirus, version of virus signature > database 8007 (20130213) __ > > The message was checked by ESET NOD32 Antivirus. > > http://www.eset.com > > > >
OT: HTML Help Related Topics control and character encoding
On 2013-02-13 12:10, Jeremy H. Griffith wrote: > I wonder if there is a different version of the > ActiveX control for different code pages? It > sounds like it's not using the same one as the > rest. > > See if there is a > in the instance of the control in your HTML. > MSDN has some very sketchy docs for it: > > http://msdn.microsoft.com/en-us/library/windows/desktop/ms644677%28v=vs.85%29.aspx > but one of the values is the character set. > They don't say what the syntax for that is, > but I'd try 1256, CP1256, and cp-1256 to start. For the record, here's what I found out. The Font param works on the button. With value=",, cp1256" and my system locale set to English, it changes the text to question marks. If I change the system locale to Arabic, then the button text is in Arabic even without the Font param. (The button text was the one thing I hadn't tested for locale -- I didn't have a translation for "Related Topics" at the time). If I supply a bad Font param (1256 instead of cp1256), and system locale is Arabic, I get question marks . I can't get the Font param (or the Text param) to work on an Item. In fact, if I place the Font param after an Item, its arguments affect the button instead. This is true even when the Button param is placed after the Item and Font params! The Text param doesn't do anything anywhere, as far as I can see. For Arabic, we'll just use a Related Topics subheading and some links. But it was interesting! Thanks again. > There are also advisories about a "security" > "upgrade" from MS that broke this control at: > > http://www.helpwaregroup.com/system/app/pages/customSearch?scope=search-ns&q=Related+Topics+ActiveX > > HTH! > > -- Jeremy H. Griffith, at Omni Systems Inc. >http://mif2go.com/ > > __ Information from ESET NOD32 Antivirus, version of virus signature > database 8006 (20130213) __ > > The message was checked by ESET NOD32 Antivirus. > > http://www.eset.com > > > >
OT: HTML Help Related Topics control and character encoding
Thanks for the tips! I'll check them out. On 2013-02-13 12:10, Jeremy H. Griffith wrote: > On Wed, 13 Feb 2013 11:32:23 -0500, Jim Owens wrote: > >> Hi, Jeremy. I'm using SBAppLocale to compile (as recommended in the >> Mif2Go Guide!), and Search is working OK in Arabic. In fact, the Arabic >> is OK everywhere in the output -- >> >> The pages are all encoded with windows-1256. > You're right on top of it, then. ;-) > >> except for the Related Topics button >> text, and the link text in the Related Topics "Topics Found" dialog box. >> >> Setting aside the compilation, if I just open an HTML page in a browser, >> everything is in Arabic, except the text on the Related Topics button >> (which is in something like Cyrillic) and the text in the Related Topics >> dialog for the button (which is all question marks unless I set the >> system locale to Arabic, in which case it's something like Cyrillic). > I wonder if there is a different version of the > ActiveX control for different code pages? It > sounds like it's not using the same one as the > rest. > > See if there is a > in the instance of the control in your HTML. > MSDN has some very sketchy docs for it: > > http://msdn.microsoft.com/en-us/library/windows/desktop/ms644677%28v=vs.85%29.aspx > but one of the values is the character set. > They don't say what the syntax for that is, > but I'd try 1256, CP1256, and cp-1256 to start. > > There are also advisories about a "security" > "upgrade" from MS that broke this control at: > > http://www.helpwaregroup.com/system/app/pages/customSearch?scope=search-ns&q=Related+Topics+ActiveX > > HTH! > > -- Jeremy H. Griffith, at Omni Systems Inc. >http://mif2go.com/ > > __ Information from ESET NOD32 Antivirus, version of virus signature > database 8006 (20130213) __ > > The message was checked by ESET NOD32 Antivirus. > > http://www.eset.com > > > >
OT: HTML Help Related Topics control and character encoding
On Wed, 13 Feb 2013 11:32:23 -0500, Jim Owens wrote: >Hi, Jeremy. I'm using SBAppLocale to compile (as recommended in the >Mif2Go Guide!), and Search is working OK in Arabic. In fact, the Arabic >is OK everywhere in the output -- > >The pages are all encoded with windows-1256. You're right on top of it, then. ;-) >except for the Related Topics button >text, and the link text in the Related Topics "Topics Found" dialog box. > >Setting aside the compilation, if I just open an HTML page in a browser, >everything is in Arabic, except the text on the Related Topics button >(which is in something like Cyrillic) and the text in the Related Topics >dialog for the button (which is all question marks unless I set the >system locale to Arabic, in which case it's something like Cyrillic). I wonder if there is a different version of the ActiveX control for different code pages? It sounds like it's not using the same one as the rest. See if there is a in the instance of the control in your HTML. MSDN has some very sketchy docs for it: http://msdn.microsoft.com/en-us/library/windows/desktop/ms644677%28v=vs.85%29.aspx but one of the values is the character set. They don't say what the syntax for that is, but I'd try 1256, CP1256, and cp-1256 to start. There are also advisories about a "security" "upgrade" from MS that broke this control at: http://www.helpwaregroup.com/system/app/pages/customSearch?scope=search-ns&q=Related+Topics+ActiveX HTH! -- Jeremy H. Griffith, at Omni Systems Inc. http://mif2go.com/
Re: OT: HTML Help Related Topics control and character
Jeremy has provided information about SBAppLocale.exe, which spares you the reboot. http://mif2go.com/xhtml/htmlhelp_0073_9133compilinginadifferentlanguage.htm On 2013-02-13 14:41, David Shaked wrote: When you compiled the Arabic CHM, did you do it on an Arabic system? NOT just one with the locale set? That's what HTML Help requires for Search to work; always has. Not just for Arabic, but for any other locale. My experience is that it's OK to use English Windows when compiling a localized CHM. I have not done Arabic, but I have done Hebrew (also an RTL language), Russian, Greek, and Asian languages. The critical aspect is to set the Windows system locale to the target language. The system locale is an internal code page that Windows uses for non-Unicode applications. It is different from the user locale, which controls the date formats and so forth. To set the system locale on Windows 7, open Control Panel > Clock, Language, and Region > Region and Language > Administrative > Language for Non-Unicode Programs. After you set the system locale, Windows prompts you to restart the computer. For more information, see: http://wiki.webworks.com/DavidShaked/LocalizingWWePProjects Most of the article is about WebWorks ePublisher, but I think the information about the system locale is relevant to all tools. David Shaked (Wernick) AlmondWeb Ltd. http://www.almondweb.com Technical Documentation * Web Development * Word and WebWorks Consultants ___ You are currently subscribed to framers as jow...@magma.ca. Send list messages to framers@lists.frameusers.com. To unsubscribe send a blank email to framers-unsubscr...@lists.frameusers.com or visit http://lists.frameusers.com/mailman/options/framers/jowens%40magma.ca Send administrative questions to listad...@frameusers.com. Visit http://www.frameusers.com/ for more resources and info. __ Information from ESET NOD32 Antivirus, version of virus signature database 8007 (20130213) __ The message was checked by ESET NOD32 Antivirus. http://www.eset.com ___ You are currently subscribed to framers as arch...@mail-archive.com. Send list messages to framers@lists.frameusers.com. To unsubscribe send a blank email to framers-unsubscr...@lists.frameusers.com or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to listad...@frameusers.com. Visit http://www.frameusers.com/ for more resources and info.
Re: OT: HTML Help Related Topics control and character encoding
On 2013-02-13 12:10, Jeremy H. Griffith wrote: I wonder if there is a different version of the ActiveX control for different code pages? It sounds like it's not using the same one as the rest. See if there is a in the instance of the control in your HTML. MSDN has some very sketchy docs for it: http://msdn.microsoft.com/en-us/library/windows/desktop/ms644677%28v=vs.85%29.aspx but one of the values is the character set. They don't say what the syntax for that is, but I'd try 1256, CP1256, and cp-1256 to start. For the record, here's what I found out. The Font param works on the button. With value=",, cp1256" and my system locale set to English, it changes the text to question marks. If I change the system locale to Arabic, then the button text is in Arabic even without the Font param. (The button text was the one thing I hadn't tested for locale -- I didn't have a translation for "Related Topics" at the time). If I supply a bad Font param (1256 instead of cp1256), and system locale is Arabic, I get question marks . I can't get the Font param (or the Text param) to work on an Item. In fact, if I place the Font param after an Item, its arguments affect the button instead. This is true even when the Button param is placed after the Item and Font params! The Text param doesn't do anything anywhere, as far as I can see. For Arabic, we'll just use a Related Topics subheading and some links. But it was interesting! Thanks again. There are also advisories about a "security" "upgrade" from MS that broke this control at: http://www.helpwaregroup.com/system/app/pages/customSearch?scope=search-ns&q=Related+Topics+ActiveX HTH! -- Jeremy H. Griffith, at Omni Systems Inc. http://mif2go.com/ __ Information from ESET NOD32 Antivirus, version of virus signature database 8006 (20130213) __ The message was checked by ESET NOD32 Antivirus. http://www.eset.com ___ You are currently subscribed to framers as arch...@mail-archive.com. Send list messages to framers@lists.frameusers.com. To unsubscribe send a blank email to framers-unsubscr...@lists.frameusers.com or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to listad...@frameusers.com. Visit http://www.frameusers.com/ for more resources and info.
RE: OT: HTML Help Related Topics control and character
> When you compiled the Arabic CHM, did you do it on an Arabic system? NOT just one with the > locale set? That's what HTML Help requires for Search to work; always has. Not just for > Arabic, but for any other locale. My experience is that it's OK to use English Windows when compiling a localized CHM. I have not done Arabic, but I have done Hebrew (also an RTL language), Russian, Greek, and Asian languages. The critical aspect is to set the Windows system locale to the target language. The system locale is an internal code page that Windows uses for non-Unicode applications. It is different from the user locale, which controls the date formats and so forth. To set the system locale on Windows 7, open Control Panel > Clock, Language, and Region > Region and Language > Administrative > Language for Non-Unicode Programs. After you set the system locale, Windows prompts you to restart the computer. For more information, see: http://wiki.webworks.com/DavidShaked/LocalizingWWePProjects Most of the article is about WebWorks ePublisher, but I think the information about the system locale is relevant to all tools. David Shaked (Wernick) AlmondWeb Ltd. http://www.almondweb.com Technical Documentation * Web Development * Word and WebWorks Consultants ___ You are currently subscribed to framers as arch...@mail-archive.com. Send list messages to framers@lists.frameusers.com. To unsubscribe send a blank email to framers-unsubscr...@lists.frameusers.com or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to listad...@frameusers.com. Visit http://www.frameusers.com/ for more resources and info.
OT: HTML Help Related Topics control and character encoding
Hi, Jeremy. I'm using SBAppLocale to compile (as recommended in the Mif2Go Guide!), and Search is working OK in Arabic. In fact, the Arabic is OK everywhere in the output -- except for the Related Topics button text, and the link text in the Related Topics "Topics Found" dialog box. Setting aside the compilation, if I just open an HTML page in a browser, everything is in Arabic, except the text on the Related Topics button (which is in something like Cyrillic) and the text in the Related Topics dialog for the button (which is all question marks unless I set the system locale to Arabic, in which case it's something like Cyrillic). The pages are all encoded with windows-1256. On 2013-02-13 10:01, Jeremy H. Griffith wrote: > On Wed, 13 Feb 2013 05:44:07 -0500, Jim Owens wrote: > >> We're using the HTML Help Related Topics ActiveX control. When we >> create an with Arabic text for the title, the wrong characters >> appear in the Topics Found dialog box, even when the system locale is >> set to Arabic. Everything else in the compiled help uses the correct >> Arabic characters, whether or not the system locale is set to Arabic. >> The encoding used by our translator is windows-1256. >> >> Is there something we can try, or is this just a limitation of the control? > When you comiled the Arabic CHM, did you do it on > an Arabic system? NOT just one with the locale set? > That's what HTML Help requires for Search to work; > always has. Not just for Arabic, but for any other > locale. > > Also, are all your HTML files in the correct Code > Page encoding, 1256? Unicode will NOT work for > HTML Help, though you may think it does. > > -- Jeremy H. Griffith, at Omni Systems Inc. >http://mif2go.com/ > > __ Information from ESET NOD32 Antivirus, version of virus signature > database 8004 (20130213) __ > > The message was checked by ESET NOD32 Antivirus. > > http://www.eset.com > > > >
OT: HTML Help Related Topics control and character encoding
On Wed, 13 Feb 2013 05:44:07 -0500, Jim Owens wrote: >We're using the HTML Help Related Topics ActiveX control. When we >create an with Arabic text for the title, the wrong characters >appear in the Topics Found dialog box, even when the system locale is >set to Arabic. Everything else in the compiled help uses the correct >Arabic characters, whether or not the system locale is set to Arabic. >The encoding used by our translator is windows-1256. > >Is there something we can try, or is this just a limitation of the control? When you comiled the Arabic CHM, did you do it on an Arabic system? NOT just one with the locale set? That's what HTML Help requires for Search to work; always has. Not just for Arabic, but for any other locale. Also, are all your HTML files in the correct Code Page encoding, 1256? Unicode will NOT work for HTML Help, though you may think it does. -- Jeremy H. Griffith, at Omni Systems Inc. http://mif2go.com/
Re: OT: HTML Help Related Topics control and character encoding
Thanks for the tips! I'll check them out. On 2013-02-13 12:10, Jeremy H. Griffith wrote: On Wed, 13 Feb 2013 11:32:23 -0500, Jim Owens wrote: Hi, Jeremy. I'm using SBAppLocale to compile (as recommended in the Mif2Go Guide!), and Search is working OK in Arabic. In fact, the Arabic is OK everywhere in the output -- The pages are all encoded with windows-1256. You're right on top of it, then. ;-) except for the Related Topics button text, and the link text in the Related Topics "Topics Found" dialog box. Setting aside the compilation, if I just open an HTML page in a browser, everything is in Arabic, except the text on the Related Topics button (which is in something like Cyrillic) and the text in the Related Topics dialog for the button (which is all question marks unless I set the system locale to Arabic, in which case it's something like Cyrillic). I wonder if there is a different version of the ActiveX control for different code pages? It sounds like it's not using the same one as the rest. See if there is a in the instance of the control in your HTML. MSDN has some very sketchy docs for it: http://msdn.microsoft.com/en-us/library/windows/desktop/ms644677%28v=vs.85%29.aspx but one of the values is the character set. They don't say what the syntax for that is, but I'd try 1256, CP1256, and cp-1256 to start. There are also advisories about a "security" "upgrade" from MS that broke this control at: http://www.helpwaregroup.com/system/app/pages/customSearch?scope=search-ns&q=Related+Topics+ActiveX HTH! -- Jeremy H. Griffith, at Omni Systems Inc. http://mif2go.com/ __ Information from ESET NOD32 Antivirus, version of virus signature database 8006 (20130213) __ The message was checked by ESET NOD32 Antivirus. http://www.eset.com ___ You are currently subscribed to framers as arch...@mail-archive.com. Send list messages to framers@lists.frameusers.com. To unsubscribe send a blank email to framers-unsubscr...@lists.frameusers.com or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to listad...@frameusers.com. Visit http://www.frameusers.com/ for more resources and info.
Re: OT: HTML Help Related Topics control and character encoding
On Wed, 13 Feb 2013 11:32:23 -0500, Jim Owens wrote: >Hi, Jeremy. I'm using SBAppLocale to compile (as recommended in the >Mif2Go Guide!), and Search is working OK in Arabic. In fact, the Arabic >is OK everywhere in the output -- > >The pages are all encoded with windows-1256. You're right on top of it, then. ;-) >except for the Related Topics button >text, and the link text in the Related Topics "Topics Found" dialog box. > >Setting aside the compilation, if I just open an HTML page in a browser, >everything is in Arabic, except the text on the Related Topics button >(which is in something like Cyrillic) and the text in the Related Topics >dialog for the button (which is all question marks unless I set the >system locale to Arabic, in which case it's something like Cyrillic). I wonder if there is a different version of the ActiveX control for different code pages? It sounds like it's not using the same one as the rest. See if there is a in the instance of the control in your HTML. MSDN has some very sketchy docs for it: http://msdn.microsoft.com/en-us/library/windows/desktop/ms644677%28v=vs.85%29.aspx but one of the values is the character set. They don't say what the syntax for that is, but I'd try 1256, CP1256, and cp-1256 to start. There are also advisories about a "security" "upgrade" from MS that broke this control at: http://www.helpwaregroup.com/system/app/pages/customSearch?scope=search-ns&q=Related+Topics+ActiveX HTH! -- Jeremy H. Griffith, at Omni Systems Inc. http://mif2go.com/ ___ You are currently subscribed to framers as arch...@mail-archive.com. Send list messages to framers@lists.frameusers.com. To unsubscribe send a blank email to framers-unsubscr...@lists.frameusers.com or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to listad...@frameusers.com. Visit http://www.frameusers.com/ for more resources and info.
Re: OT: HTML Help Related Topics control and character encoding
Hi, Jeremy. I'm using SBAppLocale to compile (as recommended in the Mif2Go Guide!), and Search is working OK in Arabic. In fact, the Arabic is OK everywhere in the output -- except for the Related Topics button text, and the link text in the Related Topics "Topics Found" dialog box. Setting aside the compilation, if I just open an HTML page in a browser, everything is in Arabic, except the text on the Related Topics button (which is in something like Cyrillic) and the text in the Related Topics dialog for the button (which is all question marks unless I set the system locale to Arabic, in which case it's something like Cyrillic). The pages are all encoded with windows-1256. On 2013-02-13 10:01, Jeremy H. Griffith wrote: On Wed, 13 Feb 2013 05:44:07 -0500, Jim Owens wrote: We're using the HTML Help Related Topics ActiveX control. When we create an with Arabic text for the title, the wrong characters appear in the Topics Found dialog box, even when the system locale is set to Arabic. Everything else in the compiled help uses the correct Arabic characters, whether or not the system locale is set to Arabic. The encoding used by our translator is windows-1256. Is there something we can try, or is this just a limitation of the control? When you comiled the Arabic CHM, did you do it on an Arabic system? NOT just one with the locale set? That's what HTML Help requires for Search to work; always has. Not just for Arabic, but for any other locale. Also, are all your HTML files in the correct Code Page encoding, 1256? Unicode will NOT work for HTML Help, though you may think it does. -- Jeremy H. Griffith, at Omni Systems Inc. http://mif2go.com/ __ Information from ESET NOD32 Antivirus, version of virus signature database 8004 (20130213) __ The message was checked by ESET NOD32 Antivirus. http://www.eset.com ___ You are currently subscribed to framers as arch...@mail-archive.com. Send list messages to framers@lists.frameusers.com. To unsubscribe send a blank email to framers-unsubscr...@lists.frameusers.com or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to listad...@frameusers.com. Visit http://www.frameusers.com/ for more resources and info.
Re: OT: HTML Help Related Topics control and character encoding
On Wed, 13 Feb 2013 05:44:07 -0500, Jim Owens wrote: >We're using the HTML Help Related Topics ActiveX control. When we >create an with Arabic text for the title, the wrong characters >appear in the Topics Found dialog box, even when the system locale is >set to Arabic. Everything else in the compiled help uses the correct >Arabic characters, whether or not the system locale is set to Arabic. >The encoding used by our translator is windows-1256. > >Is there something we can try, or is this just a limitation of the control? When you comiled the Arabic CHM, did you do it on an Arabic system? NOT just one with the locale set? That's what HTML Help requires for Search to work; always has. Not just for Arabic, but for any other locale. Also, are all your HTML files in the correct Code Page encoding, 1256? Unicode will NOT work for HTML Help, though you may think it does. -- Jeremy H. Griffith, at Omni Systems Inc. http://mif2go.com/ ___ You are currently subscribed to framers as arch...@mail-archive.com. Send list messages to framers@lists.frameusers.com. To unsubscribe send a blank email to framers-unsubscr...@lists.frameusers.com or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to listad...@frameusers.com. Visit http://www.frameusers.com/ for more resources and info.
OT: HTML Help Related Topics control and character encoding
We're using the HTML Help Related Topics ActiveX control. When we create an with Arabic text for the title, the wrong characters appear in the Topics Found dialog box, even when the system locale is set to Arabic. Everything else in the compiled help uses the correct Arabic characters, whether or not the system locale is set to Arabic. The encoding used by our translator is windows-1256. Is there something we can try, or is this just a limitation of the control?
OT: HTML Help Related Topics control and character encoding
We're using the HTML Help Related Topics ActiveX control. When we create an with Arabic text for the title, the wrong characters appear in the Topics Found dialog box, even when the system locale is set to Arabic. Everything else in the compiled help uses the correct Arabic characters, whether or not the system locale is set to Arabic. The encoding used by our translator is windows-1256. Is there something we can try, or is this just a limitation of the control? ___ You are currently subscribed to framers as arch...@mail-archive.com. Send list messages to framers@lists.frameusers.com. To unsubscribe send a blank email to framers-unsubscr...@lists.frameusers.com or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to listad...@frameusers.com. Visit http://www.frameusers.com/ for more resources and info.
