On Mon, May 12, 2008 at 06:24:30PM +0100, Jeremy Henty wrote:
On Mon, May 12, 2008 at 12:20:45PM -0400, Jorge Arellano Cid wrote:
On Mon, May 12, 2008 at 03:52:59PM +0000, corvid wrote:
The consequences of not informing the outside world about the progress of dillo in any detail: http://wiki.linuxfromscratch.org/blfs/wiki/dillo2
Please feel free to write them to get that page back on track before somebody believes what was written. ;)
I have a BLFS Trac account so I can probably do it myself. But what should I change? At a glance:
* We *do* support FTP and HTTPS. * Change "can support cookies" to "supports cookies".
Yes, but https is basic. If a page has multiple images, the dialog window may spam the user once per image. That's why https went disabled for normal users, and experienced guys/devs were left the chance to enable it.
* "Dillo always interprets web pages as if they had the ISO-8859-1 encoding." True?
It depends on what dillo they talk about. It looks like a dillo2 page, and in that case, it's FLTK2-based, it has nothing to do with GTK1, glib nor GTK2, just FLTK2. The code is now a mixture of C/C++ instead of pure C, etc... It's important to make a difference between dillo1 (C lang, GTK1/glib, __unmantained__, and dillo2 (active branch). If we talk about dillo2 then the statement: "Dillo always interprets web pages as if they had the ISO-8859-1 encoding." is absolutely false.
* "useless for reading non-English web pages" Surely not true, though maybe "useless for reading multibyte-encoded pages" is true.
If we talk about dillo2, false again. Dillo2 uses utf-8 by default, and utf-8 is multibyte-encoded. On top of that we have all the work corvid put in the character decoding, so now dillo2 can decode a boat load of charsets into utf-8 using iconv. Non english pages render quite well provided you have the necessary fonts installed. There're a few exceptions as with those that render backwards or have collapsing glyphs. For instance, set: vw_fontname="DejaVu Sans" in ~/.dillo/dillorc2 and go to: http://www.gnu.org/home.fa.html Worth a thounsand words! then go to: http://www.gnu.org/ scroll to the bottom and you'll see plenty of non-english pages, that you can click into. If you go to: http://www.bds-bg.org/ you'll see windows-1251 charset handled properly by dillo. etc.
Anything else?
Yes, we should compile and provide this information from our web site. Otherwise it will be extremely hard for a non-developer to get right. A good diff document may be got from reviewing the Changelog alone. Here we have the record of all the work we've put in dillo2; from time to time I find there things forgotten long ago! I'll try to update some pages in the site as soon as I find some time. That's the point: lack of time/manpower. All the help is appreciated. Another very important point to be stated is that the plugins and the dpi daemon need to be installed for most things to work. After the build this is done with: make install-strip. Bottom line: current dillo2 is for developers. After we make a release it will be user ready. HTH. -- Cheers Jorge.-