> From: Jeremy Quinn [mailto:[EMAIL PROTECTED]]
<snip/> > >Question #2: do you check if the <xfwt:write> element includes *one* and > >only *one* nested element? If not, we could end up with problems later > >on. Wait, why such a limitation? What if you want to write few files, not one? The result modes of the transformer might be: - exception in case of error, - <xfwt:result/> tag > No I don't, I'll add that to my list, thanks. Please reconsider this addition :) <snip/> > A namespace declaration for xfwt is always output to the files it writes to. > It was already in the Document that the file is generated from so it > happens automatically. > > I am trying to decide if this is a good thing or not. > > In one way it is quite cute ;) a kind of signature, but in another sense it > is pollution, if there are no xfwt tags in the file, why the hell should it > declare that namespace? > > If I filter it out however, then no-one can edit files containing that > namespace anymore. Why do you think this? Just add a namespace when you need it later. > Which is the right way to go do you think? I think there is no need (and may be even harm) to have xfwt namespace declared needlessly. Vadim --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
