Hi,

Another proposal for public consideration:

There seem to be an awful lot of static main methods around the fonts
and hyphenation packages, I was wondering if anyone had any objections
to moving all these methods into classes under a single package i.e.
org.apache.fop.cli.utils. This would involve more than merely
copy/pasting the main method itself, but also some of the ancillary
methods that are only used by static main methods. Obviously, this
would include updating the documentation to reflect the migration.

The reason I'm making this proposition is that I'm trying to unify the
URI resolution and file access within FOP, we currently use 5 URI
resolvers, without including what XMLGraphics and Batik do,
(FOURIResolver, FontResolver, HyphenationTreeResolver,
DataURIResolver, DTDEntityResolver) which I think we can all agree is
a little excessive. In so doing, I keep bumping up against these
static main methods or functions that are only called by them, and it
seems to me that while I'm at it, I might as well do some clean up.

Anyways your collective thoughts would be appreciated on the matter,

Mehdi

Reply via email to