Re: FW: think you have a bug in CSS processing
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
RE: FW: think you have a bug in CSS processing
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
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
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
think you have a bug in CSS processing
I think I found a bug in CSS processing. This was auto-generated and I'm far
from a CSS expert (quite the opposite). But, as far as I can tell (see
snippet below), it is supposed to be loaded from a directory named - that
is off of the main URL. For example, if the origination site is
http://www.foo.com, the GIF will be at
http://www.foo.com/-/includes/styles/swirl/skin_swirl_grey_top.gif. The
below text is came from the converted HTML file on the destination site.
You'll notice that the URL was not converted to an absolute URL pointing to
www.foo.com but neither was the GIF copied to the destination site. I've
done a find and it is nowhere to be found.
This really isn't a big deal for me as it is only one file and I've just
manually copied it over, but it does seem to be a bug worthy of fixing. If
you need more data, you can look at www.smithline.net. The snippet comes
from that page which was created using google page creator (don't ask me why
- it is definitely far from being ready for prime time) and then wget'ed
over to smithline.net.
Feel free to ping me should you need more info - Neil
PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/bin:/home/neils/bin wget
--mirror --force-html --convert-links --no-parent
--directory-prefix=/home/neils/smithline.net/data --quiet --recursive
--no-host-directories http://www.smithline.net-a.googlepages.com
#container {
padding: 0px;
background:URL(/-/includes/style/swirl/skin_swirl_grey_top.gif)
no-repeat top left;
background-color:#dfdfdf;
margin:0px auto;
}
