> -----Original Message-----
> From: Andreas L. Delmelle [mailto:[EMAIL PROTECTED]
<snip />
> As for the build targets: so we don't remove these, but it
> seems we definitely could/should tweak these to accomodate
> the creation of the JAR that will be offered through OFFO,
What I did so far (locally):
Modified the 'package' build target to deliver two separate JARs, say
fop.jar and fop-hyph.jar (added 'hyphenation-jar' target to its
dependencies)
The latter JAR can be rebuilt separately by putting the desired hyphenation
source files into ${FOP_HOME}/hyph and running Ant with the
'hyphenation-jar' build target.
Have the scripts --.bat and .sh-- append '${FOP_HOME}/build/fop-hyph.jar' to
the local CLASSPATH. I'm not too sure about the location here: is 'build'
OK, or should we dump it in the 'lib' folder, or just the 'hyph' folder?
In any case, we no longer provide hyphenation out-of-the-box, but using it
becomes fairly straightforward...
The instructions toward the end-user:
- either download precompiled 'fop-hyph.jar' from OFFO
and place it in the build-dir (or the lib-dir? or hyph-dir?)
- or download the separate XML sources for the needed patterns,
and run 'ant hyphenation-jar' which will create the JAR in
the right place so it's picked up on the next run
If they really want to, they can use multiple hyphenation JARs as long as
they make sure they are all included in the CLASSPATH when running FOP. The
base 'fop-hyph.jar' can be used as a reference for the users to point out
what needs to be done.
We can still provide the option of using uncompiled patterns directly at
runtime, but IMO it would be better to present this as an option for
one-time usage, or to test a particular pattern before adding it to a JAR in
its compiled form.
Further comments always welcome.
Cheers,
Andreas
