On Tue, Jan 15, 2008 at 12:34:12AM +0100, Thomas-Martin Seck wrote:
* Jorge Arellano Cid (jcid@dillo.org):
On Sun, Jan 13, 2008 at 05:07:04PM +0100, Thomas-Martin Seck wrote:
I'd like to know in what sense it looks "promising" to you.
It can deal with UTF8 now :) But wait, I just noticed that the window title is not decoded correctly if it contains special characters, cf <http://www.heise.de/newsticker/meldung/101768> (notice the "?" in "B?rse").
This is a known problem that only happens with window managers that use the WM_ICON_NAME instead of the _NET_WM_ICON_NAME property. I think this is a fltk bug (try the editor from the fltk/test directory and "save as" with a filename that contains special chars). I had sent a mail to the fltk list, but there seemed to be no consensus about my proposed fix. Johannes
No seriously, I like to have a fast, graphical, no-frills browser that allows me to read "non-active" UTF8 content since more and more content generation systems use it instead of plain ISO8859-1. What I like to see is frames support and CSS and if this is in the works I will happily waiting for it to mature -- and I am sure it will, now that a small but determined community seems to be (re-)forming.
What I do not really crave for is scripting or support for active content like Flash or Jave; if all else fails, I can use Opera or FF for "demanding" sites.
Unfortunately, I cannot help much with developing the core browser but offer to maintain the FreeBSD "port" of dillo2 once you consider to release it and try help with FreeBSD specific build or packaging issues. Well, as long as it does not break things for others, of course :)
_______________________________________________ Dillo-dev mailing list Dillo-dev@dillo.org http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev