|
Posted by Jukka K. Korpela on December 30, 2005, 6:59 pm
Please log in for more thread options
> ftp -i -n ftp.server.com< <EOF
That's correct markup and works well, though it represents
ftp -i -n ftp.server.com< <EOF
which is not what you mean. Use
ftp -i -n ftp.server.com <<EOF
instead (i.e., move the space after the first < before it).
> If I leave the << to indicate I am using a Here document, then the WDG
> validator complains about all sorts of stuff.
Of course you must not write the "<" characters as such but e.g. "escape"
them as <. If you use them as such, <EOF will be parsed as starting a tag.
("Escaping" the first "<" isn't strictly necessary in HTML 4.01, but
surely a good idea.)
> If I use adjoining << with no space, then the first < displays,
> but the rest of the code example disappears.
That would be nasty bug in a browser, but we could probably find a workaround
rather easily (using dummy markup, such as <<span><</span>, might
help). So far, I can see no direct evidence of such a bug. I just tried on
Firefox 1.0.2, and it shows << correctly as <<.
> If I add a space between the two < < the code shows, but the use
> of the double << for a Here document isn't clearly shown.
Then there is no "<<" but "< <". That would be a poor workaround to a bug,
but I don't think there _is_ a bug.
> Live page is at http://ericlindsay.com/blog/200508.htm#5 and will show
> one of the three problems.
Well, it contains invalid markup, with <<EOF, so it is guaranteed to be
wrong.
--
Yucca, http://www.cs.tut.fi/~jkorpela/
Pages about Web authoring: http://www.cs.tut.fi/~jkorpela/www.html
| 
XML Sitemap