So here's what I'm planning: Read all the stdin till we hit end-of-file, treat it as whatever type is specified on the command line, and process it as the home document.
Probably need two new command-line switches, --stdin-type="foo" and --stdin-url="foo", to allow you to specify the stdin Content-Type and URL data. The charset can be specified as part of --stdin-type, as per usual. We need a special home url to trigger this, too; perhaps --home-url="<stdin>". Sound reasonable? Bill > Yes, I was thinking of something like that myself. Sure, pretty easy > to do. > > Bill > > > > > While we're on the subject of using standard redirection in the > > parser, so we can do plucker-build [...] > foo.pdb, I wonder if we can also > > use the opposite for input. I have a need now to do things like: > > > > plucker-build [...] < $content_stream > > > > ..which is raw html itself, not a url reference or a file. Possible?
