Re: Antwort: Re: Antwort: Re: Changing logging behavior in an embedded application.

2006-03-07 Thread Jeremias Maerki
> > > > Jeremias Maerki <[EMAIL PROTECTED]> > 07.03.2006 08:45 > Bitte antworten an > fop-users@xmlgraphics.apache.org > > > An > fop-users@xmlgraphics.apache.org > Kopie > > Thema > Re: Antwort: Re: Changing logging behavior in an embedded

Antwort: Re: Antwort: Re: Changing logging behavior in an embedded application.

2006-03-07 Thread Eckard_Buchner
TED]> 07.03.2006 08:45 Bitte antworten an fop-users@xmlgraphics.apache.org An fop-users@xmlgraphics.apache.org Kopie Thema Re: Antwort: Re: Changing logging behavior in an embedded application. You're welcome to improve TTFReader in FOP Trunk if it doesn't do exactly what y

Re: Antwort: Re: Changing logging behavior in an embedded application.

2006-03-06 Thread Jeremias Maerki
You're welcome to improve TTFReader in FOP Trunk if it doesn't do exactly what you want it to do. TTFReader was never designed to be used as anything else than a command-line tool which is called once for each font. If people have additional needs we're gladly accepting patches against FOP Trunk.

Antwort: Re: Changing logging behavior in an embedded application.

2006-03-06 Thread Eckard_Buchner
> FOP does have a few System.out.println calls in its source code but > these are only in places where those are ok, i.e. in command-line > handling code IMHO this is not the case with the TTFReader. It tells you about each file it reads and writes. If you convert a couple of files at once this i