Re: Introduction
On Tue, Jun 22, 2010 at 12:38, Giuseppe Briotti g.brio...@gmail.com wrote: 2010/6/22 Brooke Simler siml...@science.oregonstate.edu: ... I've tried to reach out and ask to get taken off, w/ no luck. Could you please help? ... Well, Brooke, did you try to send a mail to fop-dev-unsubscr...@xmlgraphics.apache.org with subject unsubscribe? It would help if the mail server would always add a blurb at the bottom about how to unsubscribe. -Tom
Re: Possible Bug: No control Over Itemized List Marks
On Tue, Jun 29, 2010 at 12:07, Christopher R. Maden cr...@maden.org wrote: Tom Browder wrote: 1. Is this a fop bug? ... Your FO markup is almost certainly requesting the symbol you see. FOP does not make up list markers on its own; it uses the requested symbol. Thanks, Chris. The information in the two docbook books led me to believe it was an implementation issue which I assumed was fop. I found the places to fix it--it looks like a DocBook limitation to me. -Tom
Re: OPen Type Korean (Hangul) Fonts
On Tue, Jul 6, 2010 at 13:26, Vincent Hennebert vhenneb...@gmail.com wrote: ... No, GPL is not compatible with the Apache license. We wouldn’t be able to ship those fonts with FOP. Anyway, I’m not sure that that bitmap font is what you want. I don’t know how FontForge does to convert a bitmap font into a vectorial font, but the result is likely to be unsatisfying. I did find that the same place has a TrueType version already. format, like Type 1, TrueType or OpenType. Linux distribution usually come with loads of fonts for many languages. For example, check out this one for Hangul: http://packages.debian.org/sid/ttf-alee Good catch--I hadn't been able to find that in my searches. fonts are. OpenType fonts based on CFF glyphs are not supported at all. It must be seen whether advanced typography is needed to properly typeset Korean (for example, glyph shaping like in Arabic). Advanced typographic tables are not used by FOP’s layout engine at the moment. That may make the issue much more complicated. From what I've found so far, it looks like advanced type setting will be needed (but I think it would be fun). Thanks, Vincent. -Tom
OPen Type Korean (Hangul) Fonts
I would like to be able to use a Hangul (Hangeul: Korean) Open Type font with fop. I have found the Unifoundry and it has Hangul fonts in bfd format. The licensing statement from the web site (http://unifoundry.com/index.html): quote My software and is released under the terms of the GNU General Public License (GNU GPL) version 2.0, or (at your option) a later version. The precompiled fonts are released under the terms of the GNU GPL version 2, with the exception that embedding the font in a document does not in itself bind that document to the terms of the GPL. /quote It seems to me that fontforge could be used to convert the bfd fonts to a vector Open Type format. If so, would their license permit them to be used for fop use and testing? Next question, could anyone working on the Open Type area in fop use some help to move toward being able to use such fonts? Thanks. -Tom Thomas M. Browder, Jr. Niceville, Florida USA
fop Defaults: page width 8.26 inches? Why?
The default configuration file on the trunk shows this line: default-page-settings height=11in width=8.26in/ Why is the width 8.25? Thanks. -Tom Thomas M. Browder, Jr. Niceville, Florida USA
Possible Bug: No control Over Itemized List Marks
I get a default filled circle (mark='bullet'?) for the listitems in an itemized list for both html and pdf output. When I have a nested list I get a default opencircle (mark='opencircle') for the nested listitems for html output but still get the bullet for pdf output. The fop conformance page says all list handling things are taken care of. I cannot find much help on the mailing list archives except to say a font change may be needed (but no example). I can find nothing in the bug list about this. Questions: 1. Is this a fop bug? 2. Is there a way to work around the problem? If so, please give an explicit example of how to do it (or point to one). Thanks. Regards, -Tom Thomas M. Browder, Jr. Niceville, Florida USA
Re: SEVERE: Couldn't find hyphenation pattern en_US
On Sun, Jun 27, 2010 at 14:20, Simon Pepping spepp...@leverkruid.eu wrote: ... How to include fop-hyph.jar in a build of the trunk code is described at http://offo.sourceforge.net/hyphenation/fop-stable/installation.html. Thanks, Simon! Regards, -Tom
Possible Bug: I/O exception while reading font cache...
The FAQ points to a solution: turn off use of the cache. I copied the default fop config file and added the following line inside: use-cache0/use-cache Note: I also tried: use-cachetrue/use-cache I then used the -c option to fop to point to my config file, but I still get the error. I am using fop 0.95. Am I doing something wrong? Thanks, -Tom Thomas M. Browder, Jr. Niceville, Florida USA
Re: Possible Bug: I/O exception while reading font cache... [SOLVED]
On Sat, Jun 26, 2010 at 08:25, Tom Browder tom.brow...@gmail.com wrote: The FAQ points to a solution: turn off use of the cache. Okay, this is fixed on the trunk--sorry. -Tom
Re: PostScript output: missing %%DocumentNeededResources comment
On Fri, Jun 25, 2010 at 06:37, Jeremias Maerki d...@jeremias-maerki.ch wrote: Hi Vincent, ... hmmyes, that's tricky. An (atend) requires a corresponding comment in the end, but resources is defined to provide at least one item. An ugly work-around would be to always list Helvetica as needed resources and to generate a corresponding %%IncludeResource although it might never be used. Would two passes work as a first-order work-around? -Tom
Re: SEVERE: Couldn't find hyphenation pattern en_US
On Wed, Jun 23, 2010 at 06:45, Tom Browder tom.brow...@gmail.com wrote: On Tue, Jun 22, 2010 at 15:50, Eric Douglas edoug...@blockhouse.com wrote: ... So, assuming the jar file is physically in dir /usr/local/share/fop, should the CLASSPATH read: export CLASSPATH=/usr/local/share/fop/fop-hyph.jar By experiment, that method worked for the build directory, but not for my installed fop 0.95. I also tried using the environment variable FOP_HYPHENATION_PATH again (after unsetting CLASSPATH). I tried it two ways: (1) setting it to point the file and (2) setting it to point to the parent directory of the file. Both worked for the installed fop 0.95. I would like to try all that with the trunk version, but nowhere on the fop site does it tell how to install after a build. The closest thing I found is the package argument to ant. What should I do to install, please? Thanks. -Tom
Re: SEVERE: Couldn't find hyphenation pattern en_US
On Wed, Jun 23, 2010 at 08:06, Eric Douglas edoug...@blockhouse.com wrote: What do you mean install after a build? ... To 'install' as in to be able to run from a command line, simply requires having all required jars in the classpath. If you use the binary download, the classpath is built into the jar's manifest. Just read the classpath statement there and have all Well then how does a developer build the installation package (i.e., the binary download)? I want to install the trunk build just as, say, Ubuntu does to ensure all dependencies, etc., work outside the build environment. And I want to be able to distribute the run package to others. -Tom
Re: SEVERE: Couldn't find hyphenation pattern en_US
On Wed, Jun 23, 2010 at 09:04, Eric Douglas edoug...@blockhouse.com wrote: The binary download is the same as the source download should be if you compile it. That's not a standalone package. It doesn't install as an application in Windows. I'm not trying to be difficult here, Eric, just trying to figure the fop system out. I compared the fop 0.95 binary download with the trunk build and they are not the same--extra stuff in the trunk (not counting subversion files), extra stuff in the binary. Obviously there is either manual intervention or a packaging script to produce the bin package for download. If there is not a script, there should be. If there is a script, where is it? -Tom
Re: SEVERE: Couldn't find hyphenation pattern en_US
On Wed, Jun 23, 2010 at 10:52, Eric Douglas edoug...@blockhouse.com wrote: Of course the 0.95 is not the same as the trunk. There is a binary download and a source download for 0.95. If you compile that source, you should get a binary which matches the binary download. The trunk is only available in source form. Then how is the source download package produced from the trunk? -Tom
Re: SEVERE: Couldn't find hyphenation pattern en_US
On Wed, Jun 23, 2010 at 11:03, Eric Douglas edoug...@blockhouse.com wrote: You have to use Subversion to download the trunk source. There is a Subversion program which you can run from a command prompt, and there's an extension for Eclipse. Either way Eric, I'm working in the subversion trunk. I'm trying to understand how the distributable packages on the fop download site are assembled, by hand or by script? If by script, where is it? If by hand, where are the procedures written? Thanks, -Tom
Re: SEVERE: Couldn't find hyphenation pattern en_US
On Wed, Jun 23, 2010 at 16:29, J.Pietschmann j3322...@yahoo.de wrote: On 23.06.2010 18:08, Tom Browder wrote: I'm trying to understand how the distributable packages on the fop download site are assembled, by hand or by script? If by script, ... It's the build.xml file. You'll need ant (http://ant.apache.org) to run it, the target dist will generate tgz and zip archives for Thanks, I forgot about listing all the ant build targets (duh)! both a binary and a source package. It will not generate a package which can be used by the Ubuntu package system. Okay, but at least should be able to be installed (i.e., unpacked) into some directory and it should work if the fop start-up script can be found on one's path. Thanks for everyone's patience--consider this thread closed. -Tom
SEVERE: Couldn't find hyphenation pattern en_US
I am getting the subject message during build tests on the trunk as well as with the stable version of fop on Ubuntu 10.04 amd64 (fop 0.95). I have tried to explicitly point to the fop-hyph.jar file with the FOP_HYPHENATION_PATH environment variable but that doesn't seem to work. Any ideas? Thanks. -Tom Thomas M. Browder, Jr. Niceville, Florida USA
Re: SEVERE: Couldn't find hyphenation pattern en_US
On Tue, Jun 22, 2010 at 15:29, J.Pietschmann j3322...@yahoo.de wrote: On 22.06.2010 19:02, Tom Browder wrote: I have tried to explicitly point to the fop-hyph.jar file with the FOP_HYPHENATION_PATH environment variable but that doesn't seem to work. So should I file a bug for that? The fop-hyph.jar must be in the classpath, putting it into the fop/lib directory should be sufficient if FOP is run using one of the scripts as they pick up any jar there. I'm not sure whether the fop-hyph.jar from the OFFO project contains an en_US hyphenation class, maybe there is only an en_UK class there. Check using jar -tvf lib/fop-hyph.jar Note that I tried the CLASSPATH trick before with fop 0.95 and it didn't work, but I'll try again. Is there any way (tool or utility) to read a jar file to see if a particular hyphenation class is there? Thanks, -Tom
[PATCH] Correct Some Minor fop Execution Message Flaws
In my e-mail to fop-users (see
http://www.mail-archive.com/fop-users%40xmlgraphics.apache.org/msg11324.html)
I complained about a couple of minor issues:
1. Running 'fop' with no arguments throws an exception after printing
a usage statement.
2. Running 'fop -v' throws an exception after printing the version.
3. Another issue, not complained about in the cited message, is that
the current usage and help messages refer to 'Fop' while the user
executes 'fop'.
The attached patch was generated by running 'svn diff' at the top of
the working directory of a checked-out fop trunk at revision 698670.
It affects the following files:
src/java/org/apache/fop/cli/CommandLineOptions.java
src/java/org/apache/fop/cli/Main.java
It corrects all three issues listed above.
Thanks for your attention.
Regards.
-Tom
Index: src/java/org/apache/fop/cli/CommandLineOptions.java
===
--- src/java/org/apache/fop/cli/CommandLineOptions.java (revision 699531)
+++ src/java/org/apache/fop/cli/CommandLineOptions.java (working copy)
@@ -234,6 +234,11 @@ public class CommandLineOptions {
* @exception FOPException if there was an error in the format of the options
*/
private boolean parseOptions(String[] args) throws FOPException {
+ // do not throw an exception for no args
+ if (args.length == 0) {
+ printUsage();
+ System.exit(1);
+ }
for (int i = 0; i args.length; i++) {
if (args[i].equals(-x)
|| args[i].equals(--dump-config)) {
@@ -305,6 +310,7 @@ public class CommandLineOptions {
i = i + parseAreaTreeOption(args, i);
} else if (args[i].equals(-v)) {
System.out.println(FOP Version + Version.getVersion());
+ System.exit(1);
} else if (args[i].equals(-param)) {
if (i + 2 args.length) {
String name = args[++i];
@@ -331,6 +337,7 @@ public class CommandLineOptions {
i = i + parseUnknownOption(args, i);
} else {
printUsage();
+ System.exit(1);
return false;
}
}
@@ -1033,8 +1040,9 @@ public class CommandLineOptions {
* shows the commandline syntax including a summary of all available options and some examples
*/
public static void printUsage() {
+ // Remember that the user executes 'fop', not Fop.
System.err.println(
- \nUSAGE\nFop [options] [-fo|-xml] infile [-xsl file]
+ \nUSAGE\nfop [options] [-fo|-xml] infile [-xsl file]
+ [-awt|-pdf|-mif|-rtf|-tiff|-png|-pcl|-ps|-txt|-at [mime]|-print] outfile\n
+ [OPTIONS] \n
+ -ddebug mode \n
@@ -1095,28 +1103,29 @@ public class CommandLineOptions {
+ XSL-FO file is saved and no rendering is performed. \n
+ (Only available if you use -xml and -xsl parameters)\n\n
+ \n
-+ [Examples]\n + Fop foo.fo foo.pdf \n
-+ Fop -fo foo.fo -pdf foo.pdf (does the same as the previous line)\n
-+ Fop -xml foo.xml -xsl foo.xsl -pdf foo.pdf\n
-+ Fop -xml foo.xml -xsl foo.xsl -foout foo.fo\n
-+ Fop -xml - -xsl foo.xsl -pdf -\n
-+ Fop foo.fo -mif foo.mif\n
-+ Fop foo.fo -rtf foo.rtf\n
-+ Fop foo.fo -print\n
-+ Fop foo.fo -awt\n);
++ [Examples]\n + fop foo.fo foo.pdf \n
++ fop -fo foo.fo -pdf foo.pdf (does the same as the previous line)\n
++ fop -xml foo.xml -xsl foo.xsl -pdf foo.pdf\n
++ fop -xml foo.xml -xsl foo.xsl -foout foo.fo\n
++ fop -xml - -xsl foo.xsl -pdf -\n
++ fop foo.fo -mif foo.mif\n
++ fop foo.fo -rtf foo.rtf\n
++ fop foo.fo -print\n
++ fop foo.fo -awt\n);
}
/**
* shows the options for print output
*/
private void printUsagePrintOutput() {
+ // Remember that the user sees /fop', not Fop.
System.err.println(USAGE: -print [from[-to][,even|odd]] [-copies numCopies]\n\n
+ Example:\n
- + all pages:Fop infile.fo -print\n
- + all pages with two copies:Fop infile.fo -print -copies 2\n
- + all pages starting with page 7: Fop infile.fo -print 7\n
- + pages 2 to 3: Fop infile.fo -print 2-3\n
- + only even page between 10 and 20: Fop infile.fo -print 10-20,even\n);
+ + all pages:fop infile.fo -print\n
+ + all pages with two copies:fop infile.fo -print -copies 2\n
+ + all pages starting with page 7: fop infile.fo -print 7\n
+ + pages 2 to 3: fop infile.fo -print 2-3\n
+ + only even
