that Luca's patch causes a loop on this block. The null
implementation of AbstractLayoutManager.getNextKnuthElement causes
this. It should be modified to finish the LM:
public KnuthElement getNextKnuthElement() {
setFinished(true);
return null;
}
Regards, Simon
--
Simon Pepping
home page: http
On Tue, May 25, 2004 at 09:56:04PM +0200, Jeremias Maerki wrote:
...should be in place now, thanks to Ted Leung.
It works OK. Thanks, Jeremias, for your attention.
Regards, Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
in your code.
Regards, Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
, Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
be
developed without problems with other work.
Regards, Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
method AbstractLayoutManager.reset(Position pos) could be used to
reset the childLMs and the iterator over them.
Regards, Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
that this is a desirable thing to have. I thought
that it would be several releases away before we could address this.
But if you have a viable solution, by all means show it to us.
Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
.
Regards, Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
I will keep adding my small contribution to the layout
system of the development code.
Regards, Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
, Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
of the
relevant interface.
Regards, Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
this be the right
object to hold a reference to the user configuration?
Your advice would be appreciated.
Regards, Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
href, String base) ?
Note that org.apache.xml.resolver.tools.CatalogResolver is an
implementation of this interface using various sorts of catalogs.
Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
Commons Configuration. They do not yet
have a stable release.
Regards, Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
it is.
Regards
J.Pietschmann
--
Simon Pepping
home page: http://www.leverkruid.nl
+
pushCharCount), null is returned, without checking the exception list and
performing the algorithm.
I'm going to attach the proposed patch and a test fo file which shows a few
examples.
Regards
Luca
--
Simon Pepping
home page: http://www.leverkruid.nl
that.
I do not think that that logic should be duplicated or moved. There is
an inefficiency here, but I do not have any good idea for
optimization.
Regards, Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
or
RemoveC. RemoveB does handle trailing spaces except for the last one.
Regards, Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
I should add that I have realized that the rules of whitespace
handling in the FO spec are quite complicated, and that it is unwise
to handle whitespace outside of the Block.handleWhiteSpace method.
Regards, Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
--
Simon Pepping
home page: http://www.leverkruid.nl
On Thu, Apr 01, 2004 at 04:38:11PM -0800, Glen Mazza wrote:
Team,
I'd like us to go ahead and make Simon Pepping our
newest FOP team member. He has provided steady ML
help and numerous patch contributions for the past few
months, and with the many layout patches that have
been coming
/lppl/ (listed on
http://nagoya.apache.org/wiki/apachewiki.cgi?FOPAudits/March2003)
Regards, Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
associated with the XML file. The docbook stylesheets
are too large and complicated to be applied by a browser. You can only
save the XML file and apply XSL stylesheets to obtain an xhtml or pdf
file.
Mozilla Firefox fails as well.
Same reason.
Regards, Simon Pepping
--
Simon Pepping
home page
On Mon, Mar 15, 2004 at 01:40:59PM -0800, Clay Leeds wrote:
On Mar 15, 2004, at 1:15 PM, Simon Pepping wrote:
Looks good, Simon... I don't suppose you could create a PDF version? (I
know a great XML = PDF conversion tool. :-)) Seriously though, this
looks like a great potential addition
!?
Ive problary been misunderstanding a great deal here - but I hope you can
help me anyway ...
Regards,
Simon Pepping
--
Simon Pepping
home page: http://www.leverkruid.nl
font information into alt-design as compatibly as possible
with HEAD. What do I need?
I am completing my documentation on FOP code, see
http://www.leverkruid.nl/FOP/index.html. I have a chapter on
fonts. Maybe it helps you gain some quick insight.
Regards,
Simon Pepping
--
Simon Pepping
home
,
Simon Pepping
--
Simon Pepping
home page: http://www.leverkruid.nl
parser. In XMLReaderFactory, it may produce an
XMLReader which throws an exception when I want to set the validating
feature on it.
Regards,
Simon Pepping
--
Simon Pepping
home page: http://www.leverkruid.nl
for the maintenance branch.
What are those legal problems? The Dutch file nl.xml is based on the
hyphenation patterns created by the Dutch TeX user group, and are
freely distributed with TeX software. Why cannot FOP distribute them?
Regards,
Simon Pepping
--
Simon Pepping
home page: http
myself though: No change is required. If the layout dimension
is not found on a certain FO, it is looked for at the parent.
Regards,
Simon Pepping
--
Simon Pepping
home page: http://www.leverkruid.nl
, which switches
between building the FO tree and building the area tree. It does not
necessarily mean that information should flow in both directions.
Regards,
Simon Pepping
--
Simon Pepping
home page: http://www.leverkruid.nl
Length iTextIndent;
remove the i from the name; it stands for int.
Regards,
Simon Pepping
--
Simon Pepping
home page: http://www.leverkruid.nl
to the percent based length types listed in
LengthBase.
Regards,
Simon Pepping
--
Simon Pepping
home page: http://www.leverkruid.nl
On Sun, Feb 15, 2004 at 10:43:12PM +0100, Finn Bock wrote:
[Simon Pepping]
Finn,
I think it
would be a better design if, in order to resolve the percent-based
properties, you would not climb the FO tree but the Area tree. That
avoids feeding back results from the Area tree into the FO
On Mon, Feb 16, 2004 at 08:22:31PM +0100, Andreas L. Delmelle wrote:
-Original Message-
From: Finn Bock [mailto:[EMAIL PROTECTED]
[Simon Pepping]
snip /
However, I am not happy with your
solution. During the layout process, you feed the page dimensions back
into the FO
On Sun, Feb 15, 2004 at 10:43:12PM +0100, Finn Bock wrote:
[Simon Pepping]
I initially had a separate PropertyContext object where the length was
stored. The FO element then had a reference to the PropertyContext and
there was a PropertyContext for every FO. But since there was a
one
. The point here is the
implementation, which had a small glitch.
The enclosing block is the page. It is not really the enclosing block
of the simple-page-master, nor of the region-body, but of the areas
they generate. Resolution is done w.r.t. the area tree.
Regards, Simon
--
Simon Pepping
home page
Quite a piece of work. I will try to understand it.
A small correction:
On Sun, Feb 08, 2004 at 10:03:57PM +0100, Finn Bock wrote:
margin-[top,bottom]:
width of containing block, except for page context where it
^
height (I suppose).
Regards, Simon
--
Simon Pepping
when all
its forward references are resolved? At that point it is rendered, but
the PDF renderer should insert it at the proper position. That does
not seem to happen.
Regards,
Simon Pepping
--
Simon Pepping
home page: http://www.leverkruid.nl
with the others.
3. Should ToBeImplemented.java also be removed?
A lot of good work.
Regards,
Simon Pepping
--
Simon Pepping
home page: http://www.leverkruid.nl
On Sun, Jan 25, 2004 at 11:38:14PM +0100, Finn Bock wrote:
[Simon Pepping]
I have just catched up with the massive changes to the property
system. Allow me to share a few observations:
Thanks for your comments. How do you otherwise think it compares to the
previous generated property
only once?
Regards,
Simon Pepping
--
Simon Pepping
email: spepping AT leverkruid.nl
home page: http://www.leverkruid.nl
and fo.properties.Constants.java/class as
previously generated from codegen. The former of these causes ant not
to rebuild the class fo.Constants from the corresponding new code in
src, thus leaving out the new constants that were declared in the
latter.
Thanks, Simon
--
Simon Pepping
email: [EMAIL PROTECTED
/xsl:text
The old code applies a precise test for the inclusion of the import
statement. My change includes the import statement in all property
makers. Not sure what a more precise test would look like, and if
there can be any.
Regards, Simon
--
Simon Pepping
email: [EMAIL PROTECTED]
home page
.
These are my thoughts on the process.
Regards, Simon
--
Simon Pepping
email: [EMAIL PROTECTED]
home page: http://www.leverkruid.nl
public key: http://www.leverkruid.nl/personal/sp.asc
fingerprint: E3BF 7295 9AA8 8B8A C01A 219D FAAC 088C 6B28 F549
. Therefore, before dealing with the compound attribute, the
base attribute should be processed if that is specified as well.
This would be different if the compound property would not be filled
with default components, but with null components.
Regards, Simon
--
Simon Pepping
email: [EMAIL PROTECTED
which is incorrect with regard to namespaces.
at org.apache.xerces.dom.CoreDocumentImpl.checkDOMNSErr(Unknown Source)
at org.apache.xerces.dom.AttrNSImpl.setName(Unknown Source)
at org.apache.xerces.dom.AttrNSImpl.init(Unknown Source)
Regards, Simon
--
Simon Pepping
email
-site=15ptbar/fo:inline/fo:block
I think this should generate two spaces between foo and bar.
[Andreas L. Delmelle]
One in 10pt, the other 15pt, or 2 spaces of 20pt?
[Simon Pepping]
I would think one space before foo according to the characteristics of
the 20pt font and bgcolor red,
I
-site=15ptbar/fo:inline/fo:block
I think this should generate two spaces between foo and bar.
[Andreas L. Delmelle]
One in 10pt, the other 15pt, or 2 spaces of 20pt?
[Simon Pepping]
I would think one space before foo according to the characteristics of
the 20pt font and bgcolor red,
I
to the characteristics of
the 20pt font and bgcolor red, and one after foo according to the
characteristics of the 10pt font and bgcolor blue. I see no space in
the bar inline.
Regards,
Simon Pepping
--
Simon Pepping
email: [EMAIL PROTECTED]
home page: http://www.leverkruid.nl
On Wed, Nov 26, 2003 at 08:21:33PM +1000, Peter B. West wrote:
Simon Pepping wrote:
I have taken a look at the way this question is dealt with in LaTeX
(TeX does not have the notion of font families, LaTeX does). Here the
question what to use for small caps font is deferred to the font
setup
should
not believe what these notes say. If you do, and you act accordingly,
you do so at your own risk.
The notes can be found at: http://www.leverkruid.nl/FOP/index.html
Regards,
Simon Pepping
--
Simon Pepping
email: [EMAIL PROTECTED]
home page: http://www.leverkruid.nl
anything about
this. It should all be configured in the font system. That is how the
user imposes his choice of fonts.
With kind regards,
Simon Pepping
On Thu, Nov 20, 2003 at 09:22:41PM +0100, J.Pietschmann wrote:
Victor Mote wrote:
Typeface roughly corresponds to what is contained in a ttf
101 - 153 of 153 matches
Mail list logo
