- Dillo-dev - lists.mailman3.com

[Dillo-dev]about DilloHtmlParseMode

by Calvin Yu

hello all: Can you tell me the difference among these dillo html parse mode? DILLO_HTML_PARSE_MODE_INIT,DILLO_HTML_PARSE_MODE_STASH,DILLO_HTML_PARSE_MODE_STASH_AND_BODY,DILLO_HTML_PARSE_MODE_VERBATIM,DILLO_HTML_PARSE_MODE_BODY,DILLO_HTML_PARSE_MODE_PRE What do these parse mode mean? Especially, what is stash mode? Thank you very much!

Dec. 6, 2004

[Dillo-dev]Ugly fonts -- fixed

by Chris de Vidal

I honestly don't know what worked. This morning I commented out vw_fontname and reloaded Dillo and it worked! Apparently at some point in time I fixed the problem but because vw_fontname was set I didn't know when it was fixed. Now the default font looks great, like the screenshots. Compared to anti-aliased fonts of course it looks edgier and for some reason the screenshot's fonts look slightly less edgy, but it's far better than when I first started using it. Thanks to everyone! CD "You will exist forever. You and God are both in the universe to stay either as friends on his terms, or enemies on yours. Which it will be is proven in this life. And this life is a vapor. Two seconds, and we will be gone. Surely God means for our time on earth to count for something significant." -- John Piper in "Life as a Vapor." Read it here: http://www.desiringgod.org/library/onlinebooks_index.html#blv

Dec. 3, 2004

Re: [Dillo-dev]Ugly fonts

by Chris de Vidal

Thus spaketh higuita: > a font might be installed in the new system, but not installed > in the old X font system... this is your problem... I might agree, except I installed every font package on the KDE system onto the XFCE system. Xlsfonts and xfontsel shows the same output on both machines (see below). No, I think it's a matter of which GTK engine KDE is running. Strangely, XFCE 4 is GTK 2-based... The answer is probably in an obscure GTK config file somewhere. >> I don't think you mean xfontsel because that just lets me see what fonts >> look like, it doesn't show which my X server is using. > > nope, if a font show there, its installed and will show with > any problem as any aplication You might be right; the manpage *does* say xfonsel "displays the fonts known to your X server" but I haven't figured out how... I've only figured out how to show the number of matches (3022) and select an individual font and view it. xlsfonts showed me all of the fonts known to my X server but the output is identical on both systems. > so try it, check the bitstream vera fonts, they are good > fonts and should exist in all distros today > se if they look the same in xfontsel in both systems... Vera isn't an option under "fmly" on either system; it isn't even greyed out so that I could choose it if it were enabled. When I choose the bistream "fndry" and go to "fmly" I only see charter, courier, terminal. >> I compared font packages on both machines and ensured both had the same >> packages installed. Some were missing, so I installed them, updated >> the font cache, restarted X. No joy. > > restart the xfs also Oh yeah forgot to mention I did that too. >> xlsfonts shows exactly the same fonts on both machines. > > try to compare the output of some fonts in xfontsel > in both systems Actually, fonts in xfontsel on the KDE system all look crummy too... they look identical on both systems. Both systems now have exactly the same fonts. Xfontsel says "3022 names match" when I open it on both systems. Xlsfonts also matches (I did a diff on the output). I've installed the same font .deb packages. I just don't understand it. >> X on both machines are now using strictly xfs for fonts. > > also try in both systems with a new temporary user > and see if you get the same results... Worth a shot. > try to use the same desktop manager/window manager > for both also Sorry, I'm not installing a heavy window manager for a lightweight browser; there *has* to be some way to make it nice like I see in the screenshots without installing KDE. > also, try > xset fp default > xset fp rehash > and test it again... if the "good" machine start > outputting bad fonts also, its KDE that its adding > a font path that isnt in the default Same... did I also have to restart X + XFS? > KDE installs some fonts also in $HOME/.kde/share/fonts > or something like this, check if you dont have some > extra fonts in there in the good machine Negative, I did a case-insensitive search under .kde for a folder called "*font*" and came up empty. > finally, are you using the same debian "version" on both > machines? not woody and sid, right 8) Same. Also, same screen resolution and color depth. About the only difference between the two machines is KDE and XFCE. I refuse to use such bloatware on my fast work computer. It's the same reason I want Dillo to work well :) >> I think I'll just give up using Dillo for now... it hurts the eyes too >> much. > > also try in a debian mailling list Well, it's just taking up alot of time; I'll just give up for now. Thanks for the effort. Let me know if I have to restart X + XFS after running xset on the KDE machine. CD "You will exist forever. You and God are both in the universe to stay either as friends on his terms, or enemies on yours. Which it will be is proven in this life. And this life is a vapor. Two seconds, and we will be gone. Surely God means for our time on earth to count for something significant." -- John Piper in "Life as a Vapor." Read it here: http://www.desiringgod.org/library/onlinebooks_index.html#blv

Dec. 3, 2004

Re: [Dillo-dev]Ugly fonts

by higuita

On Wed, 1 Dec 2004 07:26:33 -0500 (EST), "Chris de Vidal" <Chris(a)deVidal.tv> wrote: > This must be related to the GTK 1.x engine that's used with XFCE 4. I say (...) > used by the menus at the top of Multi-Gnome-Terminal. But on GTK 2.x GTK1.x use the tradicional X fonts system GTK2.X use a new font system a font might be installed in the new system, but not installed in the old X font system... this is your problem... KDE also use the new system > I don't think you mean xfontsel because that just lets me see what fonts > look like, it doesn't show which my X server is using. nope, if a font show there, its installed and will show with any problem as any aplication its just really a program that calls X font system and asks for all fonts so try it, check the bitstream vera fonts, they are good fonts and should exist in all distros today se if they look the same in xfontsel in both systems... > I compared font packages on both machines and ensured both had the same > packages installed. Some were missing, so I installed them, updated the > font cache, restarted X. No joy. restart the xfs also > xlsfonts shows exactly the same fonts on both machines. try to compare the output of some fonts in xfontsel in both systems > X on both machines are now using strictly xfs for fonts. also try in both systems with a new temporary user and see if you get the same results... try to use the same desktop manager/window manager for both also also, try xset fp default xset fp rehash and test it again... if the "good" machine start outputting bad fonts also, its KDE that its adding a font path that isnt in the default KDE installs some fonts also in $HOME/.kde/share/fonts or something like this, check if you dont have some extra fonts in there in the good machine finally, are you using the same debian "version" on both machines? not woody and sid, right 8) > I think I'll just give up using Dillo for now... it hurts the eyes too much. also try in a debian mailling list good luck higuita -- Naturally the common people don't want war... but after all it is the leaders of a country who determine the policy, and it is always a simple matter to drag the people along, whether it is a democracy, or a fascist dictatorship, or a parliament, or a communist dictatorship. Voice or no voice, the people can always be brought to the bidding of the leaders. That is easy. All you have to do is tell them they are being attacked, and denounce the pacifists for lack of patriotism and exposing the country to danger. It works the same in every country. -- Hermann Goering, Nazi and war criminal, 1883-1946

Dec. 2, 2004

[Dillo-dev]Ugly fonts

by Chris de Vidal

This must be related to the GTK 1.x engine that's used with XFCE 4. I say that because the font in the type location box (Ctrl+L) has the same ugliness that Dillo renders websites with, and this font is the same as used by the menus at the top of Multi-Gnome-Terminal. But on GTK 2.x programs I get a nice anti-aliased font for the menus. J-Pilot, a GTK app, was recently converted from 1.x to 2.x. Before the upgrade fonts were terrible; now they're smooth. KDE must use a slightly different configuration for GTK 1.x apps; on the wife's computer, both Dillo and Multi-Gnome-Terminal use nice fonts for the menus, location box (Dillo, Ctrl+L), and when Dillo renders HTML. I have the same versions of GTK 1.x and 2.x on both machines. XFCE 4 is GTK 2.x-based. Do I *have* to install a heavy window manager to use a light web browser? Not fair :( Livio Baldini Soares wrote: > Chris, regarding your Debian box, make sure you have correctly > configured your '/etc/fonts/local.conf' configuration file. > Specifically, I have found that most Debian default installations > disable bitmapped fonts, due to the use of anti-aliased or truetype > fonts used in most applications and/or window managers. Uncomment the > lines around: <dir>/usr/X11R6/lib/X11/fonts</dir> > > After you do that, run: > > $ defoma-reconfigure > and > $ fc-cache -f No gold. > Another issue is that fonts with "odd" sizes are butt-ugly. In this > respect, try adding 0.1 to your "font_factor" variable in your dillorc > file (if it's 1.0 set it to 1.1, if it's 1.1 set it to 1.2, for > example). It usually makes very little difference in the final font > size, but makes it a _big_ difference in scalability. No difference. Thanks for the attempt. higuita wrote: > try > > "-misc-fixed-*-*-*--*-*-*-*-*-*-iso8859-1" Same. > probably kde installed truetype fonts... > try to do the xfontsel in that computer and compare > then I don't think you mean xfontsel because that just lets me see what fonts look like, it doesn't show which my X server is using. Jorge Arellano Cid said: > This is a problem with your machine's installed > fonts, not with Dillo. Never doubted that for a second, especially when exactly the same Dillo binary and config file worked at home. Just writing this list because I don't know where else to look. > I'm not a Debian user, but most probably you left out > a set of "legacy" fonts that Dillo requires. Wish that were true... I've installed every font package the other machine has. > Maybe the fastest solution is to check the font-specific .debs > of your wife's cpmputer against yours, once this is done update > the font cache, restart X and retry. I compared font packages on both machines and ensured both had the same packages installed. Some were missing, so I installed them, updated the font cache, restarted X. No joy. xlsfonts shows exactly the same fonts on both machines. X on both machines are now using strictly xfs for fonts. I think I'll just give up using Dillo for now... it hurts the eyes too much.

Dec. 1, 2004

Re: [Dillo-dev]Dillo doesn't work!! :(

by Jorge Arellano Cid

On Wed, Dec 01, 2004 at 10:50:23AM +0100, Andrea Spadaccini wrote: > higuita wrote: > > > > dillorc:98: unexpected string constant "force_visited_color", expected > > > symbol > > > > comment this line as dillo dont recognise it, as its useless > > done > > > > dpi_socket_dir.c:61: tst_dir: access : No such file or directory > > > - /tmp/andrea-0c137u/ > > > debug_msg - init_sockdir: The socket directory > > > /tmp/andrea-0c137u does not exist > > > or is not a directory dpid.c:500: init_all_dpi_sockets: bind : > > > Address already in use/tmp/andrea-3vbac6/bookmarks.dpi > > > > try removing this directory and kill any dillo and > > dpi server and try again... > > [andrea@iridiumII andrea]$ ls /tmp/ > gconfd-andrea/ orbit-andrea/ sylpheed-1000= xmms_giorgia.0= > mc-root/ session_mm_apache0.sem xmms_andrea.0= xmms_luther.0= > [andrea@iridiumII andrea]$ dillo > dillo_dns_init: Here we go! > Disabling cookies. > Nav_open_url: Url=>about:splash< > Nav_open_url: Url=>dpi:/bm/< > dpi_socket_dir.c:61: tst_dir: access : No such file or directory > - /tmp/andrea-u1ua5k/ > debug_msg - init_sockdir: The socket directory /tmp/andrea-u1ua5k does not exist > or is not a directory dpid.c:500: init_all_dpi_sockets: bind : Address already > in use/tmp/andrea-69f7lb/bookmarks.dpi > dpid started > Capi_dpi_conn_timeout:: try 1 > main.c:153: get_command: dpid tag is NULL > : main.c:326: main: get_command failed > : > ** ERROR **: file main.c: line 351 (main): assertion failed: (numsocks >= 0) > aborting... > waitpid: No child processes > IO_write_chunk: Pipe rotta > Dillo: normal exit! > > > > if it still fails, try to strace the dillo to > > see if you find any tip why its failing > > I did it, but I didn't understand anything!!!! > > > also, if still fails, try to do a netstat -lp and > > see if that sockets are still in use and by who. > > [andrea@iridiumII andrea]$ su > Password: > [root@iridiumII andrea]$ netstat -lp > Active Internet connections (only servers) > Proto Recv-Q Send-Q Local Address Foreign Address State > PID/Program name tcp 0 0 *:x11 *:* > LISTEN 164/X tcp 0 0 *:http > *:* LISTEN 112/httpd Active UNIX domain > sockets (only servers) Proto RefCnt Flags Type State I-Node > PID/Program name Path unix 2 [ ACC ] STREAM LISTENING 284 > 232/sylpheed /tmp/sylpheed-1000 unix 2 [ ACC ] STREAM > LISTENING 132 164/X /tmp/.X11-unix/X0 > > > maybe you have a locked/sleeping dpi server somehere > > [root@iridiumII andrea]$ ps aux | grep dp > root 164 4.2 9.7 116544 37764 ? R 10:16 1:24 X -dpi 120 > > > > i'm using slackware 10.0 and dillo is working fine > > here > > :( > Can you give me some other tip, please? > What should I find when I strace dillo? An easier approach would be to follow the directions of: Q: After the upgrade I got: "ERROR: can't start dpid daemon!" in the FAQ. From this lines: > dpi_socket_dir.c:61: tst_dir: access : No such file or directory > - /tmp/andrea-u1ua5k/ > debug_msg - init_sockdir: The socket directory /tmp/andrea-u1ua5k does not ex > or is not a directory dpid.c:500: init_all_dpi_sockets: bind : Address alread > in use/tmp/andrea-69f7lb/bookmarks.dpi It's clear there're conflicts with the directory and an old dpi server. The directory names are different and there's a bound address for bookmarks. -- Cheers Jorge.-

Dec. 1, 2004

Re: [Dillo-dev]Dillo doesn't work!! :(

by Andrea Spadaccini

higuita wrote: > > dillorc:98: unexpected string constant "force_visited_color", expected > > symbol > > comment this line as dillo dont recognise it, as its useless done > > dpi_socket_dir.c:61: tst_dir: access : No such file or directory > > - /tmp/andrea-0c137u/ > > debug_msg - init_sockdir: The socket directory > > /tmp/andrea-0c137u does not exist > > or is not a directory dpid.c:500: init_all_dpi_sockets: bind : > > Address already in use/tmp/andrea-3vbac6/bookmarks.dpi > > try removing this directory and kill any dillo and > dpi server and try again... [andrea@iridiumII andrea]$ ls /tmp/ gconfd-andrea/ orbit-andrea/ sylpheed-1000= xmms_giorgia.0= mc-root/ session_mm_apache0.sem xmms_andrea.0= xmms_luther.0= [andrea@iridiumII andrea]$ dillo dillo_dns_init: Here we go! Disabling cookies. Nav_open_url: Url=>about:splash< Nav_open_url: Url=>dpi:/bm/< dpi_socket_dir.c:61: tst_dir: access : No such file or directory - /tmp/andrea-u1ua5k/ debug_msg - init_sockdir: The socket directory /tmp/andrea-u1ua5k does not exist or is not a directory dpid.c:500: init_all_dpi_sockets: bind : Address already in use/tmp/andrea-69f7lb/bookmarks.dpi dpid started Capi_dpi_conn_timeout:: try 1 main.c:153: get_command: dpid tag is NULL : main.c:326: main: get_command failed : ** ERROR **: file main.c: line 351 (main): assertion failed: (numsocks >= 0) aborting... waitpid: No child processes IO_write_chunk: Pipe rotta Dillo: normal exit! > if it still fails, try to strace the dillo to > see if you find any tip why its failing I did it, but I didn't understand anything!!!! > also, if still fails, try to do a netstat -lp and > see if that sockets are still in use and by who. [andrea@iridiumII andrea]$ su Password: [root@iridiumII andrea]$ netstat -lp Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 *:x11 *:* LISTEN 164/X tcp 0 0 *:http *:* LISTEN 112/httpd Active UNIX domain sockets (only servers) Proto RefCnt Flags Type State I-Node PID/Program name Path unix 2 [ ACC ] STREAM LISTENING 284 232/sylpheed /tmp/sylpheed-1000 unix 2 [ ACC ] STREAM LISTENING 132 164/X /tmp/.X11-unix/X0 > maybe you have a locked/sleeping dpi server somehere [root@iridiumII andrea]$ ps aux | grep dp root 164 4.2 9.7 116544 37764 ? R 10:16 1:24 X -dpi 120 > i'm using slackware 10.0 and dillo is working fine > here :( Can you give me some other tip, please? What should I find when I strace dillo? Thanks for your help! > ciao Are you Italian too? Ciao :) -- [ Andrea Spadaccini a.k.a. Lupino / Lupin85 - from Catania ] [ MAIL: lupin85(at)email.it - ICQ: 91528290 - Linux 2.4.22 ] [ Linux Registered User #313388 - Powered by Slackware 9.1 ] -- Email.it, the professional e-mail, gratis per te: http://www.email.it/f Sponsor: Difendi la tua casella di posta dai virus e dallo spam, prendi Email.it Pro15, Pro50 o Pro100 la casella professionale e sicura. Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=1048&d=1-12

Dec. 1, 2004

Re: [Dillo-dev]Re: dillo: umask(0) in dpid/main.c?

by Jeremy Henty

On Tue, Nov 30, 2004 at 03:10:50PM -0300, Jorge Arellano Cid wrote: > On Sun, Nov 28, 2004 at 01:03:23PM +0100, Richard Zidlicky wrote: > > > Is there still a good reason to set umask to 0 for all plugins? > > ... it makes much more sense to use 077 as a mask for dpis > (i.e. only allowing the owner). > > Comments are welcome. Well, I'd vote for 077. World-writable files give me the willies. Cheers, Jeremy

Dec. 1, 2004

Re: [Dillo-dev]Dillo doesn't work!! :(

by higuita

On Tue, 30 Nov 2004 01:04:35 +0100, Andrea Spadaccini <lupin85(a)email.it> wrote: > dillorc:98: unexpected string constant "force_visited_color", expected > symbol comment this line as dillo dont recognise it, as its useless > dpi_socket_dir.c:61: tst_dir: access : No such file or directory > - /tmp/andrea-0c137u/ > debug_msg - init_sockdir: The socket directory > /tmp/andrea-0c137u does not exist > or is not a directory dpid.c:500: init_all_dpi_sockets: bind : > Address already in use/tmp/andrea-3vbac6/bookmarks.dpi try removing this directory and kill any dillo and dpi server and try again... if it still fails, try to strace the dillo to see if you find any tip why its failing also, if still fails, try to do a netstat -lp and see if that sockets are still in use and by who. maybe you have a locked/sleeping dpi server somehere i'm using slackware 10.0 and dillo is working fine here ciao -- Naturally the common people don't want war... but after all it is the leaders of a country who determine the policy, and it is always a simple matter to drag the people along, whether it is a democracy, or a fascist dictatorship, or a parliament, or a communist dictatorship. Voice or no voice, the people can always be brought to the bidding of the leaders. That is easy. All you have to do is tell them they are being attacked, and denounce the pacifists for lack of patriotism and exposing the country to danger. It works the same in every country. -- Hermann Goering, Nazi and war criminal, 1883-1946

Dec. 1, 2004

[Dillo-dev]Re: dillo: umask(0) in dpid/main.c?

by Jorge Arellano Cid

On Sun, Nov 28, 2004 at 01:03:23PM +0100, Richard Zidlicky wrote: > Hi, Hi. > I stumbled upon this as I noticed that bookmarks and saved files > are world writable. Is there still a good reason to set umask > to 0 for all plugins? Good question! Basically the umask(0) call is there because the "Linux Programming Second Edition Unleashed" recommends so as a standard for daemons ;). Now, looking into it, it makes much more sense to use 077 as a mask for dpis (i.e. only allowing the owner). > > Another detail I noticed while checking file creation > is this: > --- dillo-0.8.3/src/cookies.c.rz 2004-11-28 12:39:33.000000000 +0100 > +++ dillo-0.8.3/src/cookies.c 2004-11-28 12:40:22.000000000 +0100 > @@ -100,7 +100,7 @@ > > if ((F_in = fopen(filename, "r+")) == NULL) { > /* Create the file */ > - fd = open(filename, O_WRONLY | O_CREAT | O_TRUNC, S_IRUSR | S_IWUSR); > + fd = open(filename, O_WRONLY | O_CREAT | O_TRUNC, S_IRUSR | S_IWUSR, 0777); > if (fd != -1) { > if (init_str) > write(fd, init_str, strlen(init_str)); Well, with the proper mask set to 0077 this would not be required. If the need to add explicit permissions arise, it'd be 0077 too. Comments are welcome. -- Cheers Jorge.-

Nov. 30, 2004