- Dillo-dev - lists.mailman3.com

[Dillo-dev]Re: null byte in HTML
by Jorge Arellano Cid May 13, 2004

May 13, 2004

---------- Forwarded message ---------- Date: Thu, 13 May 2004 12:33:13 +0300 (EEST) From: Jukka K. Korpela <jkorpela(a)cs.tut.fi> To: Jorge Arellano Cid <jcid(a)dillo.org> Subject: Re: Is the null byte allowed in HTML? On Wed, 12 May 2004, Jorge Arellano Cid wrote: > I can't yet found whether the null byte character is allowed in > HTML. Can you shed some light on this? It is not. You could use http://validator.w3.org to check for disallowed characters (it reports "non SGML character number 0"), but the ultimate reference is a) for HTML 4, the SGML declaration http://www.w3.org/TR/html4/sgml/sgmldecl.html where UNUSED effectively means 'disallowed' b) for XHTML, the XML specification, see http://www.w3.org/TR/REC-xml/#charsets which say, among other things, that all characters below 9 (HT) are disallowed. Thanks for a good question - I'm just finalizing a book on XHTML (in Finnish, sorry) and I realized that I had forgotten to discuss the character issue in sufficient detail. (I just realized that various generators may produce data with control characters.) -- Jukka "Yucca" Korpela, http://www.cs.tut.fi/~jkorpela/

2 1

[Dillo-dev]null byte in HTML
by Jorge Arellano Cid May 12, 2004

May 12, 2004

Hi there! Does anyone know whether a null-byte ('\0') is allowed inside HTML or SGML or XML? Cheers Jorge.-

1 0

[Dillo-dev]download problem on OpenBSD
by Riccardo Mottola May 11, 2004

May 11, 2004

Hello, using pre2 I went to sourceforge do download a file. On the mirror page I selected one and clicked on the "here" message for the non-stadard refresh which gives a direct link to the file (I could use it for d/l with wget). Clicking on it brought up a file location requester, I selected my home directory and gave ok. Dillo crashed with: Nav_open_url: Url=>http://prdownloads.sourceforge.net/ayttm/ayttm-0.4.6.tar.gz?use_mirror=hean…< Connecting to 66.35.250.217 Nav_open_url: Url=>http://heanet.dl.sourceforge.net/sourceforge/ayttm/ayttm-0.4.6.tar.gz< Dns_server [0]: heanet.dl.sourceforge.net is 0x721cb8 Connecting to 193.1.219.87 HTTP warning: Unhandled MIME type: <application/x-gzip> dpi.c:71: a_Dpi_rd_dpi_socket_dir: fopen : No such file or directory - /home/multix/.dillo/dpi_socket_dir debug_msg - init_sockdir: The dpi_socket_dir file does not exist dpid started Riccardo

2 2

Re: [Dillo-dev]dillo interface and motif, athena etc
by Riccardo Mottola May 11, 2004

May 11, 2004

david feldman wrote: > > I think your questions are very good, I hope you get good answer! > unfortunately there was no follow up. I wonder if anyone else beside you was interested. -R

2 1

[Dillo-dev]BUG#522
by Jorge Arellano Cid May 10, 2004

May 10, 2004

Hi, Can anyone reproduce BUG#522? 522 Impact: soft error At: run time Type: crash Comments: Url=>http://www.rti-zone.org/dillo/Html.testsuite/jorge/c2.html< Gdk-ERROR **: BadValue (integer parameter out of range for operation) serial 4689 error_code 2 request_code 45 minor_code 0 HTReproduce: debian unstable WorkedBy: nobody Cheers Jorge.-

2 1

Re: [Dillo-dev]BUG#522
by Jorge Arellano Cid May 10, 2004

May 10, 2004

On Mon, 10 May 2004, Riccardo Mottola wrote: > Jorge Arellano Cid wrote: > > > > Hi, > > > > Can anyone reproduce BUG#522? > > [...] > > No I cannot reproduce it on solaris. > > I compiled dillo on Solaris, UltraSparc too (alyazs solaris 2.6, gcc > 3.3) You might add this to the compatibility list too. So we have: Solaris 2.6, gcc 3.3, Sparc v8 processor (=32bit) Solaris 2.6, gcc 3.3, UltraSparc (64bit?) What SunOS do they report? Cheers Jorge.-

1 0

[Dillo-dev]dillo-0.8.1-pre2.tar.bz2
by Jorge Arellano Cid May 10, 2004

May 10, 2004

Hi there! It took a long time, but finally, dillo-0.8.1-pre2.tar.bz2 is ready for download. The problem was that the patch for the problem of left-clicking an unhandled MIME type involved changes, inside the cache module, that were not trivial. I pondered the situation carefully trying to decide whether to make the patch and delay the next release, or leave it for 0.8.2. After studying the situation and developing a patch, important changes were made in the cache (for instance all the cached URLs use new code now, and the main scheduler was also changed, and the posibility of deleting an active URL-transfer was made possible). After all that, it only remained to offer a download dialog for the aborted transfer, and as the patch was already major, I went ahead and the result was one of those improvements you can't leave out. What does it do? well, now you can left-click on any URL; if it happens to be of an unhandled MIME type, the transfer is aborted, and a download dialog appears to offer the possibility of saving the resource locally. Simple and clean. Now you can click carelessly on those fake-download links from SF until you reach the real source ;). The tradeoff: the possibility of labelling this release as "beta stable" is not as clear as before. This tarball requires plenty of testing, so please download it and give it a hard time! Any use of the browser serves, specially testing the new download feature and multiple windows at the same time. Get it from: http://www.dillo.org/download/dillo-0.8.1-pre2.tar.bz2 and report back to dillo-dev. Cheers Jorge.- PS: Kudos are also welcome! ;)

3 6

[Dillo-dev]compile problems on AIX + gcc
by Riccardo Mottola May 7, 2004

May 7, 2004

Hello, I'm trying to compile 0.8.1-pre1 on AIX 4.1 : One never knows, maybe som4e progress was made :) I had still to use CFLAGS="-lpthreads" to have configure pthread working at configure. I notice the following warnings gcc -DHAVE_CONFIG_H -I. -I. -I.. -DDILLORC_SYS='"/usr/local/etc/dillorc"' -I/u sr/local/include -I/usr/local/include/gtk-1.2 -I/usr/local/include/glib-1.2 -I/u sr/local/lib/glib/include -lpthreads -D_REENTRANT -D_THREAD_SAFE -Wall -Waggreg ate-return -c `test -f 'dw_bullet.c' || echo './'`dw_bullet.c gcc: -lpthreads: linker input file unused since linking not done should I have used LDFLAGS or something else? isn't there a more elegant solution to work around this pthread regnition problem? like a configure option? Cheers, Riccardo

1 0

[Dillo-dev]Re: about gtk on solaris 2.6
by Jorge Arellano Cid May 6, 2004

May 6, 2004

Riccardo, On Thu, 6 May 2004, Riccardo Mottola wrote: > > Hey Jorge, > > just a quick precisation. On the box where i have the old 0.7.3 dillo > which gives GTK errors, I have GIMP installed and that one works fine, I > have edited quite some images. > > SO I suspect it is something in the way dillo calls GTK that could > trigger the error, before saying GTK is bugged on that platform totally. There may be some good news for you: Try this patch: diff -pru dillo/src/dillo.c dillo-0.8.0/src/dillo.c --- dillo/src/dillo.c 2004-04-21 16:47:34.000000000 -0400 +++ dillo-0.8.0/src/dillo.c 2004-05-06 11:11:31.000000000 -0400 @@ -216,6 +216,8 @@ gint main(int argc, char *argv[]) /* Initialize GUI and parse GTK related args */ gtk_init(&argc, &argv); gdk_rgb_init(); + gtk_widget_set_default_colormap (gdk_rgb_get_cmap()); + gtk_widget_set_default_visual (gdk_rgb_get_visual()); /* Handle command line options */ while ((opt_flg = Dillo_get_opt(Options, argc, argv, &opt_argv, &idx))) { It fixes the colormap and visual detection/settings on some systems. The documentation is a bit vague about this calls, they are deprecated now, formerly suggested as initialization for most cases and removed from theGTK+2.0 API (with compatibility defines). If you're lucky, it may help with AIX too. Please test it and report. Note: The patch is in CVS now, but use a "pre1" patched tarball for the test. That asserts the use of the same configure script. Cheers Jorge.-

1 0

[Dillo-dev]downloads and pre2
by Jorge Arellano Cid May 6, 2004

May 6, 2004

On Tue, 4 May 2004, Yves de Champlain wrote: > Hi > [...] > Everything works fine except for this : > > av_open_url: Url=>http://ftp.gnu.org/gnu/ddd/ddd-3.2.1.tar.gz< > Connecting to 199.232.41.7 > warning: Unhandled MIME type: <application/x-tar> > > ** CRITICAL **: file web.c: line 57 (a_Web_dispatch_by_type): assertion > `dw != NULL' failed. > > Of course, this does not start any download but after this, > I still get messages in the shell but I will > not have those from wget once I do "save link as" > like I have if I do "save link as" before. Effectively, a left click on a non-dillo-viewable MIME type URL triggers this error message. The code inside dillo assigns it to a "null-client" which means it continues to download but it's "ignored". This has some side effects, one of them is the transfer not being aborted (so it continues wasting bandwidth and memory). It also keeps a cache entry, so when a dpi download is requested it hits and gets fed from the cache! (not from a dpi). That's clearly a bug. This days I've been reviewing the code with a view to patch it, but it seems that a full patch (aborting the transfer, cleaning the cache entry, stopping the clients and offering a download dialog) may be too complex to debug in this pre-release testing stage. Aborting the download (which would allow for the later dpi download) looks simpler. I'm currently working on this. That, plus the two patches in CVS seem to round "pre2" and most probably become 0.8.1. Cheers Jorge.-

1 0