Hi,

Can someone comment on this, as I'd like to get this done...

Another alternative might be to add (input)encoding/outputencoding attributes to a specialized fileset top be used by the <copy>/<move> tasks.

That way we could eventually have multiple fileset with different encodings for these tasks, if we intend to have support for multiple filesets for these tasks ...

So the options are :

- (input)encoding / outputencoding attributes on <copy> / <move> task itself

- (input)encoding / outputencoding attribute on new specialized fileset

- (input)encoding / outputencoding attribute on <filterchain>

I don't think that last one is good, because that would mean you'd need to have two (input)encoding attributes for the new <loadfile> task (which I'll probably commit to cvs later today), as you don't always have a <filterchain> when loading a file.

By having these attributes on either the tasks or the fileset, we can also support on the fly conversion from one encoding to another while copying/moving files.

What do you think ?

Gert

----- Original Message ----- From: "Gert Driesen" <[EMAIL PROTECTED]>
To: "Ian MacLean" <[EMAIL PROTECTED]>
Cc: "Nant-Developers (E-Mail)" <[EMAIL PROTECTED]>
Sent: Saturday, October 02, 2004 1:47 PM
Subject: encoding/outputencoding attribute



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

Reply via email to