OT: HTML Help Related Topics control and character encoding

2013-02-13 Thread Jim Owens
We're using the HTML Help Related Topics ActiveX control. When we create an Item 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,

Re: OT: HTML Help Related Topics control and character encoding

2013-02-13 Thread Jeremy H. Griffith
On Wed, 13 Feb 2013 05:44:07 -0500, Jim Owens jow...@magma.ca wrote: We're using the HTML Help Related Topics ActiveX control. When we create an Item 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.

Re: OT: HTML Help Related Topics control and character encoding

2013-02-13 Thread Jim Owens
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

Re: OT: HTML Help Related Topics control and character encoding

2013-02-13 Thread Jeremy H. Griffith
On Wed, 13 Feb 2013 11:32:23 -0500, Jim Owens jow...@magma.ca 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.

Re: OT: HTML Help Related Topics control and character encoding

2013-02-13 Thread Jim Owens
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 jow...@magma.ca 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

RE: OT: HTML Help Related Topics control and character

2013-02-13 Thread David Shaked
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

Re: OT: HTML Help Related Topics control and character encoding

2013-02-13 Thread Jim Owens
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 PARAM name=Font ... in the instance of the control in your HTML. MSDN has some

Re: OT: HTML Help Related Topics control and character

2013-02-13 Thread Jim Owens
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

OT: HTML Help Related Topics control and character encoding

2013-02-13 Thread Jim Owens
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,

OT: HTML Help Related Topics control and character encoding

2013-02-13 Thread Jeremy H. Griffith
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

OT: HTML Help Related Topics control and character encoding

2013-02-13 Thread Jim Owens
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

OT: HTML Help Related Topics control and character encoding

2013-02-13 Thread Jeremy H. Griffith
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

OT: HTML Help Related Topics control and character encoding

2013-02-13 Thread Jim Owens
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 >>

OT: HTML Help Related Topics control and character

2013-02-13 Thread David Shaked
> 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

OT: HTML Help Related Topics control and character encoding

2013-02-13 Thread Jim Owens
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

OT: HTML Help Related Topics control and character

2013-02-13 Thread Jim Owens
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