"Bo Peng" <[EMAIL PROTECTED]> writes: > Dear all, > > Using a trick that add par_id and pos information during the handling > of encoding_exception, I came up with a much simpler patch. Basically,
This patch is welcome, since not knowing what character has a problem is really annoying. I am not sure though that this system f exception (while clever) is very scalable wrt other information we might want to make available during export. The traditional solution to such problems was to use the OutputParams struct and to add there whatever variable is necessary. Is it really unfeasible here? JMarc
