this at the office.
Regards, Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
is the same). I guess
that a dissertation like that cited above contains much more
information than implemented in TeX.
Regards, Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
does.
Regards, Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
already.
I do not have a broadband connection, and therefore no Skype or other
VoIP.
Regards, Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
I don't want to work with a series of patches like
you guys did earlier, I'd like to create a branch to do that on as soon
as we've agreed on a strategy. Any objections to that?
That is a good idea.
Regards, Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
page breaking strategies,
but also help us implement a simple strategy to start with, and
gradually evolve it to a higher level of sophistication.
Regards, Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
be tackled at another time, and perhaps by another team
member. So, please, do not say that a solution is not everything, but
take the opportunity and tackle the problem that remains. Or, if you
have no time, watch it sit there and suffer. :)
Regards, Simon
--
Simon Pepping
home page: http
renderer or in build/test-results/layoutengine when running the Ant
build.
I'll continue investigating but would appreciate any ideas you might
have.
Jeremias Maerki
--
Simon Pepping
home page: http://www.leverkruid.nl
Jeremias,
Note that you can use the ancestor axis:
xpath=//text[. = 'line1']/ancestor::pageViewport/@nr
instead of
xpath=//text[. = 'line1']/../../../../../../../../../@nr
Regards, Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
to evaluate to 'line-through', but got 'li' (XPath:
//flow/block[3]/lineArea/inlineparent[1]/text)
Regards, Simon
On 06.02.2005 13:54:54 Simon Pepping wrote:
Hi Jeremias,
I have errors with the layoutengine test files, for example:
text-decoration1.xml
want to have.
There are many such cases in the test files. I think you should modify
all cases where you test on the content of a text area.
Regards, Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
.
I'll continue investigating but would appreciate any ideas you might
have.
Jeremias Maerki
--
Simon Pepping
home page: http://www.leverkruid.nl
some hints on where i could start
Regards, Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
/
fileset dir=build
include name=fop-transcoder-allinone.jar/
/fileset
--
Simon Pepping
home page: http://www.leverkruid.nl
On Tue, Jan 11, 2005 at 09:25:50AM +0100, Jeremias Maerki wrote:
On 10.01.2005 22:00:01 Simon Pepping wrote:
There does not seem to be a need to add
the inherited value later; the property maker already has done so. See
IndentPropertyMaker.compute(PropertyList). It uses
); ===
}
return enums[enumValue];
}
Regards, Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
(Constants.PR_START_INDENT).getLength();
+inheritedEndIndent = pList.getParentPropertyList()
+.get(Constants.PR_END_INDENT).getLength();
+}
+}
snip/
Jeremias Maerki
--
Simon Pepping
home page: http://www.leverkruid.nl
require.
I believe that releasing is a good thing as soon as we have a usable
product. But it is true that I am not very attracted to such a task at
the moment. Whether instead I am thinking deeply is quite another
matter :)
Regards, Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
is only used if the attribute value is
'inherit'. Otherwise it converts the attribute value into a property
value object. See my description in
http://www.leverkruid.nl/FOP/html/ch09s02.html.
Regards, Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
--or
was this just an oversight? (Actually, anyone know
why we're not making FObj and FObjMixed abstract as
well? I might be missing something here...)
Jeremias Maerki
--
Simon Pepping
home page: http://www.leverkruid.nl
the
whole thing, just to improve what I stumble upon.
I know nothing that speaks against that.
Regards, Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
(foText));
+}
+}
+}
--
Simon Pepping
home page: http://www.leverkruid.nl
out:);
+log.error(e.getMessage());
+return;
+}
--
Simon Pepping
home page: http://www.leverkruid.nl
used, minor bug in
TableLayoutManagerMaker fixed.
Sorry for the regression, and thanks for spotting and fixing it. I
have also taken measures to avoid the tabs.
Regards, Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
to
be developed). Thoughts? Objections?
It is true that nothing has been done to make threading a reality. I
do not object to your removing the Runnable interface.
Are you a fan of Extreme Programming? They seem to teach you to avoid
adding future features.
Regards, Simon
--
Simon Pepping
home page
On Mon, Dec 13, 2004 at 02:26:40PM -0700, Victor Mote wrote:
Simon Pepping wrote:
The code you presented seems to be an algorithm implementing
an iterator over a tree. Because it maintains its state, it
can be stopped and resumed at will, provided you keep a
reference
must be captured
before that flattening takes place? Or are you simply making that an option
now?
Do you want to traverse the FO tree, without relying on the Java
stack, and drive the layout process from there by firing node events?
Regards, Simon
--
Simon Pepping
home page: http
:' are removed. This is probably
due to the fact that the space removal mechanism does not recognize
that fo:retrieve-marker elements may generate text.
Regards, Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
the subtree under the retrieved marker in
LM.preloadnext(), this would prevent later runs with the same FO tree
from reusing markers that would pertain to the layout of an earlier
run.
Regards, Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
Hi,
I have just committed a patch which fixes bug 32253. One problem
remains: the text in the marker does not always have the right
properties, e.g. the right size. This is probably due to the fact that
Marker.rebind() does not rebind the whole subtree below a marker.
Regards, Simon
--
Simon
into Lines,
Software---Practice and Experience 11 (1981) 1119-1184. It should be
possible to find this journal in academic libraries.
Regards, Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
by a block-area generating child. Perhaps it should wrap them
in a Knuth Box of the appropriate width, or in a new class of Knuth
Element, which LineLM would know that it should be placed on a line of
its own.
Regards, Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
methods to extract the layout
part of the configuration and pass it on to a client class,
e.g. LineLM. Cf. FOUserAgent.getUserRendererConfig().
TeX's terms are pretolerance and tolerance for the two values of
maxAdjustment.
Regards, Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
(), plus incompatibleFitnessDemerit, it can never
be selected. The optimization omits it from the list of best
breakpoints. Knuth mentions that it saves him 25% of executions of his
loop, in his computational experiments.
Regards, Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
the
energy that Jeremias has been pouring tirelessly in FOP, Batik, the XML
federation and probably many things here that I don't know about.
Congratulations, Jeremias, and thank you for your efforts.
Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
--
Simon Pepping
home page: http://www.leverkruid.nl
, with proper alignment,
borders, margins, indents, etc.
Regards, Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
to solve.
Indeed. Something like ICLM is needed, which creates an inline area
containing the block areas.
Regards, Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
On Wed, Nov 17, 2004 at 02:25:02PM +0100, Luca Furini wrote:
Simon Pepping wrote:
Marker extends FObjMixed, which adds InlineStackingLM. This is a
problem. In the new model there should be a strict separation between
LMs implementing InlineLevelLM and those that do not. InlineStackingLM
getNextBreakPoss would be
invoked. Apparently I am wrong, and this warrants more study than a
quick solution. I do not have time to investigate this in more depth
during this week. The same for the block-inline-block error.
Regards, Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
.
For RetrieveMarkerLM that separation is not so clear. I think it has
to implement InlineLevelLM, otherwise it cannot act as a child of
LineLM, at the penalty that you noticed.
Regards, Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
before
committing them.
These comments are fine.
Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
which
actions that could be. If you can move all required actions for a new
LM object into the constructor, I have no objection to the removal of
this method.
Regards, Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
will
preclude it from having the same look feel as the rest of the FOP web
site.
A shame; I thought book.xml was the right name for this file. Renamed
to DnI.xml.
Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
]
Webmaster/Developer - Medata, Inc. - http://www.medata.com/
PGP Public Key: https://mail.medata.com/pgp/cleeds.asc
--
Simon Pepping
home page: http://www.leverkruid.nl
looking a little more at
the scientific aspects of this work.)]
I have it. The chapter on the line breaking algorithm is very
enlightening.
Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
-user perhaps you/we should transfer it to a more
'permanent' server (since your e-mail will be in the FOP archives in
perpetuity). I'm thinking that a good to place for this extension is on
the 'Objects For Formatting Objects' Sourceforge project page[2]
(assuming that Simon Pepping
, Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
Luca,
I will try to look at your patch later this week.
Regards, Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
://www.medata.com/
PGP Public Key: https://mail.medata.com/pgp/cleeds.asc
--
Simon Pepping
home page: http://www.leverkruid.nl
, Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
this up.
Regards, Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
of Interface and abstract
implementing superclass? If AbstractCharIterator adds nothing to the
interface, it is better to remove this abstract superclass. It does
implement a few methods, though.
Regards, Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
=allwordssubstrkeywords=keywords_type=anywordsfield0-0-0=nooptype0-0-0=noopvalue0-0-0=cmdtype=doitorder=Reuse+same+sort+as+last+time
--
Simon Pepping
home page: http://www.leverkruid.nl
.
Regards, Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
dependent on one
person.
Regards, Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
explained and this license statement accepted was lengthy. I took care
to state each license carefully in the covering page
http://sourceforge.net/offo/hyphenation.html. For a large part thanks
to Jeremias earlier work.
Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
efforts to realize a valuable open source formatting objects
processor.
As I said earlier, I wish to spend my time on the layout system in the
trunk, which leaves me no time to port FORay's code back into FOP.
Regards, Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
that that is not explained;
the text behaves as if that is the only version of FOP. I will change
that some time.
Regards, Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
hyphenation a top-level package (i.e.,
org.apache.fop.hyphenation). Comments?
I have no problem with your proposal.
Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
On Fri, Sep 03, 2004 at 10:23:27AM +0200, Luca Furini wrote:
Simon Pepping wrote:
You mention that you have not implemented the Knuth algorithm for
ContentLM. Would it be difficult to do that?
No, I have almost done.
I think I will be able to attach a patch including this fix
like you are right. This would apply to a displayed formula
in a paragraph. Nobody would want a layout in which the last line
before the display is justified, so there seems to be a problem here.
Regards, Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
like in such a scenario with the current
code?
The current code breaks the paragraphs into lines. It makes short
lines.
Regards, Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
, but at least
*without* having to rewrite and replace core FO classes.
My thoughts are along the same lines that Jörg has argued. I think we
should do option 2. vCN() should be written such that it allows this.
Regards, Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
inconsistent code. When I apply it to the newer
version, I get errors by the patch program. Can you try to generate a
new patch?
Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
mentioned this--and by virtue of working in
Layout and FOTree, they would presumably come across
this problem much more often.
--
Simon Pepping
home page: http://www.leverkruid.nl
to write
this down more in extenso?
Regards, Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
of difference due to recent cvs commits.
Perhaps you cannot include new files, because as an anonymous CVS user
you cannot add files (cvs add).
Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
can have the default value auto. I think normal
should be a keyword. Apparently, the actual value can only be
calculated at layout time, when the font is known.
Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
that allows the final line of a
paragraph to be shorter than the others'. Setting \parfillskip to 0
removes this ability. Usually \parfillskip has infinite
stretchability.
Regards, Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
be made simpler to allow a decent Java
programmer to add code to the layout system. It is an aspect I want to
pay attention to, but I will take it slowly and cautiously.
Regards, Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
--- Chris Bowditch [EMAIL PROTECTED] wrote:
I think Joerg was saying that the details of the
code are irrelevant to the
end user. I tend to agree with this point, and see
no benefit in removing tbe
AddLMVisitor stuff. So I have to vote -0 as well.
Chris
--
Simon Pepping
home
On Wed, Jul 28, 2004 at 01:24:22PM -0700, Clay Leeds wrote:
On Jul 28, 2004, at 11:51 AM, Simon Pepping wrote:
On Sun, Jul 25, 2004 at 12:51:56PM -0700, Clay Leeds wrote:
As I understand it, you're primarily doing documentation that is more
developer and/or embedded oriented, which is one
directory to commit the
files into? Or shall I create a directory in
src/documentation/content/xdocs? Or in src/documentation/content/?
Regards, Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
). More
recently, I've had some success, but I'm currently working with the
forrest-dev list to get them resolved--and we've made progress[1]
[1a].
I appreciate that that is not an easy problem to solve.
(More comments inline)
On Jul 25, 2004, at 11:41 AM, Simon Pepping wrote:
I have tried
and externally, in object code and, if included
in your
Contributions, source code form) your
Contributions. Except for the
rights granted to the Foundation in this
paragraph, You reserve all
right, title and interest in and to your
Contributions.
Christian
--
Simon
, or am I doing something wrong?
Regards, Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
to be written--many of them
quite complex. Feel free to help out if you'd like!
Glen
--- J.Pietschmann [EMAIL PROTECTED] wrote:
Simon Pepping wrote:
The code in Root shows that fox:bookmarks is the
only allowed fox
child of fo:root. It is not clear that that is
true. The web page
I am preparing my documentation for check-in into the repository. What
would be a suitable place. A directory in
src/documentation/content/xdocs? Would that be in the way of the
forrest build of the web site?
Regards, Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
. Even if it is true, it creates compatibility problems.
Regards, Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
transformations may find a SAXParser example easier to
apply. That was my own situation until this thread.
Regards, Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
it before
returning to the Transformer version. This way, we
have a working example should we ever need to document
this style (perhaps on a web page, so users are at
least aware of it) in the future.
Glen
--
Simon Pepping
home page: http://www.leverkruid.nl
to first construct the user
agent with all desired features and then create a driver with it.
Regards, Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
of an app from each
other. And often it is worth the extra lines of code.
Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
building. Now the area tree activates itself,
based on an event in the FO tree.
I believe this change violates the separation between the FO tree and
the area tree. I think that separation is a good idea and should be
maintained.
Regards, Simon
--
Simon Pepping
home page: http
the reasons one
follows a standard API.
Note that the Xalan and other people call the javax.xml.transform part
TrAX. AFAIK, javax.xml.parsers is also in JAXP.
Regards, Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
On Fri, Jul 09, 2004 at 03:05:11PM -0700, Glen Mazza wrote:
Thanks, Simon. Its good that we have people of your
skill on our team.
Thanks for the compliment.
Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
-generation task. I guess we should
keep it in then.
I support that decision. It is one more entry point for apps. Of
course they can fire off their own SAX events, but if they have a DOM
tree and FOP does it for them, that is nice.
Regards, Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
committers.
That is not a problem. I never publish anything without a copyright
holder. If it goes to FOP CVS and other contributions are merged, then
the copyright holder is just changed, like with source code.
Regards, Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
that may benefit from
customization.
Regards, Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
, Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
one of you could drop them a line...
ExTeX, isn't that the name devised for NTS, but never used? Who are
using that now? Is there development in that area?
Regards, Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
of Docbook 4.2 XML files. Could this be part of
the wiki? Or could it be in CVS?
Regards, Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
on the project anyway.
Regards, Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
. You can see my logging strategy in my recent patch.
In that patch I have also started to use the trace level for very
detailed logging.
Let us discuss a common logging strategy.
Regards, Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
--
Simon Pepping
home page: http://www.leverkruid.nl
post some photos to my web site when I get back.
Peter
--
Peter B. West http://www.powerup.com.au/~pbwest/resume.html
--
Simon Pepping
home page: http://www.leverkruid.nl
and PropertyList.elementName are now
always null, and PropertyList.getElement() now always returns
null. Can you fix that?
Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
to bother with migrating it.
I'm in agreement with you Glen. I'm not motivated to do the migratation and
relearn tools, etc. Lets wait and see how many other projects migrate.
Chris
--
Simon Pepping
home page: http://www.leverkruid.nl
On Tue, Jun 01, 2004 at 12:16:24PM +0100, Chris Bowditch wrote:
Simon Pepping wrote:
Note 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:
Great stuff. Do you think
1 - 100 of 153 matches
Mail list logo