On 09/08/11 11:33, Jirka Kosek wrote:
On 7.8.2011 18:50, Bob Stayton wrote:
This isn't a case of import precedence, but of different attributes.
In general, the qualified attributes (like space-before.optimum) take
precedence over the non-qualified attributes (like space-before). I
wish
On 09/08/11 07:58, Gjertrud wrote:
Hi!
I can't get the ?dbfo-need height=1in? to work. Not if I change to the
metric system either. I found that this issue has been raised earlier:
http://old.nabble.com/dbfo-need-height-and-FOP-tt27421275.html
I am using DocBook XSL 1.75.2 and FOP
On 14/04/11 09:06, Jirka Kosek wrote:
David Cramer wrote:
I've done a little research on this and found on the fop list some
discussion (pasted below). The fop developers feel that using the
hyphenation character to achieve this is an abuse of the
hypenation-character property.
I don't
Hi Antti,
Antti Karanta wrote:
On Wed, 03 Feb 2010 10:13:47 +0200, Antti Karanta
antti.kara...@napa.fi wrote:
When I test dbfo-need with fop.0.95 and 1.75.2, I found that it does
work in some locations but not others. In the case of placing a
dbfo-need between block elements like para,
Hi,
Ron Catterall wrote:
Could somebody tell me which is the correct symbol to use for apostrophe.
The HTML special characters entity set has apos #x27 where apos
presumably stands for apostrophe - this is the straight up single quote
mark which XML defines and uses for special purposes.
Hi Jens,
What do you mean by “do not hyphenate properly”? If FOP doesn’t
hyphenate at all, this probably is because it is missing hyphenation
patterns. Look here for how to install them:
http://offo.sourceforge.net/hyphenation/index.html
Otherwise, could you please attach your FO file and
, which will work
with all versions of FOP
fop -xml narow-column.xml -xsl
/path-to-docbook-1.75.2/fo/docbook.xslexample.pdf
I have enclosed the FO file for your convenience.
Regards
Jens
Vincent
On Wed, Dec 16, 2009 at 12:12 PM, Vincent Hennebert
vhenneb...@gmail.com
Hi,
If that's an acceptable option for you, you can use the Trunk version of
FOP in which that bug has been fixed. You can download a snapshot of the
source code here:
http://svn-master.apache.org/snapshots/fop/
And see here for help about building FOP:
Hi Tobias,
Tobias Anstett [k15t.com] wrote:
Hi,
Recently I had a problem with image overflows using Apache as well as XEP.
I use both very wide and very high images in my documentation. When
applying my customization layers they are always scaled to match the
width of the page but I have
Hi,
Since it’s not a regular word it can’t be hyphenated; you must specify
yourself the places where it is allowed to break. If you want a hyphen
to be visible when the text is broken you can use the soft hyphen
character (U+00AD). Otherwise you can use a zero-width space (U+200B).
HTH,
Vincent
that process,
inserting those characters by hand is obviously tedious.
HTH,
Vincent
Thanks,
BRAMANI.
On Tue, Oct 27, 2009 at 5:55 AM, Vincent Hennebert vhenneb...@gmail.com
wrote:
Hi,
Since it’s not a regular word it can’t be hyphenated; you must specify
yourself the places where
Hi,
Dean Nelson wrote:
Hi y'all,
Is there a way to shrink the page size in Docbook without having to
reformat the doc going to PDF (FOP).
My users would like to have a half size manual to travel with instead of
a regular US Letter size page. I guess I could to this at the printers,
Hi Lily,
Lily Galle wrote:
Hi,
If I want to indent one whole paragraph (not only the first line of the
paragraph), what should I do?
The “text-indent” only indents the first line of one paragraph. This is not
what I want.
Simply use the margin-left property.
Thanks for any help!
Hi,
Bob Stayton wrote:
I believe this is a FOP limitation,including 0.95, supposedly fixed in
the trunk version[1].
Yes, that’s right. However...
Is anyone using the trunk version of FOP that can test this
problem?
[1]
Hi Bob,
Bob Stayton wrote:
Hi,
This is very interesting. I did not know that keep-together is not a
property that acts on fo:table-cell, but that is indeed what the spec
says. My experience has been that in both XEP and Antenna House, putting
that property on fo:table-cell will keep the
Hi,
Bob Stayton wrote:
OK, I checked this out, and it seems that FOP 0.95 knows how to keep an
ordinary table cell together, but it does not know how to keep a cell
together if it spans down to additional rows. That should probably be
reported as a bug on FOP, because it should work for
Hi,
Marcel Tromp wrote:
Hi,
I am using fop 0.95. I am using code similar to this example:
I've tried using this dbfo at different location as well (row, start of
table) and I don't see any difference: fop breaks the table in the
middle of a cell that straddles multiple rows.
tbody
Hi Marcel,
Marcel Tromp wrote:
Hi,
I have a long table in which certain columns contain a large vertical
span (using morerows attribute).
When printing to pdf with fop, fop page breaks this large vertical cell
at an arbitrary place.
I have been trying to control this using the
Hi,
My experience with LaTeX is getting old, so I may have missed the latest
news. Anyway...
Albretch Mueller wrote:
~
Say you have a body of texts about engineering or Sciences including
lots of drawings (colours are not important) with basically lines,
planes, ... how well can you encode
Hi,
Dennison, Cheri a écrit :
Hi!
I'm upgrading to FOP 0.95 from 0.20.5 and from 1.70.1 to 1.74 for the DB
stylesheets, and with the upgrade I have a particular long orderedlist (with
another level of nested orderedlists inside) that no longer breaks correctly
at the bottom of the page.
Hi Nancy,
Nancy Brandt wrote:
Hi guys,
I've got the following problem: (using XSLTPROC and FOP 0.94)
When one of the cells in the last table row on a page is too large
(because of a long sentence for example), this cell moves to the next
page, while other row cells stay on the
on this subject will be very welcomed. As a worst case scenario
i'm looking for a way to disable this warning, but i prefer fix the problem
even there is no visual problem on the pdf output.
HTH,
Vincent
--
Vincent HennebertAnyware Technologies
http://people.apache.org
.
Thanks!
Vincent
--
Vincent HennebertAnyware Technologies
http://people.apache.org/~vhennebert http://www.anyware-tech.com
Apache FOP Committer FOP Development/Consulting
://www.nabble.com/draft.watermark.image-and-catalog.xml-tp17166155p17166155.html
Sent from the docbook apps mailing list archive at Nabble.com.
--
Vincent HennebertAnyware Technologies
http://people.apache.org/~vhennebert http://www.anyware-tech.com
Apache FOP
a small chance it will be fixed in the next couple
of months.
split/
Vincent
--
Vincent HennebertAnyware Technologies
http://people.apache.org/~vhennebert http://www.anyware-tech.com
Apache FOP Committer FOP Development/Consulting
has been fixed and the
workaround should no longer be necessary, starting from version 0.95beta
of FOP.
Vincent
--
Vincent HennebertAnyware Technologies
http://people.apache.org/~vhennebert http://www.anyware-tech.com
Apache FOP Committer
and pngcheck. There are differences,
but when I try to use convert to fix them it doesn't seem to help.
Harry
Since I've had so many responses to this, I thought I'd add a tarball
with what I'm trying to do.
Harry
--
Vincent HennebertAnyware Technologies
http
Graphics team,
Vincent Hennebert
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
ask.
I hope this helps,
Vincent
--
Vincent HennebertAnyware Technologies
http://people.apache.org/~vhennebert http://www.anyware-tech.com
Apache FOP Committer FOP Development/Consulting
admon.xsl
l.50: FOP now supports the url
checked each of the font locations and they are
proven to be true to the location specified in the xconf file. The
fonts registered are the same fonts which have been used to process the
documents in version fop-0.20.5.
Any help would be appreciated.
Andrew
--
Vincent Hennebert
patterns from another
website and put the fop-hyph.jar file you get in the build/ directory of
your FOP installation. This separate process is necessary because of
licensing issues (hyphenation patterns may not be distributed with FOP).
HTH,
Vincent
--
Vincent Hennebert
Hi Paul,
Paul Stubbe wrote:
I do not know if the following issue is a docbook or a FOP issue.
But as a happy Docbook user, I start my search for a solution on this list.
The footnote content is lost (?) during the fo to pdf processing whenever I
put a footnote in a qandaset.
Is this
Hi Chris,
Chris Ridd wrote:
Hi,
I'm using Docbook and the related XSL stylesheets pretty successfully
except for one odd problem.
I have a number of procedures containing steps, and if a para inside a
step contains a menuchoice, and my stylesheet sets:
xsl:param
Hi,
Akagi K wrote:
Hi DocBook gurus,
In June this year my colleague built FOP 0.94 from the binary that was
available then.
You probably mean he built a binary from a checkout of the Trunk.
Wordwrapping in Japanese which was a problem with FOP0.93
was resolved with that. I see now that
Hi,
Sorry for the delay...
Mauritz Jeanson wrote:
-Original Message-
From: spr
This didn;t work either:
xsl:attribute-set
name= header.table.properties
xsl:attribute
name = table-layoutfixed/xsl:attribute
xsl:attribute
name =
Hi,
You appear to be on a Linux box. Install the gsfonts package (“Fonts for
the Ghostscript interpreter(s)”). You will get clones of the 35
well-known Postscript fonts, among which the base 14 PDF fonts (Times,
Helvetica, Courier...).
Go to the directory where these fonts are installed
the compliance page for a detailed overview:
http://xmlgraphics.apache.org/fop/compliance.html
For download information, see the following page:
http://xmlgraphics.apache.org/fop/download.html
For the XML Graphics team,
Vincent Hennebert
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment
Hi Cheri,
Dennison, Cheri a écrit :
Naresh--
Did you run into any troubles getting fonts to work with 0.93? We're in
the process of trying to upgrade and bumped into a font problem there.
We haven't dug into yet, but just curious if you ran into anything.
If you’re upgrading from the 0.20.5
Vincent Hennebert a écrit :
Hi,
There seems to be a bug in FOP which apparently doesn't handle nested
lists too well. I'm investigating.
Confirmed. There's an ugly bug related to elastic spaces, I prefer to
not enter the details ;-)
A workaround is to use fixed spaces (minimum = optimum
Hi,
Euis Luhuanam a écrit :
Hi,
I would like to migrate from fop 0.20 to 0.9X.
Unfortunately, it seems not to be straight forward.
I am using Ubuntu Feisty with a 2.6.20-16-generic
kernel; Java2RE 1.5.0_11; xsltproc (libxml 20627,
libxslt 10120; libexslt 813); and docbook-xsl-1.71.1.
[Keep forgetting that reply-to: isn't set to docbook-apps...]
Hi Joseph,
caporale a écrit :
I'm using FOP 0.93, xsltproc, and DocBook 4.5.
Sometimes text appears to almost overlap DocBook's footer line. I've
noticed the problem more when I'm doing lists and especially lists within
lists.
Message original
Sujet: Re: [docbook-apps] Text going out of margins in PDF
Date: Tue, 03 Jul 2007 17:39:00 +
De: Bob Saggot
Pour: Vincent Hennebert
Vincent,
See the bottom of pages 2 and 3. Thanks for taking a look at this.
Joseph
From: Vincent Hennebert
To: caporale
Hi,
There seems to be a bug in FOP which apparently doesn't handle nested
lists too well. I'm investigating.
Vincent
Message original
Sujet: Re: [docbook-apps] Text going out of margins in PDF
Date: Tue, 03 Jul 2007 17:39:00 +
De: Bob Saggot
Pour: Vincent Hennebert
Hi François,
Francois Gouget a écrit :
Hi,
I'm having trouble converting Japanese Docbook/XML documents to PDF. I
have attached a very simple test document as an example (you can also
download it from http://fgouget.free.fr/tmp/docbook/foo.xml in case it
gets mangled in the mail).
I
[Re-sending to the list...]
Jeff Powanda a écrit :
Yes, I've tried using absolute URLs for both the font-base element and
the metrics-url attribute on the font element. Both still result in
the null pointer exception when I run FOP.
Relative URLs should work, both for base and font-base. Are
Bob Stayton a écrit :
This seems to be a bug in FOP 0.93 regarding fo:footnotes inside a
fo:list-block. If you set the stylesheet parameter
glossary.as.blocks=1 then the footnote comes out ok. But it isn't as
nice looking.
I think you could report this as a bug to the FOP developers.
46 matches
Mail list logo