encode/decode filters

[James Walker]

The input of an encode filter is a file in the working directory that is 
being committed, correct?  If so, then why does the "tempfile:" form of 
filter use temporary files for both input and output?  I'd think that 
INFILE could be replaced by the path to the actual input file.

The reason I ask is that I was wondering whether the encode/decode 
filters could handle Mac resource forks.  Looks like the answer is no, 
because the resource fork has already been stripped off the input before 
it arrives at the encode filter.