I should probably resist the bait here, but... Jorge wrote:

...

Is there any interest to support this target on a source code basis? I'd like to have a way to run dillo on Win*, but not sacrificing current portability [2], nor having to write a completely different code path for Win*.

I'll just say patches 2, 6, 7, 8, 9, 11, and maybe 14 will get you 85% of that, without sacrificing *any* existing portability, and with only minimal changes to the existing Dillo code: http://dillo-win32.sourceforge.net/dillo/dillo3-patches.php Patches 7 and 8, the sockets abstraction layer, are the big ones; the rest of them are small tweaks. The remaining 29 patches are things like UI tweaks and moving DPIs back into the browser, which you are free to leave out. Oh, and I do regularly test my code on Unix, if you're wondering: http://obeythepenguin.users.sourceforge.net/openbsd/files/screenshot.png http://dillo-win32.sourceforge.net/dillo/screenshots.php?closeup=unix-openbs...

An API that works in both would be a good solution. For instance, we know that some dpi servers already work in Win* (with cygwin). There may even be a way to achieve it natively, and I seem to recall the FLTK3 team had this in mind. It would be more than worth to ask them about their plans on the subject. Again, as I'm not a Win* developer, I don't qualify to lead this effort on the Win* side. HTH.

Well, frankly I don't think most of the current DPIs belong outside the browser in the first place, as I've explained here: http://dillo-win32.sourceforge.net/dillo/dpi.php (If I have any technical details about the implementation wrong, please let me know.) I have started work on a native Windows DPI patch if you'd like to see it, though I'm afraid it's not functional yet, and it's *very* ugly code. Regards, ~Benjamin