The toupper conversion *probably* isn't the problem, but for the record I
can imagine a situation in which this might happen. Many years ago, for
example, on Sun systems (Sun/OS, prior to Solaris) the toupper() and
tolower() macros in the C library were implemented in a rather odd way
(oriented towards performance rather than accuracy). One therefore got
unexpected results with some strings (I can't remember the details, but I
think it involved strings containing numerals or other non-alpha
characters). On the same systems (as I recall) the corresponding toupper()
and tolower() *functions* behaved as expected.
You just never know.
att393et.dat (196 Bytes)
ยทยทยท
--------------------------------------
Gary H. Merrill
Director and Principal Scientist, New Applications
Data Exploration Sciences
GlaxoSmithKline Inc.
(919) 483-8456
"Vaclav Slavik"
<vaclav.slavik@matfyz.c
>
To: wxPython-users@lists.wxwindows.org
01-Dec-2003 14:01 cc:
Please respond to Subject: Re: [wxPython-users] wxHtmlWindow mishandling <pre> tag
wxPython-users@lists.wx
windows.org
Hi,
Chris Barker wrote:
I had this problem, and it turned out that wxHtmlWindow was case
sensitive:
No, it isn't (never was). It had to be something else, because all
tags are converted to uppercase before the parser can see them. A
possible explanation is that wxToupper() (which is same as toupper()
C function in ANSI mode) didn't work, but I can't imagine any
situation when this would the case...
Vaclav
--
PGP key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x465264C9
(See attached file: att393et.dat)