Hi Mary
> My monitor is not on a USB connection. It is a ViewSonic 17 in., connected to
> a custom-built computer: Pentium 4, 120 GB HD, 512 MB RAM. System properties
> says further, "Pentium (R) 4 CPU253GHz 255GHz 512 MB of RAM."
Doesn't seem as though we have much in common wrt hardware: Dell 1704FPT
(Digital) monitor (re-badged Samsung) attached to a Dell Precision WorkStation
370 with a 3.8GHz processor, 4GB (4x1GB SDRAM modules) and 2 Maxtor 7Y250M0
Serial-ATA/150 disks.
> Actually, I am not able to maintain my non-default color scheme. So, I gave
> up. It runs Windows Classic (Default blue, with large fonts). If I change it,
> Windows puts it back on the next reboot.
How annoying of Windows. :( But the large fonts stick? Weird. Also, I suspect, a
little OT. Might be able to assist PM if you'd like to get this fixed.
> Please keep asking the questions.
At the other end of the scale, I'm now wondering whether two single-byte
characters can look like one single Unicode character - ie, if that sequence of
bytes can represent more than one sequence of characters, depending on the
character set being used. I notice, for example, that often spaces are the
victims of this bug - although admittedly spaces are a very common character and
so statistically are more likely to be victims - and wonder whether the space
can combine - either mathematically or by concatenation - to form something
which then is undisplayable and so is cut from the editor view.
I have no idea whether that all was even remotely clear. Looked OK to me, but I
think an illustrative example or so might be in order here.
Eg 1: Character addition
Space (1-byte 0x20) added to M (1-byte 0x4D) would produce a 2-byte 0x006D.
Eg 2: Character concatenation
Space (1-byte 0x20) concatenated with M (1-byte 0x4D) would produce a 2-byte
0x204D.
If we can find common ground between the characters that disappear, perhaps that
will give more clues.
It's also possible that it's a buffering problem - this thought stemming from
the fact that longer messages seem more susceptible to the bug.
> I can't help believe the fault is somewhere in there, since this behavior came
> on with the testing of the new charsets. Before 3.51.3 I had no problems of
> this kind at all.
It certainly is recent. I'm out of other ideas for now. Perhaps if I get some
sleep I'll dream up some more. :)
--
Groetjes
Natasha
The Bat! 3.51.4 Pro on Windows XP Pro 5.1 Build 2600 Service Pack 2
________________________________________________________
Current beta is 3.51.4 | 'Using TBBETA' information:
http://www.silverstones.com/thebat/TBUDLInfo.html
IMPORTANT: To register as a Beta tester, use this link first -
http://www.ritlabs.com/en/partners/testers/
