On Mon, Sep 05, 2005 at 09:35:26PM +0200, Jeremias Maerki wrote: > As I said, widely differing views between Batik and FOP about this. In > my own personal opinion, I'm with you. From the POV of XML Graphics > Commons we have a problem. We've voted on the plan for Commons where we > said that we'd try to remove the dependency on Commons Logging. If there > is a problem with that, the right place to raise this is > [EMAIL PROTECTED]
That means that those Commons components will have to define their own interface to which they are willing to send logging events, just like ForayFont does. FOP will have to implement all interfaces defined by the libraries it uses. It should do so on top of a Commons Logger instance, to preserve Commons Logging user configurability. It would of course be easier if all components would use a standard interface like Commons Logging. But that is not going to happen in this world. My remark about runtime information to debug a system configuration is inspired by a TeX system, which needs to load many component files. I realized that it uses a different method. Its resolver library does indeed no logging. Instead, there is a stand-alone front end to it that the user must run separately to obtain configuration debugging information. For example, when in my LaTeX run class X is not loaded as I expect, I use this app (kpsewhich) to find out where the resolver library thinks the class X is. It also displays search path information, and information about how the search path is constructed from the configuration file and the built in path components. Regards, Simon > On 05.09.2005 21:15:50 Simon Pepping wrote: > <snip/> > > I am not sure that I understand everything that is being said > > here. But I am alarmed when I hear that basic libraries, in this case > > the FontServer, shouldn't log anymore. In my experience a font system > > requires powerful logging, in order to expose runtime behaviour to the > > systems manager or end user. Configuring font systems and > > understanding why a piece of font software does not use it as you > > expect, is a hard task that requires suitable runtime information from > > the software. > > Jeremias Maerki > -- Simon Pepping home page: http://www.leverkruid.nl
