while we're on the subject of non-ASCII character sets: any possibility of netsurf eventually supporting hebrew and/or arabic correctly? is text rendering an issue for the core or something the platform implementations handle?
-- eliyahu
"Physical reality is consistent with universal laws. When the laws do not operate, there is no reality. All of this is unreal."
I'm afraid you're going to have to explain exactly what is wrong (except the obvious "overwriting the image"), as I can't read Arabic. However, I do notice that the characters appear to be different to what they are under NetSurf (and Firefox) under Linux.
I'm afraid you're going to have to explain exactly what is wrong (except the obvious "overwriting the image"), as I can't read Arabic. However, I do notice that the characters appear to be different to what they are under NetSurf (and Firefox) under Linux.
the main issue -- at least in the example you have above -- is that the text is backwards. the characters are being rendered left-to-right rather than right-to-left. also the vertical rendering could be improved, for example, certain characters should be slightly lower on the line than they are. the former is really important, the latter not so much.
the same two issues happen with hebrew, by the way, although there i rarely see the vertical issue. occasionally a 'nun sofit' is higher than it should be, but that's about it. so if you could open a bug for the netsurf team to recognize right-to-left languages, that would be awesome. admittedly i doubt there are that many RISC OS or amiga users in the near east, but, hey, you never know.
-- eliyahu
"Physical reality is consistent with universal laws. When the laws do not operate, there is no reality. All of this is unreal."
I found a useful test page http://www.madore.org/~david/misc/unitest/ I've just checked it on NetSurf (OS4 and GTK) and it looks more than just backwards to me, but I'm unfamiliar with the characters and the comparison block is in a different font
Just a small feature request: could the search string gadget become activated automatically upon opening the Find Text window? That would spare the user from having to click inside the gadget.
Just a small feature request: could the search string gadget become activated automatically upon opening the Find Text window? That would spare the user from having to click inside the gadget.
Just a small feature request: could the search string gadget become activated automatically upon opening the Find Text window? That would spare the user from having to click inside the gadget.
I see but wonder how the Find Text window (or the string gadget) are related to the popup menu bug report under the link? The window doesn't even use a popup menu...
No, unfortunately to write a test case I need to know what is causing it (as it doesn't show up in a simple contextmenus example), and to find out what is causing it I need a test case. Catch-22
I did read something about ActivateGadget being unsafe, but the suggested alternative showed up the problem too.
I see but wonder how the Find Text window (or the string gadget) are related to the popup menu bug report under the link? The window doesn't even use a popup menu...
I can't remember for sure whether I tried activating the find string gadget, however I definitely have for the URL one. What happens is it activates fine, but when the pop-up (context) menu is opened the whole thing either crashes with the Grim Reaper, or deadlocks (depending on the mood it is in). I have no idea what the link is between the gadget activation and the context menu.
You're right that it is a different window, which might make a difference, so I can try it but am not holding out much hope.
It happens because I'm passing a NULL back to the core for an empty clipboard. Either this is a core bug, or I'm supposed to be passing a pointer to a NULL. I'll raise it on the ML.
You're right that it is a different window, which might make a difference, so I can try it but am not holding out much hope.
It seems to be working, it's present in #820. I've made it so entering the text searches for the first occurrence immediately too, because clicking next with the mouse is a bit annoying.