[XML-SIG] xmlproc bug?

Lars Marius Garshol larsga@garshol.priv.no
07 May 2001 14:27:47 +0200

* Lars Marius Garshol
| I see no reason why it should be. If the application is converting
| to Unicode itself, or if it got the data from somewhere as Unicode,
| there is no reason why it should not be allowed to parse those data.

* Martin v. Loewis
| I agree in principle. However, just allowing to call feed with a
| Unicode object is too permissive: What if you had previously called it
| with a string?

Good point. One should have to stick to either Unicode or byte strings
throughout a single parse.

Looking at the code I think it makes sense to require client code to
also be consistent in its use of the 'decoded' flag. That is, decoded
should always have the same value throughout an entire parse.
| So if this is allowed, 

It is allowed now, since I've committed my change.

| care should be taken that a sensible thing happens when somebody
| mixes byte and unicode strings (signalling a fatal error might be
| sensible).

I agree.

I am working on the modification now and will commit it shortly.

--Lars M.