Re: rsync server
| From: | Jim Winstead | Date: | Sun, 19 May 2002 16:00:50 +0000 |
| Subject: | Re: rsync server | ||
| References: | 1 2 3 4 5 6 | Groups: | php.mirrors |
| Request: | Send a blank email to php-mirrors+get-10344@lists.php.net to get a copy of this message | ||
On Sun, May 19, 2002 at 03:36:07PM +0200, Gabor Hojtsy wrote:
> > > Well, I think I'll take a look at it on the weekend, if I'll have
> > > the time. It is more easiert, then it looks like. As the plain HTML
> > > and PHP versions of the manuals are just different in some added
> > > PHP code, and so we can add code to every page to detect a ?plain
> > > parameter, and so we can print out the manual in plain text ;)
> > > This way, we may also include some more sophisticated navigation
> > > in the printable version. I'll look at this, if I'll have the time.
> >
> > this isn't quite what i meant. use css, and no parameter is necessary.
> >
> > http://www.alistapart.com/stories/goingtoprint/
>
> The PHP files should now somehow, what CSS to use, this means a needed
> parameter for every file, or a session, or some more development then
> CVS. How would you remember the printed setting if user goes from
> page to page? And then the printed version needs no TOC menu and PHP.net
> navigation which is generated by the PHP files...
perhaps the article didn't do a good job explaining this: on an html
page, you can declare a stylesheet that is only used for printing.
in the browser, it looks as normal, but then the print stylesheet can
hide navigational elements, make the target of links be printed
alongside the link, etc.
(do a print preview of the article to see what i mean.)
jim