Ian,
I wonder if we should move the encoding / outputencoding from the <filterchain> element to the <copy> / <move> tasks ?
We could, like Ant, also use the encoding/outputencoding attribute to allow files to be converted from one encoding to another while copying/moving them (even without using filterchains).
Also, I was planning on adding a <loadfile> task (similar to its Ant counterpart) which also support <filterchain>, but in that case you would also need to be able to specify an encoding on the <loadfile> task itself, as you might not always been using filters, and still need to specifiy the encoding of the file that you're loading.
Also, the outputencoding attribute of the <filterchain> element does not make sense in case of the <loadfile> task.
Should we rename the "encoding" attribute to "inputencoding" ?
What do you think ?
Gert
------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
