"Erich E. Hoover" writes:
> +while(min <= max)
> +{
> +const char *encoded_symbol;
> +
> +pos = (min+max)/2;
> +encoded_symbol = html_encoded_symbols[pos].html_code;
> +dir = strncmp(encoded_symbol, amp, len);
On Thu, Jun 14, 2012 at 11:47 AM, Erich E. Hoover wrote:
> ...
> I can't think of any other way they'd be doing it... It honestly blew
> me away to see that screenshot, I wouldn't have thought to implement
> it that way in a million years.
The bug submitter was using xchm, so for completeness I
On Thu, Jun 14, 2012 at 11:44 AM, Alexandre Julliard
wrote:
> ...
> Wow, is Windows really doing it this way? That's a good contestant for
> the Most Stupid Win32 API Behavior award.
I can't think of any other way they'd be doing it... It honestly blew
me away to see that screenshot, I wouldn't
On Thu, Jun 14, 2012 at 11:22 AM, Alexandre Julliard
wrote:
> ...
>
> I don't see why you'd want to use ANSI code pages for this, since they
> will be converted to Unicode anyway.
It's important to use the ANSI code page because of the way the
characters are handled internally (you can see this i
"Erich E. Hoover" writes:
> On Thu, Jun 14, 2012 at 11:22 AM, Alexandre Julliard
> wrote:
>> ...
>>
>> I don't see why you'd want to use ANSI code pages for this, since they
>> will be converted to Unicode anyway.
>
> It's important to use the ANSI code page because of the way the
> characters a
"Erich E. Hoover" writes:
> Real Name:
> Erich Hoover
>
> Description:
> This patch adds the ability in HTML Help to convert HTML encoded
> characters (e.g. ê) into the Unicode character equivalent. This
> feature is needed by the table of contents and the index for
> displaying internat
