Quoting Jeremias Maerki <[EMAIL PROTECTED]>:
No, but that could easily be included in AbstractCodePointMapping where the substitution is controlled from. That would be easier to implement than an event in the event processing framework as AbstractCodePointMapping doesn't have access to the user agent. If we decide to make it an event (which is probably a bit cleaner), I probably have to change AbstractCodePointMapping a bit to make it a two-stage process (we can only return one result, a char, which is not suitable for indicating a substitution to the outside). That's the first decision. The second is the log level (for both approaches): DEBUG, INFO or WARN. I'd vote for DEBUG in this case.
I agree that events are best and that DEBUG is the right level. Simon ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. --------------------------------------------------------------------- Apache XML Graphics Project URL: http://xmlgraphics.apache.org/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
