Just downloaded and tested that application, it doesn't have any useful settings, except maybe for "Use .GIF transparency for smaller files", but that may lead to worse performance in large files. But I've performed some tests and it still creates 32bit frames despite the GIF transparency setting so it'd be of no use.
Frankly I don't know what formats this browser accepts, I know I don't have (nor want) Flash on my system so there may be no other feasible option for displaying animations directly in the/this browser. I also don't know of other (free) screen capturing applications that could create old-style GIFs (8bpp frames), if that could somehow avoid the memory leak.
[EDIT] See
here for a few screen capture applications.
[/EDIT] That's why I suggested - at least for the moment - the simpler option of placing a link to the GIF rather than embedding the image: people can open it in a new window/tab or download and view locally in an appropriate image viewer. I know it wouldn't be catchy but it would be safe. It's up to you.
On a brighter note, dead keys appear correctly now in the OSD with v3.81.
The only minor issue - if I can call it like that - is that in OSD they're behaving correctly as dead keys, that is they wait for a valid character to follow to form a composed character otherwise the caret doesn't advance, while in the typing window they're being placed directly and the caret advances - that is they don't actually behave like dead keys but like normal keys. I've mentioned this before in relation to layouts being set as default, seems to be a system issue. I'm not sure if the script should strictly follow system's behavior or it's just fine the way it works now. Thought I should mention it, is all.
Anyway, good job, you finally nailed it (at least for the RO layout) .
[EDIT] There still is one minor issue: OSD will not appear if user starts typing with a dead key right after script start. So if I wanted to type
ˇ^˘°˛·´˝¨¸ for a demo I'd have to type whatever other regular character first, otherwise there would be no OSD.
Something else that bugged me while trying to test some screencap applications: how on earth would one clear the OSD history? Everytime I tried to capture a demo a large string of whatever I typed previously would interfere. I want a clean OSD - how do I do it, apart from restarting the script?
Oh and while at that, Don't bother with GifCam, it yields same 32bit frames too despite the apparently useful menu at the Save button (split button is not available in XP, must right-click the button to get it) and its logic is stupid, it works in 'pause' mode so if you click Start/Stop a few times without saving it'll add to the frames, ending up with a huge, possibly unrelated pile of frames. No way to discard unwanted previous frames other than restarting it.
Others on the page linked above are .NET, either incompatible with XP or cloud-based. Apparently nobody can create plain old 4/8bpp GIFs nowadays.