Re: Problems running FOP
"Arved Sandstrom" <[EMAIL PROTECTED]> wrote: > I assure you that WinZip or equivalent is entirely capable of unpacking > .tar.gz compressed archives. Not only that, the download is faster because > .tar.gz files are almost always smaller. It does a fine job, though it's often a good idea to shut off "TAR File Smart CR/LF Conversion" in the Configuration dialog, just in case it guesses wrongly about whether a file is a text file or not. Cheers, -Peter S. Housel- [EMAIL PROTECTED] http://members.home.com/housel/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Xslt task issue (was Re: [GUMP] Build Failure - Fop)
At Sun, 26 Aug 2001 16:48:52 +0200, Karen Lease wrote: > OK. I fixed it. I found a way to build the font files without using the > "mergefile" attribute on Xslt (thanks to an example in the XSLT > Recommendation on how to use the key function on an external document - > cool!). Then I changed Xslt.java to only build a DOM tree as input to > the transformer if mergefile is used, otherwise just to pass the input > xml filename. That lets Xalan2 know the system id (ie, file name) of the > input XML file so that it can correctly resolve relative URLs in the > document function. That should keep GUMP happy for now. Why not then just use Ant's built-in
Re: Alternative to SVG
> I don't think it's possible to embed pdf directly into another pdf document. > It *might* be possible to support eps directly with fop by using pdf > xobjects (not quite sure here, but I think I remember somthing about that > from the pdf spec), but then the pdf document would have to be printed on a > postscript printer to show the figures. It's *possible* (pdftex and dvipdfm can do it), but nobody's written the code to do it for FOP. Looking at the source to dvipdfm, it looks like it (lazily) parses the pdf file, scrounges through the page tree, and includes a reference to the first page. This should be doable in the FOP framework as well. -Pete-r - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
[PATCH] Proper use of font encodings for "native" fonts
One of the major annoyances for me as I tried to use FOP has been that it didn't try very hard to get the encodings of the Symbol and ZapfDingbats fonts right. In particular, using the proper Unicode characters for glyphs in these fonts wasn't possible. The enclosed patch (against 0.20.2, though it should apply cleanly against the CVS HEAD version) fixes the encoding mechanism. It splits charlist.xml (which only covered WinAnsiEncoding) into two files, glyphlist.xml (containing the official Adobe Glyph List and Zapf Dingbats glyph lists), and encodings.xml (containing all of the standard Adobe encodings). This forces the build process to do a relational "join" on the two files to generate CodePointMapping.java, slowing it down a little bit. It still uses the WinAnsiEncoding for text fonts because this vector gives the best coverage. Building with -Dtextfontencoding=MacRomanEncoding or -Dtextfontencoding=MacExpertEncoding should work too, and allow a different subset of the font characters in the native text fonts. With the addition of code to output encoding vectors, other encodings (such as CEEncoding) could be used. Note that this patch requires that the ant distribution's "optional.jar" be added to lib. -Peter S. Housel- [EMAIL PROTECTED] http://members.home.com/housel/ fop-encoding.zip Description: Zip archive - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: provisional-distance-between-starts and provisional-label-separation doesn't work
At Thu, 11 Oct 2001 10:33:59 GMT, [EMAIL PROTECTED] wrote: > hi all, > I'm using FOP-0.20.1 and I have used the above attributes for the > list-block, but it doesn't work. So, anyone has any ideas about this > problem? > > Anyway, in order to perform this task, I have used text-indent in the > list-block, and it worked. > > But, there is a text-alignment problem in the list (please refer the > attachment), so, how can I solve it? As it says in the XSL spec, you're supposed to use end-indent="label-end()" in the fo:list-item-label element and start-indent="body-start()" in the fo:list-item-body element. See docs/examples/fo/list.fo for an example. -Peter- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: timeframe for maintenance release
Christian Geisert <[EMAIL PROTECTED]> wrote: > Arved already proposed 15 Dec as release date. > > I think it would be a good idea to do some testing before the actual release, > so we should do a code freeze some days in advance. > What about Monday the 10th ? Any hope of including my recently-posted font encoding patch in the release? Cheers, -Peter S. Housel- [EMAIL PROTECTED] http://members.home.com/housel/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: uncommitted patches
> while browsing the archives I found the following uncomitted patches, > and as it is quite frustrating if your patch gets not noticed (and you > worked hard for it..) we should try to commit all (if possible). > > * improved font-encoding by Peter S. Housel > (see http://marc.theaimsgroup.com/?l=fop-dev&m=100559770232644&w=2) > To build with this patch you need optional.jar from ant 1.3 > (download > http://jakarta.apache.org/builds/jakarta-ant/release/v1.3/bin/jakarta-ant-1. 3-optional.jar > and copy it to lib/optional.jar) and add it to build.bat (build.sh has it two > times ;-) > I noticed the same problems as Rainer Garus > (see http://marc.theaimsgroup.com/?l=fop-dev&m=100790930100949&w=2) > Peter, what do you think? I'll fix the problems and come up with a revised patch by this weekend. Cheers, -Peter S. Housel- [EMAIL PROTECTED] http://members.home.com/housel/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Suggestions for the "How to get Help" page
1. In item 1, the word "embed" is spelled incorrectly. 2. The word "get" in the title should probably be capitalized. 3. A link to ESR's "How to Ask Questions the Smart Way" (http://www.tuxedo.org/~esr/faqs/smart-questions.html) might be helpful. Cheers, -Peter S. Housel- [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: infinity character and PDF
"J.Pietschmann" <[EMAIL PROTECTED]> wrote: > Jens v. Pilgrim wrote: > >The infinity character (Unicode: ∞ , HTML: ∞ ) is > > rendered correctly by the AWT and Print renderers, but incorrectly by > > the PDF renderer...(I've got a '#' there). > > Try ∞ > > I think it's a problem with the character mapping tables. By > default, FOP uses only a few standard fonts defined by Adobe > for PDF generation, it does not use any Unicode fonts. If you > get a "#", check in which font the glyph is and change to it. The XSL spec allows the "font-family" to be a comma-separated list of font families, and for the processor to choose the appropriate font for each character when a "font-selection-strategy" of "character-by-character" is given. Unfortunately neither FOP nor XEP support the "font-selection-strategy" property, so it is necessary to explicitly use fo:inline to change the font for special characters. Another alternative is to embed a TTF font that includes all of the characters you need. The docs/examples/fo/fonts.fo file lists all of the characters supported by each of the default fonts in their standard encodings. Cheers, -Peter S. Housel- [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Re: the license of Chinese hyphenation pattern file
"stoneson" <[EMAIL PROTECTED]> wrote:
> the problem is : when I use to write a part of Chinese
> in the block or table-cell, the Chinese text could not broken
> in the end of line. so I use the hyhens to fixed it, the problem solved,
> but there is not hyhens file of Chinese for FOP, I wonder is there any
good
> way to make the text broken if I would not use hyhens.??
What some people do is to put a space character (" ") after every Chinese
character. It spaces out the text a little, but at least FOP knows where it
can break the lines, and it looks better than hyphens (which can be mistaken
for the number "1").
At some point the FOP developers need to implement the Unicode Line Breaking
Algorithm (described in http://www.unicode.org/unicode/reports/tr14/) so
that FOP can break lines of Chinese/Japanese/etc. without needing extra
spaces.
-Peter-
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
Re: Sun XSL Formatter
"Arved Sandstrom" <[EMAIL PROTECTED]> writes: > Well, Java or C or C++ or Haskell, it would have been nice to have a clue. > > We have an ASF tradition of developing communities...this kind of stuff that > Sun and IBM does is getting old. Don't open-source it; sell it. I will argue > against its adoption into Apache. Googling for xmlroff yields: http://www.plurb.com/webservices/UBL4.pdf Looks like they want to donate it to Gnome, not Apache. Despite your not wanting to sound bitter, your protest still sounds bitter anyway. -Peter- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
