I agree with you (except for the last statment about one line).
I found this statement interesting:
6.6.7. fo:inline
"An fo:inline that is a child of an fo:footnote may not have block-level
children. An fo:inline that is a
descendant of an fo:leader or of the fo:inline child of an fo:footnote
Peter B. West wrote:
> Does anyone know what happened to fop 19? Did the tag go away? It does
Probably there has never been one ..
> not show up in a cvs status of build.xml. I ask because the starting
> point for my code was 19, and I would like a point nearby to branch from
> for my init
Buchtík, Michal wrote:
> Hi Fops,
> I translate messages and resources for AWT viewer, can you commit it?
> It's in ISO-8859-2 coding.
Does this work with current maintenance branch (or 0.20.3 final) ?
The reason I'm asking is that the enconding of the resources has
been changed to utf-8 with fop
Hi, i forgot for encoding change.
I convert it to UTF-8 a test it with current maintain branch.
It works ok.
See new attachment.
Thanks for notice.
Michal
-Original Message-
From: Christian Geisert [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 02, 2002 11:45 AM
To: [EMAIL PROTECTED]
Sub
Hi, Keiron
I think what I should do is establish a section on the website with all the
other design notes that is a central location for these kinds of studies.
This could be the first one. I can undertake to start churning these out on
a fairly regular basis - I think we need them.
Once they ar
chrisg 02/05/02 04:01:22
Modified:.Tag: fop-0_20_2-maintain CHANGES
Added: src/org/apache/fop/viewer/resources Tag: fop-0_20_2-maintain
messages.cs resources.cs
Log:
Added czech translation for AWT viewer
Submitted by: Michal Buchtik <[EMAI
When trying to process my fo-file I get the following error:
FATAL ERROR: 'master-reference' for 'fo:page-sequence'matches no
'simple-page-master' or 'page-sequence-master'
My "header" looks like this and is copy/pasted from the examples
http://www.w3.org/1999/XSL/Format";>
Buchtík, Michal wrote:
> Hi, i forgot for encoding change.
> I convert it to UTF-8 a test it with current maintain branch.
> It works ok.
> See new attachment.
Committed, thanks for your contribution.
> Thanks for notice.
> Michal
Christian
I have a fo document for printing mailing labels and positioning on the
printed document needs to be exact. FOP generates a perfectly spaced PDF
document, but when I print it, Acrobat scales it down a bit and throws the
whole thing off. Digging around I found that unchecking "Shrink oversize
Your stylesheet still uses pre-Recommendation XSL:FO. Please see the
release notes for instructions to resolve this:
http://xml.apache.org/fop/relnotes.html
> When trying to process my fo-file I get the following error:
> FATAL ERROR: 'master-reference' for 'fo:page-sequence'matches no
> 'simple-
Title: Message
Hi
all,
Sorry in advance if
I'm not doing this right, it's my first official contribution (or attempt
thereof) to FOP!
I ran into issues
where my servlet was getting installed and run from a number of locations,
making the relative paths in fop-userconfig.xml not work, so
I have a fo document for
printing mailing labels and positioning on the printed document needs to be
exact. FOP generates a perfectly spaced PDF document, but when I print it,
Acrobat scales it down a bit and throws the whole thing off. Digging
around I found that unchecking "Shrink ov
David Frankson wrote:
> I have a fo document for printing mailing labels and positioning on the
> printed document needs to be exact. FOP generates a perfectly spaced PDF
> document, but when I print it, Acrobat scales it down a bit and throws the
> whole thing off. Digging around I found th
I've been working on a schema for FO documents so that I can off-load
the validation chore. I created the schema from the W3C documents which
state the following for table-cell:
Contents:
(%block;)+
In addition this formatting object may have a sequence of zero or more
fo:markers as its init
Arved, Keiron et. al.
I guess logically it's true that the blocks nested in inlines should be
wrapped in inline areas, but it makes me nervous :-)
At least they cause line breaks, that much seems sure. I still think
that we should put pressure on the spec editors to either get rid of
structure or
chrisg 02/05/02 15:27:25
Modified:.Tag: fop-0_20_2-maintain build.bat build.sh
build.xml buildtools.xml
Removed: lib Tag: fop-0_20_2-maintain xalan-1.2.2.jar
xalanj1compat.jar
src/org/apache/fop/tools/xsl
I wrote a test document that implemented all of the enumerated values
for block attributes. Here are the results where FOP complained. All of
the other enumerated values seem to be implemented. For the value
"inherit" FOP implements inheritability. It just doesn't recognize the
inherit enumera
Comments inline...actually, no, they're not, they are really block-stacking,
but you get the drift. :-)
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
> Karen Lease
> Sent: May 2, 2002 7:21 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [REDESIGN] Line la
Comments below.
> -Original Message-
> From: Chuck Paussa [mailto:[EMAIL PROTECTED]]
> Sent: May 2, 2002 7:16 PM
> To: [EMAIL PROTECTED]
> Subject: What the spec says about table-row, table-cell etc.
>
>
> I've been working on a schema for FO documents so that I can off-load
> the validat
Karen,
Comments below.
Karen Lease wrote:
>Arved, Keiron et. al.
>
>I guess logically it's true that the blocks nested in inlines should be
>wrapped in inline areas, but it makes me nervous :-)
>At least they cause line breaks, that much seems sure. I still think
>that we should put pressure on
Arved,
This is a good idea. I half-heartedly suggested as much to Matthew
Huggett when he asked what a non-programming technical writer might
contribute. It requires too deep an insight into the spec, but he (or
Cyril) may of some assistance to you.
What would be even more generally useful wo
21 matches
Mail list logo
