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 sketch
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
>>
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 o
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
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 as
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 t
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 eve
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 o
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 a
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 t
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, wheth
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, wheth
12 matches
Mail list logo
