- Dillo-dev - lists.mailman3.com

[patch]: do not require Html_process_word()s argument to be null-terminated

by onepoint＠starurchin.org

Just to clarify, I wasn't expecting any speed-up from this, it was just a cleanup patch. I accept the point about the dangers of fragile APIs in general, but I don't find it very compelling in this particular case. Html_process_word() is called from only one place, and it's caller has to hack its around the entirely unnecessary requirement that the argument be null-terminated. I don't see that any API is damaged just by cleaning up this particular function call. Regards, Jeremy Henty

Sept. 15, 2010

Segmentation fault on startup

by jameslovejoy＠tiscali.co.uk

I can confirm that dillo runs successfully with fltk compiled with --disable-xft Thanks! On 14 Sep 2010, at 07:01, James Lovejoy <jameslovejoy(a)tiscali.co.uk> wrote: > Mostly I'm just doing this for educational purposes and I'll just sort of learn as I go along. From what you have told me I can pretty much say that the target system does not have fontconfig on it (I don't ever remember installing it). I will 1. Install it 2. Try fltk without xft. > > On 13 Sep 2010, at 21:23, "Benjamin Johnson" <obeythepenguin(a)gmail.com> wrote: > >> On Mon, 13 Sep 2010 15:49:39 -0400, James Lovejoy <jameslovejoy(a)tiscali.co.uk> wrote: >> >>> Where should fonts.confirm be and how can I make sure fontconfig is installed. >> >> Not meaning this personally, but are you *sure* you're experienced enough to roll your own distro? I used to do that kind of work myself, and two things you really need to know are (1) what every package on the system does, at least in very general terms; and (2) how to work with the base system's tools (package management, etc.) >> >> I believe fonts.conf is in /etc/fonts.d/ or /etc/fontconfig/ or some similar location; you should be able to find it using >> find /etc -name fonts.conf >> >> As far as checking if fontconfig is installed, see if you have /usr/bin/fc-cache or /usr/lib/libfontconfig* on your system. The easiest way to check for a package in general is to use your system's package management tools, but unfortunately I'm not that familiar with dkpg -- I've always used Slackware-based systems myself. >> >> ~Benjamin >> >> _______________________________________________ >> Dillo-dev mailing list >> Dillo-dev(a)dillo.org >> http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev > > _______________________________________________ > Dillo-dev mailing list > Dillo-dev(a)dillo.org > http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev

Sept. 14, 2010

[bug]: ignored CSS attributes on html element

by obeythepenguin＠gmail.com

On Tue, 14 Sep 2010 14:54:19 -0400, Johannes Hofmann <Johannes.Hofmann(a)gmx.de> wrote: > It took me a while to find out, but the reason is rather simple: > > The <html> is opened before the style is loaded (it's in <head> > after all). So at the time we call startElement() for <html>, we > don't have the style information. > > I didn't find anything in the CSS reference how to handle this case, > but major browsers seem to allow CSS for the html-element. > > We could somehow delay the startElement() call for <html> until > <head> is parsed completely, but I have to look for a way to make > this hack not too ugly... Suggestions welcome :-) > > Cheers, > Johannes Maybe treat it, for CSS purposes, like a second <body> tag? i.e. rather than delay startElement(), map CSS attributes assigned to "html" to some pseudo-element parsed just before <body>. That might be a really stupid idea, but it makes sense to me since that's how <html> usually behaves, CSS-wise. For example, on my own sites I use something like html { background: #202020; color: #202020; } body { background: white; width: 6in; margin: 2em auto 2em auto; padding: 1em 4em 1em 4em; border: 2px solid black; } to display the body as a white box against a black background. ~Benjamin

Sept. 14, 2010

[bug]: ignored CSS attributes on html element

by Johannes.Hofmann＠gmx.de

On Tue, Sep 14, 2010 at 07:26:53PM +0100, Jeremy Henty wrote: > On Mon, Sep 13, 2010 at 03:54:22PM -0400, Benjamin Johnson wrote: > > On Mon, 13 Sep 2010 15:42:17 -0400, Johannes Hofmann > > <Johannes.Hofmann(a)gmx.de> wrote: > > > > >Hm, I've never seen the "text" property in CSS, can you point me to > > >the place where it is documented? > > >Also in http://www.penny-arcade.com/2010/9/10/ I can't find the > > >string "text:" neither in the source nor in the stylesheet - am I > > >missing something? > > > > I'm guessing it's just a typo for "color". > > Yes, you're right. I'm bewildered as to how I could have messed that > up. But anyway, dillo ignores the "color" attribute on the html > element (as easily seen by changing "text" to "color" in the example I > gave and then experimenting with changing between "html" and "body"). > So, how to fix this? It took me a while to find out, but the reason is rather simple: The <html> is opened before the style is loaded (it's in <head> after all). So at the time we call startElement() for <html>, we don't have the style information. I didn't find anything in the CSS reference how to handle this case, but major browsers seem to allow CSS for the html-element. We could somehow delay the startElement() call for <html> until <head> is parsed completely, but I have to look for a way to make this hack not too ugly... Suggestions welcome :-) Cheers, Johannes > > Regards, > > Jeremy Henty > > _______________________________________________ > Dillo-dev mailing list > Dillo-dev(a)dillo.org > http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev

Sept. 14, 2010

[bug]: ignored CSS attributes on html element

by onepoint＠starurchin.org

On Mon, Sep 13, 2010 at 03:54:22PM -0400, Benjamin Johnson wrote: > On Mon, 13 Sep 2010 15:42:17 -0400, Johannes Hofmann > <Johannes.Hofmann(a)gmx.de> wrote: > > >Hm, I've never seen the "text" property in CSS, can you point me to > >the place where it is documented? > >Also in http://www.penny-arcade.com/2010/9/10/ I can't find the > >string "text:" neither in the source nor in the stylesheet - am I > >missing something? > > I'm guessing it's just a typo for "color". Yes, you're right. I'm bewildered as to how I could have messed that up. But anyway, dillo ignores the "color" attribute on the html element (as easily seen by changing "text" to "color" in the example I gave and then experimenting with changing between "html" and "body"). So, how to fix this? Regards, Jeremy Henty

Sept. 14, 2010

Segmentation fault on startup

by jameslovejoy＠tiscali.co.uk

Mostly I'm just doing this for educational purposes and I'll just sort of learn as I go along. From what you have told me I can pretty much say that the target system does not have fontconfig on it (I don't ever remember installing it). I will 1. Install it 2. Try fltk without xft. On 13 Sep 2010, at 21:23, "Benjamin Johnson" <obeythepenguin(a)gmail.com> wrote: > On Mon, 13 Sep 2010 15:49:39 -0400, James Lovejoy <jameslovejoy(a)tiscali.co.uk> wrote: > >> Where should fonts.confirm be and how can I make sure fontconfig is installed. > > Not meaning this personally, but are you *sure* you're experienced enough to roll your own distro? I used to do that kind of work myself, and two things you really need to know are (1) what every package on the system does, at least in very general terms; and (2) how to work with the base system's tools (package management, etc.) > > I believe fonts.conf is in /etc/fonts.d/ or /etc/fontconfig/ or some similar location; you should be able to find it using > find /etc -name fonts.conf > > As far as checking if fontconfig is installed, see if you have /usr/bin/fc-cache or /usr/lib/libfontconfig* on your system. The easiest way to check for a package in general is to use your system's package management tools, but unfortunately I'm not that familiar with dkpg -- I've always used Slackware-based systems myself. > > ~Benjamin > > _______________________________________________ > Dillo-dev mailing list > Dillo-dev(a)dillo.org > http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev

Sept. 14, 2010

Segmentation fault on startup

by obeythepenguin＠gmail.com

On Mon, 13 Sep 2010 15:49:39 -0400, James Lovejoy <jameslovejoy(a)tiscali.co.uk> wrote: > Where should fonts.confirm be and how can I make sure fontconfig is > installed. Not meaning this personally, but are you *sure* you're experienced enough to roll your own distro? I used to do that kind of work myself, and two things you really need to know are (1) what every package on the system does, at least in very general terms; and (2) how to work with the base system's tools (package management, etc.) I believe fonts.conf is in /etc/fonts.d/ or /etc/fontconfig/ or some similar location; you should be able to find it using find /etc -name fonts.conf As far as checking if fontconfig is installed, see if you have /usr/bin/fc-cache or /usr/lib/libfontconfig* on your system. The easiest way to check for a package in general is to use your system's package management tools, but unfortunately I'm not that familiar with dkpg -- I've always used Slackware-based systems myself. ~Benjamin

Sept. 13, 2010

Segmentation fault on startup

by jameslovejoy＠tiscali.co.uk

Where should fonts.confirm be and how can I make sure fontconfig is installed. On 13 Sep 2010, at 20:34, "corvid" <corvid(a)lavabit.com> wrote: > James wrote: >> If you check my prior email I have included an updated backtrace. On further examination of the source it looks to me like fltk is trying to hardcode my fonts?!? > > To the best of my knowledge, fltk::HELVETICA, COURIER, TIMES, etc., actually > meant Helvetica, Courier, Times, etc., with the old font system, > but with xft, they just mean sans, mono, serif, etc. > > And then in the fontconfig files, sans and friends are set > to some specific font (e.g., looking quickly in mine, it seems that > fonts.conf makes sans an alias for sans-serif, and then conf.d is full > of files that specify that, for the sans-serif family, here are a bunch > of specific font families in order of preference...). > > > _______________________________________________ > Dillo-dev mailing list > Dillo-dev(a)dillo.org > http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev

Sept. 13, 2010

[bug]: ignored CSS attributes on html element

by obeythepenguin＠gmail.com

On Mon, 13 Sep 2010 15:42:17 -0400, Johannes Hofmann <Johannes.Hofmann(a)gmx.de> wrote: > Hi, > Hm, I've never seen the "text" property in CSS, can you point me to > the place where it is documented? > Also in http://www.penny-arcade.com/2010/9/10/ I can't find the > string "text:" neither in the source nor in the stylesheet - am I > missing something? > > Regards, > Johannes I'm guessing it's just a typo for "color". ~Benjamin

Sept. 13, 2010

[bug]: ignored CSS attributes on html element

by Johannes.Hofmann＠gmx.de

Hi, On Sun, Sep 12, 2010 at 10:26:29PM +0100, Jeremy Henty wrote: > > Penny Arcade is illegible in Dillo[1]. The problem is that its CSS > sets the text attribute on the html element and Dillo ignores this, so > we get black text on blue instead of white text on blue. > > Here is a demo: > > <html> > <head> > <style type="text/css">html{text:#F00;}</style> > </head> > <body> > Blah, blah, blah > </body> > </html> > > The text is plain black, but if you change html to body in the CSS > then the text is red as it should be. > > Thoughts on how to fix this? It's not obvious to me whether this is a > one-liner patch or something more radical is needed. Hm, I've never seen the "text" property in CSS, can you point me to the place where it is documented? Also in http://www.penny-arcade.com/2010/9/10/ I can't find the string "text:" neither in the source nor in the stylesheet - am I missing something? Regards, Johannes

Sept. 13, 2010