- Dillo-dev - lists.mailman3.com

Fun with autocnf and mercurial

by joerg.sonnenberger＠web.de

On Tue, Feb 17, 2009 at 05:26:36PM +0000, Jeremy Henty wrote: > Yes, that's much better. Revised patch attached. Please ensure that this is not part of releases and/or if the .hg directory is missing. Joerg

Feb. 17, 2009

Fun with autocnf and mercurial

by onepoint＠starurchin.org

On Tue, Feb 17, 2009 at 05:26:29PM +0100, Hofmann Johannes wrote: > I like the idea, but wouldn't something like "hg id" be more > appropriate? It shows the current revision which is not necessarily > tip. Yes, that's much better. Revised patch attached. Regards, Jeremy Henty

Feb. 17, 2009

Fun with autocnf and mercurial

by Johannes.Hofmann＠gmx.de

On Mon, Feb 16, 2009 at 11:09:21PM +0000, Jeremy Henty wrote: > > Here's a patch for discussion. Since I am parsing Dillo logs for > debugging, I thought it would be neat if Dillo logged the mercurial > revision. Patch attached. > > Thoughts? Does anyone know a better way to get the revision for a > particular tag? Piping "hg tags" through a sed script is rather > kludgy but I can't find a way to get mercurial to tell me directly. I like the idea, but wouldn't something like "hg id" be more appropriate? It shows the current revision which is not necessarily tip. Cheers, Johannes

Feb. 17, 2009

Leaking image structures

by corvid＠lavabit.com

I wrote: > Probably not related, but occasionally progressive jpegs > haven't been displaying some of the later scans. It does this when the image is being scaled.

Feb. 17, 2009

META charset without MIME type

by corvid＠lavabit.com

Jorge wrote: > I also want to maybe re-use this widget for the XHTML parsing > dilemma. This is: to render or not to render XHTML. Last time I > read the specs, XHTML must be validated and not rendered when not > valid. In practice, when facing non-valid XHTML, Firefox renders > it and doesn't even warn. If we render, and warn, and show the > BUGs found in the bug-meter, we'd be closer to the original idea. From a little reading, I get the impression that it has to be well-formed in an xml sense to be rendered, but you can have HTMLish errors like, oh, putting random things in <select> and still render it.

Feb. 17, 2009

Fun with autocnf and mercurial

by onepoint＠starurchin.org

Here's a patch for discussion. Since I am parsing Dillo logs for debugging, I thought it would be neat if Dillo logged the mercurial revision. Patch attached. Thoughts? Does anyone know a better way to get the revision for a particular tag? Piping "hg tags" through a sed script is rather kludgy but I can't find a way to get mercurial to tell me directly. I log the qparent revision as well as the tip revision because I manage patches with Mercurial queues, so my qparent revision is the vanilla tip revision that I am currently based on. Also, I used printf() to log the revisions because neither MSG nor MSG_WARN produced anything. I don't know why. Can anyone explain? Regards, Jeremy Henty

Feb. 17, 2009

META charset without MIME type

by corvid＠lavabit.com

Jorge wrote: > Don't worry man. This is more or less cooked. > > From the link suggested by Rogut?s Sparnuotos: > > http://www.w3.org/TR/2008/NOTE-WCAG20-TECHS-20081211/G110.html > > I got to: > > http://www.w3.org/TR/2008/NOTE-WCAG20-TECHS-20081211/H76.html > > which is a W3C's page with an example that uses quotes. Ergo, > we will support it. Not parsing the major/minor part because the quotes confused us, though? The type could differ -- I remember that crash Jeremy found where meta changed it to application/xhtml+xml...

Feb. 16, 2009

META charset without MIME type

by jcid＠dillo.org

On Mon, Feb 16, 2009 at 07:41:05PM +0000, corvid wrote: > I wrote: > > Jorge wrote: > > > On Sun, Feb 15, 2009 at 11:11:59PM +0000, corvid wrote: > > > > Jorge wrote: > > > > > summary: Fixed handling of META's content-type with no MIME type > > > > > (e.g. only charset). > > > > > > > > Is that legal? It doesn't sound legal. > > > > > > Verbatim from HTML-4.01 SPEC: > > > > > > META: > > > [...] > > > content = cdata [CS] > > > > > > This attribute specifies a property's value. This specification > > > does not list legal values for this attribute. > > > > Right, MIME types are specified elsewhere and not here in the HTML spec. > > > > I imagine this has to do with furaisanjin's "'", and a quick look into > > the spec suggests that should be getting turned into a "'" if it's an > > attr. I'll see if I can find what's going on there. > > furaisanjin's was inside an attribute, and the content type one delimits > an attribute. So the spec says > > By default, SGML requires that all attribute values be delimited using > either double quotation marks (ASCII decimal 34) or single quotation > marks (ASCII decimal 39). Single quote marks can be included within > the attribute value when the value is delimited by double quote marks, > and vice versa. Authors may also use numeric character references to > represent double quotes (") and single quotes ('). > > And the question is whether that last sentence is talking about > attribute delimiters, attribute values, or both. I don't know! > It looks like a person would have to make the questionable decision > to digest the super-mega-horror that is SGML in order to find out. Don't worry man. This is more or less cooked. From the link suggested by Rogut?s Sparnuotos: http://www.w3.org/TR/2008/NOTE-WCAG20-TECHS-20081211/G110.html I got to: http://www.w3.org/TR/2008/NOTE-WCAG20-TECHS-20081211/H76.html which is a W3C's page with an example that uses quotes. Ergo, we will support it. Currently I'm in the process of implementing the "instant client-side redirect" thing, and also want to replace the custom HTML that's injected into the page (the META refresh warning) with a widget (most probably inside the control panel, hidden when not needed). I also want to maybe re-use this widget for the XHTML parsing dilemma. This is: to render or not to render XHTML. Last time I read the specs, XHTML must be validated and not rendered when not valid. In practice, when facing non-valid XHTML, Firefox renders it and doesn't even warn. If we render, and warn, and show the BUGs found in the bug-meter, we'd be closer to the original idea. Comments? -- Cheers Jorge.-

Feb. 16, 2009

META charset without MIME type

by corvid＠lavabit.com

I wrote: > Jorge wrote: > > On Sun, Feb 15, 2009 at 11:11:59PM +0000, corvid wrote: > > > Jorge wrote: > > > > summary: Fixed handling of META's content-type with no MIME type > > > > (e.g. only charset). > > > > > > Is that legal? It doesn't sound legal. > > > > Verbatim from HTML-4.01 SPEC: > > > > META: > > [...] > > content = cdata [CS] > > > > This attribute specifies a property's value. This specification > > does not list legal values for this attribute. > > Right, MIME types are specified elsewhere and not here in the HTML spec. > > I imagine this has to do with furaisanjin's "'", and a quick look into > the spec suggests that should be getting turned into a "'" if it's an > attr. I'll see if I can find what's going on there. furaisanjin's was inside an attribute, and the content type one delimits an attribute. So the spec says By default, SGML requires that all attribute values be delimited using either double quotation marks (ASCII decimal 34) or single quotation marks (ASCII decimal 39). Single quote marks can be included within the attribute value when the value is delimited by double quote marks, and vice versa. Authors may also use numeric character references to represent double quotes (") and single quotes ('). And the question is whether that last sentence is talking about attribute delimiters, attribute values, or both. I don't know! It looks like a person would have to make the questionable decision to digest the super-mega-horror that is SGML in order to find out.

Feb. 16, 2009

a policy for dillorc vs. style.css conflicts?

by corvid＠lavabit.com

Jorge wrote: > Now, if we're to put them in CSS, we must provide > well-commented sample stylesheets, and also give some directions > in the FAQ. It should be simple for the user to know how to set > his own stylesheet options without previous CSS knowledge, and > also how to disable the remote CSS when a page doesn't look good. > > It'd be great to specify, for instance, a "reading" stylesheet > (for low contrast and highcontrast) from our website and to let > the user tweak it. Then when he gets to a long page that he wants > to read (not just skim), he could disable remote CSS and use the > one he prefers. Some days ago, I started trying to put together a sample style sheet (attached). I got as far as putting in the things that I would find valuable to know, but I _have_ been exposed to CSS a bit in recent months, so it was hard to see how much would have to be spelled out to an intelligent layman and how much would be obvious from context and insulting to spell out. So I...I got stuck. (Strays from topic a bit: The world is filled with things aimed toward experts and filled with things aimed toward ignorant people who can be kept ignorant and separated from their money, but the intelligent layman does not have his needs met.)

Feb. 16, 2009