Hello Arne,
keep-with-previous, keep-with-next and break-* are supposed to work on
table-row objects. However, I'm pretty sure there are still some bugs in
there. Could you send an example of your FO file to the list and point
out the problem?
Regards,
Karen Lease
Arne Pingel wrote:
I have
Hi all,
I see there are several of these. I guess they are coming from the
automatic nightly build. The exception is being thrown by the stylesheet
itself because one of its named templates sees an unexpected situation.
Since none of the xsl or foproperties.xml files in codegen has been
touched
Hi Weiqi,
A few weeks ago, you asked some questions about cell borders. You'll
probably notice now that using border-collapse=collapse works better,
thanks to Ivan Demakov's recently contributed fix.
However you made another observation which I finally got around to
checking out:
You wrote,
Hi,
While debugging a strange problem from John Wyman recently, I discovered
an inconsistency in how we decide whether a block area has room for
another line of text. It works differently on the first line in the
block from the remaining lines.
This isn't necessarily stupid, at least for some
Hi Weiqi,
There are some slight improvements in the current CVS.
border-collapse=collapse is working better, at least in cases where
all the cells have the same size borders.
The handling of border specifications on the rows is still not done: it
should be taken into account on the cells in the
Hi Keiron,
It looks like you are the testing guru. Thanks for taking the initiative
on this; I agree that it's crucial.
I've finally got around to looking at this in more detail, as I'm trying
to add some good cases for tables. I have one problem and one question.
Problem:
For some reason,
Keiron Liddle wrote:
On Fri, 06 Jul 2001 23:33:21 Karen Lease wrote:
Hi Keiron,
Problem:
For some reason, certainly relating to ClassLoader behavior, if I run
build.sh test in my xml-fop directory, the version checking code in
RunTest is finding the ./conf/config.xml file locally
Keiron Liddle wrote:
Then after that I will see about handling the element child constraints (I
haven't worked out how this should be done yet, any ideas) and doing a
similar thing (to be impl.) with the rest of the elements that we don't
have yet.
For things like tables, I had
Hi Mark,
To fix the error messages, please build the clean target and then
rebuild. New properties added have changed values for a lot of constants
and all the classes need to be recompiled.
HTH,
Karen
Mark Lillywhite wrote:
Hi foppers
I just checked out the latest fop from CVS (after a
, including the
famous inherit keyword for all properties. In short, there is still
plenty of work in there for some enterprising person(s).
Regards,
Karen
Arved Sandstrom wrote:
At 10:25 PM 7/11/01 +0200, Karen Lease wrote:
Keiron Liddle wrote:
Then after that I will see about
which is being created by your XML and XSL so that I can check it out.
HTH,
Karen Lease
Huisking, Michael wrote:
Hi.
My xsl-region-body is defined like this:
fo:flow flow-name=xsl-region-body
fo:table border-style=solid border-width=0.5pt
xsl:copy-of select
Hi all,
Since I'm doing table work now, I'll try to have a look at this and see
if it can fixed.
Regards,
Karen Lease
Eric Galluzzo wrote:
Good question. Does anyone knows how to vertically center text in a
table-cell?
I'm afraid that I don't. :)
I tried display-align=center
Hi all,
I can't seem to get a cvs connection to xml.apache.org right now, either
over ssh or anoncvs. Over the ssh bridge with localhost, I get cvs
[login aborted]: recv() from server localhost: EOF
And using the public cvs access, I get
cvs [login aborted]: connect to xml.apache.org:2401
Bonjour Jean-Claude,
That looks like the sort of problem I might be working on soon. I'll let
you know if and when I get it fixed.
Salut,
Karen
GALLO Jean-Claude wrote:
I would like to create a fo:table inside which a fo:table-cell contain
another fo:table. Everything goes fine while you
Hi,
Yes, the number-rows-spanning property on table-cell IS now implemented,
but only in the CVS version, not yet in the last release (0.19). If you
want it before the next release (hopefully coming up fairly soon,
Arved???), you'll have to use the CVS sources.
Unfortunately, the
Hi all,
I'm still slogging away with tables, trying to get eliminate border
drawing errors. I think I've made some progress, both in the table and
in the rendering code.
I finally discovered why the background rectangles were hanging out a
pixel or so beyond the borders (at least in PDF). When
and the 4 side regions must be positioned.
It's a little complicated; try looking at the diagrams in the XSL CR
specification in 6.4.12 and 6.4.13.
Hope that helps and happy Foppin'
Regards,
Karen Lease
David S. Dixon wrote:
Greetings,
I generated the attached test.fo file in Java
Hi Petr,
It should work now (CVS from tonight), except when you also have a
height property on the same cell. It's OK if you have a height property
on the row containing the cells with display-align.
Regards,
Karen
Petr Andrs wrote:
Hi all,
can anybody suggest me how to vertically center
Hi Gregor,
If you are still stuck, I have a few more ideas of things to try.
./build.sh -version
Ant should print out its version number
(I get: Ant version 1.3 compiled on March 2 2001)
If you still get nothing, try running ant from the command line directly
(from the same directory where you
there is more code to
see what to do with spaces, which is more complicated. I'm not
necessarily asking you to try to fix the bug I mentioned, but thought
you might have something to say about it.
Regards,
Karen Lease
Tore Engvig wrote:
On Mon, 23 Jul 2001, Rainer Garus wrote:
Is it possible
/ and then follow it directly with your
absolutely positioned block-container?
Or are you trying to do something else?
Regards,
Karen Lease
ROUGIER Bertrand wrote:
I put a fo:block break-before=page/ inside a fo:block-container
to get a page break but it doesn't work.
When I put fo:block break
Jim,
Is it possible for you to test with the latest CVS version of FOP? If
not, there will soon be a 0.20 release. I've done some more work on
tables since the 0.19 release jar so perhaps it will work better. If
not, please write again, with an example if possible.
Thanks,
Karen
Jim Urban
appears as fixed because of the recent changes -
but it might because the LineArea constructor now discards some pending
InlineSpaces.
I'll take a look at it.
Tore
On Tue, 24 Jul 2001, Karen Lease wrote:
Hi Tore,
While you're looking at whitespace in LineArea I thought you might
Oops, I just realized I commented out my hack, but didn't save before
building. In fact the empty table row is still there. Can't win 'em
all.
Karen Lease wrote:
Hi Tore,
Great, I checked it again too (without the hack I had put in..) and it
works. The table bug reported was actually
Hi Petr,
I've looked at this quickly and my first reaction is that it's probably
not specific to tables. I think it has to do with line-height (aka
leading in old typographic terms). Neither font-size nor line-height are
specified at a high level in your .fo. The default font-size is 12pt and
,
Karen Lease
[EMAIL PROTECTED] wrote:
Hello,
In the fragmant below i have two nested blocks. if I process the file with
XEP the second block has a left margin of 1in relative to the margin of
the
outer block (so 2 inch in total). if I process this with FOP both blocks
have
the same margin of 1
(the four bottom lines) has its own unique height
of line. So it maybe has something to do with usage of font metrics.
Petr
On 5 Aug 2001, at 0:16 Karen Lease wrote about Re: problems with height of cells i :
Hi Petr,
I've looked at this quickly and my first reaction is that it's probably
Arved Sandstrom wrote:
At 12:22 AM 8/6/01 +0200, Karen Lease wrote:
So much for the explanations. Unfortunately, I'm not sure I'll try to
fix this right away, since I fear that it involves some rather major
changes. It really comes down to the fact that the fo:inline object
doesn't
message so one of us can take a look at it.
Regards,
Karen Lease
Arnaud Carrard wrote:
Hi,
I cannot access the FOP-FAQ on the xml.apache.org web
site, concerning the use of FOP, so I write directly
to this list.
I would like to apologise in advance because I am a
real beginner
Hi Emmanuel,
As you say, the problem seems to be in processing the XSL. That isn't
really done by FOP, except by calling Xalan (or some other kind of Trax
compliant transformer.)
Sounds like one of two things: obscure classpath problem or problem with
the Sun JDK 1.3.1 itself on Win98. Do you
Koen (and Ralph and others),
There is a problem, but it's not a border-drawing problem.
You have a left-margin specified as 2cm on a block which is containing
the paragraphs before the table and the table itself. This property is
inherited and is therefore used on both the fo:table and the
Hi Arved (and other interested parties),
Lots of other bugs (like the inline-area height) show up well in tables
because the grid makes things visible. That's the case with the trailing
white-space bug I saw the other day, resulting in an empty table row.
Some of these can also be shown by using
.
(Sorry if you'd already done this; I've been away for a few days and
might have missed an earlier message in the stack I went through last
night.)
Regards,
Karen Lease
P.S. Also, I believe the 0.20.1 version of FOP should fix the problem
you reported in late July concerning vertical alignment in table
Hi Eric,
Sorry if no one has answered your plea before now.
Unfortunately (or perhaps fortunately?) I don't have any problem with
the example you sent. I'm using the latest CVS, but if you are using an
earlier version of FOP, you probably should try with the latest release
which is 0.20.1.
I've
the base URI of the node, which would seem to be the base
URI of the XML document containing the node. The documents FOP is trying
to process are in the same directory as the original XML documnent being
processed.
I think the FOP XSL is correct, but of course, I could be wrong...
Regards,
Karen
Struan,
Oops, I hadn't noticed the second version of addLine taking the
ruleStyle since it wasn't being called in the doFrame stuff when I made
my change. Duhh.
The baseline alignment stuff is harder than the straight after align.
Our line-height calculations need to be right before we get into
reproduce this behavior with the border.fo file.
Or perhaps I don't understand what you mean?
Hope that helps a bit,
Karen Lease
Steve McCardle wrote:
Hi,
Firstly, ... am I in the right place for queries of this nature ? (I've
tried fop-dev-help fop-dev-info already !)
I'm completely
Hi fellow foppers,
Concerning the recent GUMP build failures, Sam Ruby wrote:
... the following change:
http://cvs.apache.org/viewcvs.cgi/xml-xalan/java/src/org/apache/xalan/templates/FuncDocument.java.diff?r1=1.23r2=1.24
..causes the following build failure:
Hi Keiron,
I'd like to think about Layout Managers, but I'd be more than happy to
bat ideas around with anyone else who's interested in that.
Karen
Keiron Liddle wrote:
Hi All,
These are the design tasks that I think we need to cover before (serious)
coding is done on the new layout
and then rebuild the buildtools.jar.
using the command build -buildfile buildtools.xml in your xml-fop
directory.
Hope that helps you.
-Karen Lease
Bodo Teichmann wrote:
Keiron,
now i got the pdf but still have the following problems:
1. the relative uri in fop.xml do not work. i get the following
Hi Suhail,
Actually to keep two different FO together, you need to use
keep-with-next or keep-with-previous. The keep-together property means
to keep an entire FO in the same page or column (if possible). For
example, if you put keep-together on an fo:block, FOP should try to keep
the whole
I guess I'm not yet 100% where the boundaries between all this stuff is.
Too bad we can't do a whiteboard session...
-Karen
Arved Sandstrom wrote:
At 10:56 PM 9/10/01 +0200, you wrote:
Hi Keiron,
I'd like to think about Layout Managers, but I'd be more than happy to
bat ideas around
Hi Steven,
I hate to tell you this, but 0.14 is a REALLY OLD version of FOP and no
one here is probably going to be able to help you. The best thing would
be for you to update your FOP distribution (http://xml.apache.org/fop)
and get the latest 0.20.1 version. The command line has changed but
Hi Corinna and welcome back,
Your idea sounds quite good to me. Speaking as a committer, I'm sure I
could spare a few minutes every now and then to commit the bugtest
files. Actually I've got rather a bunch of files lying about already
with names like bug1234.fo :-)
Since you've been absent for
Hi Keiron,
I'll fix the bug 3531 (column-number attribute not working on
table-column) before the release unless you're already working on it.
Also willing to give a hand with updating the website.
Regards,
Karen
PS. I'm working away on LayoutManager ideas and hope to contribute
something
Hi Amit,
The number-rows-spanned property is now implemented in FOP, but it
wasn't yet in 0.18.1. If you want to use it, you should download the
latest version of FOP from the website - that's 0.20.1.
Regards,
Karen
[EMAIL PROTECTED] wrote:
I'm not sure if this is the right place to ask
Hi all,
I've been turning over some ideas about LayoutManagers, FOs and Areas
and what's responsible for what.
I've concentrated for now on the layout of inline stuff, for two
reasons:
a) we know the current area tree is incorrect at this level
b) if we don't make Lines, the Block LayoutManager
Karen Lease wrote:
Hi Amit,
The number-rows-spanned property is now implemented in FOP, but it
wasn't yet in 0.18.1. If you want to use it, you should download the
latest version of FOP from the website - that's 0.20.1.
Regards,
Karen
[EMAIL PROTECTED] wrote:
I'm not sure
You could try using getOutputStream and then building your own Writer by
putting on an encoding. The IllegalState is because you can't use the
Writer and the OutputStream in the same servlet.
But it seems to me if you've already written something to the output and
the FOP output is appended on to
Keiron Liddle wrote:
Hi All,
I have been doing some performance testing so we can get an idea of how
things might be improving (or getting worse) with changes to the code.
[snip]
So the question is: can we drop java 1.1 support and use better data
structures?
Interesting results!
With
Paul,
It looks like the ParserFactory is looking for (and not finding) the
Sun parser rather than the xerces parser which comes with the Fop
package. This could be due to having an old version of the jaxp.jar or
parsers.jar (or maybe crimson.jar) on your classpath. Is the CLASSPATH
variable set?
and fonts. When running FOP from the
command line, most of the configuration work happens in the Options
class (org.apache.fop.apps), so you might want to look at that too.
Regards,
Karen Lease
Joerg Pietschmann wrote:
Hello,
i use FOP in a servlet together with the Saxon XSL processor.
I
shot in a Word document). (Or perhaps putting error.txt after
your command line will put the output into a file which you can send.)
You probably also want to attach your xsl and xml files if they are a
reasonable size.
Regards,
Karen Lease
Siarom Egrub wrote:
Hi All,
Please assist me
I think anything we can do to encourage the use of XSL-FO is a good
thing, especially now that XSL is finally a W3C Recommendation.
+1
Regards,
Karen Lease
Stefano Mazzocchi wrote:
Hi people,
recently, some code was donated to the Apache Cocoon project in order to
connect it with JFor
Hi Chris,
Yes, definitely try a more recent version. The latest is actually
0.20.2. That should have support for setting height on either row or
cell and maybe some sizing problems have been fixed. To prevent rows
being broken, use keep-together=always on the table-row object. That's
the only
Well, no, actually the XSL Recommendantion says that padding doesn't
apply to table-row (See 6.7.9 and the Note about Common Border,
Padding and Background properties.
Using padding on table-cell is the correct solution.
Regards,
Karen
Keen Tim wrote:
I'm attempting to use padding-top and
you're seeing it.
I'll try to look into it again.
Regards,
Karen Lease
Guillaume Rousse wrote:
Sorry if this has already been asked there, but list archive are currently
unreachable.
The current fop version (0.20.1) ships with xalan-j 2.0.0, and builds fine.
Trying to build it with current
parlait Karen Lease :
I committed into CVS 26.8.2001. So it wasn't in 0.20.1 but it should
certainly be in 0.20.2RC.
However, 0.20.2RC compilations fails with current batik 1.0 release:
[javac]
/home/guillaume/rpm/BUILD/Fop-0.20.2/build/src/org/apache/fop/svg/PDFANode.java:55:
paint
Matt,
The short answer is no. The value must be specified as a fixed length
or as a percentage which is interpreted relative to the page height, so
it's still a fixed value.
So your options are:
1) make extent large enough to contain your biggest possible header
2) depending on the structure of
and look at the
Tutorials/Articles section.
Good luck,
Karen Lease
Rossi, Bernard L. (LNG) wrote:
How would you transform something like this to pdf?
entity_keys.xml
Thanks.
Bernie Rossi
Name: entity_keys.xml
entity_keys.xmlType: unspecified type (application
cases yet, though
I've got some ideas for float management in the back of my mind.
Regards,
Karen
Arved Sandstrom wrote:
At 12:05 AM 11/10/01 +0100, Karen Lease wrote:
Hi all,
An initial version of the Layout Manager classes (package
org.apache.fop.layoutmgr) is now in CVS, plus some
Hi all,
An initial version of the Layout Manager classes (package
org.apache.fop.layoutmgr) is now in CVS, plus some related changes in
Area (up for discussion; this is just past the pseudocode point, but at
least it builds :-) and in the fo/pagination classes.
Needless to say, it does nothing
it on to
the render. Then the completed fo elements that made up the page can be
discarded.
Rather than always waiting for a page sequence to end, which is easier but
not better.
Regards,
Keiron.
On 2001.11.10 00:05 Karen Lease wrote:
Hi all,
An initial version of the Layout Manager classes
before the fop.jar in the binary build. Maybe that will work.
Good luck,
Karen Lease
Jaron J. Rubenstein wrote:
FOPers,
I have been working through an odd XSL-FO for the past few days. I would
truly appreciate some assistance in getting this to work (or at least
confirming that it's a bug
to make things more
explicit for FOP. However, you should be able to get about the same
result.
Good luck,
Karen Lease
Siarom Egrub wrote:
Hi All,
Thanks for your input. I enclosed a copy of error.txt along with the XML and XSL
files. These are just test files, as I am trying to get acquainted
interface. You can also just use
an XSLT engine to generate an FO file directly so that you can see
exactly what you are sending to FOP.
However that isn't enough to explain the extreme slowness you see. There
must be some other place in your servlet which is taking time.
Good luck,
Karen Lease
Pablo
Hi Scott,
It sounds like you may be putting the background on the block containing
the text. Try putting it on the table-cell itself or even on the row.
HTH,
Karen
Scott Moore wrote:
I'm creating tables for FOP that have a black background with white text in
the table header. The rest of
the proportional width function for table-columns, so it's
easier to specify them.
Hope that helps,
Karen Lease
Kaiser Christian (SV SC RS T33) wrote:
Hello,
a page that includes a (certain) table cannon be printed.
This table includes only images.
I've create this document in DocBook XML 5.0
Hi all,
I just committed some new table functionality to CVS. You can now do
things like
fo:table table-layout=fixed width=100%
fo:table-column column-width=proportional-column-width(2)
fo:table-column column-width=proportional-column-width(1)
.
You can mix absolute and proportional units
: Karen Lease [mailto:[EMAIL PROTECTED]]
Sent: Sunday, October 14, 2001 11:46 AM
To: [EMAIL PROTECTED]
Subject: Re: Table Headings
Hi Scott,
It sounds like you may be putting the background on the block containing
the text. Try putting it on the table-cell itself or even on the row.
HTH
Hi Pablo,
I'm not sure what you mean by row. If you mean a line of text, the
answer is no, at least not like that. You can try using a leader between
the text, replacing the leader-length value with what you want.
fo:blockFirst textfo:leader leader-pattern=space
leader-length=6cm/Second
I'm glad to see this will be getting done. I had thought of doing it,
but I'm trying not to get distracted and to devote what little time I
have (which is likely not to improve for the next two weeks
unfortunately) to the new FOP.
Since I'm going to be talking about XSL-FO at the XML 2001
to
anything.
You might also try setting all of the column-widths to one proportional
unit using column-width=proportional-column-width(1). That should make
sure that all your columns are included, whatever the width is. You must
still set the width on the table though.
Good luck,
Karen Lease
[EMAIL
Hi Kerion,
I agree it's better to have some output. Like my choir director says, we
can't know if you're singing the wrong note if we can't hear it :-)
I had some code written for this, but it's set up to return a
BreakPosition and it's incomplete.
I haven't gone back to the white-space
.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
Karen Lease
Sent: February 28, 2002 6:31 PM
To: [EMAIL PROTECTED]
Subject: Re: [REDESIGN] TextLayoutManager whitespace handling
[ SNIP ]
That's one thing. In your example, even supposing we
Deb,
Which version of tomcat are you using? Especially with Tomcat 3.x I've
seen lots of classloader problems. Can you find out which jars are being
used by tomcat (in its lib or maybe lib/ext directory)? Look out for
jaxp.jar or perhaps a version of xerces at that level which would be
pulling
Hi Matthew,
You're right, it really shoulldn't do this. However you can keep it from
doing it by putting the keep-together=always attribute on the
table-row containing the cell which is breaking. Keep-together doesn't
work yet for block, but at least in this case, it does for table-row.
Like
Hi,
I wrote a fairly detailed description of the Break Possibility idea and
put it in the design docs section, for anyone who's interested.
Could someone please tell me the procedure for getting the html version
of the design docs regenerated on the web site? Or does this just
magically happen?
addressing memory
concerns. We'll see.
In fact I am switching to FOP for the rest of the day, to start looking at
the image layout, so I'll be mixing stuff up a fair bit from now on.
Regards,
Arved
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
Karen
Thank you Jeremias. I've committed it.
Regards,
Karen
Jeremias Maerki wrote:
Hi there
Since Michael did the first cut at the logging stuff and Jörg has
already submitted something on JAXP, I made the best out of my day off
and happily hacked around in the xml-docs directory. I hope you
Excellent idea:
+1 for Peter, Joerg and also Jeremias
-Karen
Keiron Liddle wrote:
I propose that we offer Peter West and Joerg Pietschmann to become
committers.
Peter has of course shown lots of commitment of the last year+.
Joerg is helping a lot with user questions FAQ etc.
If they
Hi Keiron,
On the one hand, I'm happy to see new work in the LayoutManagers.
On the other hand, it turns out, I have been plugging (unfortunately
really slowly) away at the Break Possibility ideas I mentioned a while
back and just this very evening I had gotten the Line and Text
LayoutManagers
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
Karen Lease
Sent: April 27, 2002 12:20 PM
To: [EMAIL PROTECTED]
Subject: Re: line layout commit
[ SNIP ]
At any rate, I'm certainly not averse to having some more structured
kind of communication
Hi Foppers,
I've gone ahead and committed the major part of the Break Possibility
approach to layout managers which I have developped. It leaves Keiron's
new code intact (except for a couple of changes I needed to make to be
able to subclass his LineLayoutManager). It's also not activated; to do
Hi Keiron,
Here are a few comments on your new layoutmgr stuff (which is definitely
more advanced than mine in most ways) :
1. I can't figure out how/where you manage space-start, space-end,
border, padding, background etc (ie, any non-inherited properties) for
non leaf node inline FO, ie:
Karen Lease wrote:
Hi Keiron,
Here are a few comments on your new layoutmgr stuff (which is definitely
more advanced than mine in most ways) :
1. I can't figure out how/where you manage space-start, space-end,
border, padding, background etc (ie, any non-inherited properties) for
non
Peter,
Here's my point of view on where line-breaking (perhaps including
hyphenation) happens.
The end result of layout is a sequence of nested areas. However while
layout is happening, line-breaking logic has to pretend that it's only
working on a flat row of characters and other inline leaf
Not really. As a fairly interested party, I must admit that mentions of
throwing it out and starting over don't leave me totally indifferent,
but I've got little enough time as it is for FOP these days, and I'm
trying not to let myself be distracted.
In any case, we all know that it's never right
Arved,
I'm definitely in favor of deciding how we think things are supposed to
be laid out. Of course it would be nice if we were on the same
wavelength with the majority of FO users and implementors... but I'm not
too worried about that.
Besides the stuff we're talking about currently, we need
Hi Keiron,
I think this is a good start. I especially like the illustration which
covers all aspects of the problem.
I have some suggestions for the proposed text (see below).
-Karen
Keiron Liddle wrote:
Hi devs,
I have attached a picture of how I think this process should work (in
Foppeuses, Foppeurs,
I've added some new stuff to the development branch to show how the
BreakPoss strategy would handle nested inlines. It doesn't do anything
with blocks in inlines yet. For the moment, FOs are creating BP style
layout managers for Inline, Text and Line.
There's a new inline
Congratulations Keiron.
You've certainly earned this with your steady contributions to FOP.
Regards,
Karen
Arved Sandstrom wrote:
Hi, all
I am very pleased to announce that Keiron has been elected to membership in
the Apache Software Foundation, effective tomorrow (voting finished
Hi all,
I see this started a few days ago, but I just came back from a couple of
weeks of vacation (and a couple of months of being totally buried in
work), so before I go back to the office, I'll at least let you know I'm
still around and even reading the list now and then :-)
I also
Hi Keiron etc,
I'm really happy to see all this movement going on and folks from the
maintenance branch getting into the redesign to help you out. I'm
hoping to be able to start contributing again too, perhaps not right
away, but hopefully in September. There may even be some possibility of
Hi Jessica,
That's a good question. As far as I've seen there's nothing official in
the specification, so it's up to each implementation to handle this. I
believe it falls in the category of things which could be defined by the
user agent idea in FOP and then used by the line-breaking
:
-Original Message-
From: Karen Lease [mailto:[EMAIL PROTECTED]]
Sent: August 19, 2002 6:58 PM
To: [EMAIL PROTECTED]
Subject: Re: Tasks - layout
[ SNIP ]
With regard to the line-height calculations, is anybody in the group
interested in getting into the gory details of the baseline stuff
and
could report back to the group.
However, it seems clear that FOP will definitely need to enhance the
information it is managing about Fonts in order to provide the baseline
information needed to implement these aspects of the spec.
Regards,
Karen
Tony Graham wrote:
Karen Lease wrote at 20 Aug
Arved Sandstrom wrote:
-Original Message-
From: Peter B. West [mailto:[EMAIL PROTECTED]]
Sent: August 20, 2002 9:51 PM
To: [EMAIL PROTECTED]
Subject: Re: Style issues.
[ SNIP ]
The only encoding rule I'd realy like to have:
Don't mix underscores with camelCase.
Beside
Hi Keiron,
Keiron Liddle wrote:
snip/
The line height calculation and alignment is only very basic at the moment.
The idea is that the LineLM gets certain information to find the offset to
baseline and total line height and when the InlineLM add areas they use this
information to set the
Your explanation couldn't be clearer. I now understand why the
underscore doesn't bother me so much even though I'm not such a Heathen
as not to use Emacs:
1) I type on a french keyboard and I don't have to shift to get the
underscore character (only to get most every other useful character
1 - 100 of 107 matches
Mail list logo
