Rodolfo M. Raya wrote:
Does anybody have a routine to reorder BIDI text?
You can use java.text.Bidi from jdk1.4 and sun.awt.font.Bidi in jdk1.2/1.3,
they provide basic BIDI facilities. The problem is that java.text.Bidi is
since jdk1.4 and sun.awt.font.Bidi does not exist in jdk1.4. So I suggest
Michael Schnuerle wrote:
I've got 4 logos to submit to the logo contest. I found out about it
last week, worked on them this weekend, and read today the deadline was
Friday. Regardless, I hope they can be consided in the voting. They
are all in .gif format. I have them in SVG, but each has
On Tue, 2003-03-04 at 08:20, Oleg Tkachenko wrote:
Rodolfo M. Raya wrote:
Does anybody have a routine to reorder BIDI text?
You can use java.text.Bidi from jdk1.4 and sun.awt.font.Bidi in jdk1.2/1.3,
they provide basic BIDI facilities. The problem is that java.text.Bidi is
since jdk1.4
Let's try this code (I did not test it):
substitute:
fo:table-row
fo:table-cell
xsl:apply-templates select=paragraph/
/fo:table-cell
/fo:table-row
through:
xsl:for-each select=paragraph
fo:table-row
I don't see a problem with having the userconfig.xml in the WAR. It's
pretty read-only in there and it's only a one-liner in your code.
If you absolutely want to change the default font setup you should have
a look at org.apache.fop.render.pdf.FontSetup.java. This is where the
default fonts get
On 03.03.2003 10:55:10 H. krishna wrote:
Hai Everybody,
1. I need the placement of FIGURE TABLE is top of
page only. how to define in the fo file. The
fo:float is not implemented (fop-0.20.5rc2).
I am already post this problem.
I'm not sure I get you right, but you can specify
Dear Jeremias Maerki,
Thanks for your mail. i am used
linefeed-treatment=preserve this is correct (or)
not.
I'm not sure I get you right, but you can specify
fo:block break-before=page
[..my stuff on top of the page..]
This tells FOP to start a new page and new content
is started
Well.
1. Which FOP version are you using?
I'm using the 0.20.5rc2 version of FOP, since I had some problem with the
markers with the last official release 0.20.4, which ere corrected in this
candidate.
[white-space-collapse=false].
2. Don't use this.
Yep, you're right ! This tag was
On 04.03.2003 15:30:33 H. krishna wrote:
Thanks for your mail. i am used
linefeed-treatment=preserve this is correct (or)
not.
Depends on your input XML. If there are linefeeds in there, these could
be responsible for the linefeed. Try experimenting a bit. Change
linefeed-treatment etc.
Hi,
I'm using Adobe 5.0
-Type 1 font
-previous is 0.20.4
font metrics-file=/nas/web/fonts/ITCGaraBold.xml
kerning=yes
embed-file=/nas/web/fonts/GAB_.PFB
font-triplet name=AGaramondBD style=normal weight=normal/
/font
fop log see attachment
Thanks
Lucian Opris
-Original
Dear Jeremias Maerki,
I am attached my fo file. I like my pdf file is:
Page 1:
Paragraph 1
Paragraph 2
Paragraph 3
Paragraph 4 Not finished
Page 2:
Figure 1
Paragraph 4 continued text
Paragraph 5
Paragraph 6
Paragraph 7
Paragraph 8
Page 3:
Figure 2
Paragraph 9
Paragraph 10
Paragraph 11
Hi !
I would like to now your point of view on this subject :
I want to use the text-transform=uppercase attribute in a fo:block tag,
but I saw in the output console that it was not implemented yet (using
0.20.5rc2), so I am wondering on the best way to implement it with xsl...
I thought
Hello Simon
You can use the XSLT translate-function to change to upper-case. (See
example below)
xsl:call-template name=toUpperCase
xsl:with-param name=wort select=name/
/xsl:call-template
!-- = --
!-- Translates a String to Upper-Case --
!--
Your stuff works here on Windows XP with the latest FOP and using
Acrobat Reader 5.05. The only thing I changed was using Windows-style
filenames and weight=bold because it's a bold font. But the latter is
probably insignificant.
Try using URLs instead of filenames:
Hmm, looks like you really need fo:float for this, which isn't
implemented. You probably need to find a different layout. What you can
do is counting lines and sort of do the page-breaks yourself. That has
been discussed before on this list but it's difficult, pretty hacky and
does not guarantee
Thanks for the reply Oleg,
Multithreaded access isn't a requirement, so we are in the clear there.
The requirements are simple:
1. TIFFs must use comp group 3x or greater
2. Must be able to set (or even hardcode) the width and height.
3. Must be able to split each page of the XSL-FO doc into
Simon,
I have found good success with using a table for my XSL-FO table of contents
output. It makes lining up the leader lines and page numbers much easier. It
is not wholly elegant, but it works great.
Mark Dudley
Xerox Corporation
-Original Message-
From: [EMAIL PROTECTED]
Thanks for your help Helmut.
I haven't find better way to do it !
Cheers,
Simon
Hello Simon
You can use the XSLT translate-function to change to upper-case. (See
example below)
xsl:call-template name=toUpperCase
xsl:with-param name=wort select=name/
/xsl:call-template
Title: RE: FOP output to TIFF
David:
I ran into many of the same issues you did rendering to TIFF.
I used Oleg's TiffRenderer:
The Black and White thing is really a Windows imaging issue. I got around this by using Alternatiff browser plug-in, or viewing my TIFF's on a non-windows based
Title: Message
Thanks
for the feedback.
Unfortunately, the black vs. white things is not up to my
interpretation. This is part of an already existing and heavily used
document archival application (written in VB). So it's too late to change
requirements.
What
workaround did you use for
Title: Message
I
really never solved this one
sry
Rob
-Original Message-From: David Blevins
[mailto:[EMAIL PROTECTED]Sent: March 4, 2003 2:59
PMTo: [EMAIL PROTECTED]Subject: RE: FOP output to
TIFF
Thanks for the feedback.
Unfortunately, the black vs. white things is
[EMAIL PROTECTED] wrote:
I want to use the text-transform=uppercase attribute...
I thought about using the xsl translate(string,string,string) function,
but I don't think that's the best solution and I'm sure there is a better
way to do that.
There is *no* better way to do this until locale
[EMAIL PROTECTED] wrote:
Please note that I don't want to use a proportionnal (like Courier) font
in my Table of Content, cause I have some graphical obligation.
The problem is not caused by the font, it is caused by the problem
that FOP has to reserve space for the page numbers at a time when
J.Pietschmann wrote:
[EMAIL PROTECTED] wrote:
Please note that I don't want to use a proportionnal (like Courier)
font in my Table of Content, cause I have some graphical obligation.
The problem is not caused by the font, it is caused by the problem
that FOP has to reserve space for the page
Consider this FO snippet:
fo:page-sequence master-reference=CoverPage
force-page-count=odd
[...Cover page...]
/fo:page-sequence
fo:page-sequence master-reference=ContentPage
initial-page-number=1
fo:flow flow-name=xsl-region-body
fo:block font-size=22pt break-before=page
Clay Leeds wrote:
When you say this bug is fixed in CVS do you mean that it's fixed in
the maintenance branch (i.e., the soon-to-be-released 0.20.5/0.20.5rc3
version)
Yes.
There is a CHANGES and an archive for the commit messages at
http://marc.theaimsgroup.com/?l=fop-cvs
J.Pietschmann
26 matches
Mail list logo
