Re: FW: think you have a bug in CSS processing

[J.F. Groff]

Oh wait. Somebody already did the patch!

http://www.mail-archive.com/[EMAIL PROTECTED]/msg09502.html
http://article.gmane.org/gmane.comp.web.wget.patches/1867

I guess it's up to maintainers to decide whether to include this in
the standard wget distribution. In the meantime, hearty thanks to Ted
Mielczarek, you made my day!

 JFG

On 4/13/07, J.F. Groff <[EMAIL PROTECTED]> wrote:

Hi Tony,

> > Amazingly I found this feature request in a 2003 message to this very
> mailing
> > list. Are there only a few lunatics like me who think this should be
> included?
>
> Wget is written and maintained by volunteers. What you need to find is a
> lunatic willing to volunteer to write the code to support this feature
> request.

Heh, sure ! I'm lunatic enough to try... Fetching the code from svn as
I write this. But the docs page says:

At the moment the GNU Wget development tree has been split in two
branches in order to allow bugfixing releases of the feature-frozen
1.10.x tree while continuing the development for Wget 2.0 on the main
branch.

Anywhere I can look at planned features for the 2.0 branch? There's an
awful lot of items in the project's TODO list but no mention of CSS.
Shall I just add the feature request to the TODO first, or is there a
community process involved in picking candidate features?

Cheers,

  JFG

Re: FW: think you have a bug in CSS processing

[J.F. Groff]

Hi Tony,


> Amazingly I found this feature request in a 2003 message to this very
mailing
> list. Are there only a few lunatics like me who think this should be
included?

Wget is written and maintained by volunteers. What you need to find is a
lunatic willing to volunteer to write the code to support this feature
request.


Heh, sure ! I'm lunatic enough to try... Fetching the code from svn as
I write this. But the docs page says:

At the moment the GNU Wget development tree has been split in two
branches in order to allow bugfixing releases of the feature-frozen
1.10.x tree while continuing the development for Wget 2.0 on the main
branch.

Anywhere I can look at planned features for the 2.0 branch? There's an
awful lot of items in the project's TODO list but no mention of CSS.
Shall I just add the feature request to the TODO first, or is there a
community process involved in picking candidate features?

Cheers,

 JFG

RE: FW: think you have a bug in CSS processing

[Tony Lewis]

J.F.Groff wrote:

> Amazingly I found this feature request in a 2003 message to this very
mailing
> list. Are there only a few lunatics like me who think this should be
included?

Wget is written and maintained by volunteers. What you need to find is a
lunatic willing to volunteer to write the code to support this feature
request.

Tony

Re: FW: think you have a bug in CSS processing

[J . F . Groff]

Neil wrote:
> When giving it some thought I think a
> valid argument could be made that the string in the CSS document is not 
> exactly
> an URL but it is certainly URL-like.

The "URL-like strings" in CSS are actually standard URLs, either absolute or
relative, so they shouldn't be a big deal to handle. A caveat for the parser:
they can be quoted or unquoted and still work.
See http://www.w3.org/TR/CSS21/syndata.html#uri

Amazingly I found this feature request in a 2003 message to this very mailing
list. Are there only a few lunatics like me who think this should be included?

Cheers,

  JFG

FW: think you have a bug in CSS processing

[Tony Lewis]

From: Neil Smithline [mailto:[EMAIL PROTECTED] 
Sent: Saturday, March 31, 2007 9:44 PM
To: Tony Lewis
Subject: Re: think you have a bug in CSS processing

 

Oh - well if you don't support CSS processing then I guess I am making a new
request. I'm also suggesting a clarification to your documentation so that
this is clear.

-r --recursive

Recursive web-suck. According to the protocol of the URL, this can mean two
things. Recursive retrieval of a HTTP URL means that Wget will download the
URL you want, parse it as an HTML document (if an HTML document it is), and
retrieve the files this document is referring to, down to a certain depth
(default 5; change it with -l). Wget will create a hierarchy of directories
locally, corresponding to the one found on the HTTP server. 


At least at first glance , this seems to mean that the URL in the CSS
portion should be translated and downloaded. When giving it some thought I
think a valid argument could be made that the string in the CSS document is
not exactly an URL but it is certainly URL-like. I think there should be
some explicit documentation stating what is not covered. 

 

- Neil
 

On 3/31/07, Tony Lewis <[EMAIL PROTECTED]> wrote:

  [EMAIL PROTECTED] wrote:

 

> I think I found a bug in CSS processing.

I think you're making a new feature request (and one that we've seen before)
to ADD processing for CSS.

Tony