Jeremias Maerki a écrit :
If anyone has any requirements for XSL-FO 2.0 which I should bring up at
the workshop in Heidelberg next week, please let me know. Deadline
2006-10-16 so I have time to prepare.
Jörg's comments just reminded me of something I think is missing in the
current spec:
Jeremias Maerki wrote:
If anyone has any requirements for XSL-FO 2.0 which I should bring up at
the workshop in Heidelberg next week, please let me know. Deadline
2006-10-16 so I have time to prepare.
Luca, are you going, too? How do you travel?
Yes, I'm going.
I think I'll travel by train,
On Mon, Oct 09, 2006 at 11:45:08PM +0200, J.Pietschmann wrote:
Jeremias Maerki wrote:
If anyone has any requirements for XSL-FO 2.0 which I should bring up at
the workshop in Heidelberg next week, please let me know.
More radical thoughts:
- Deprecate mixing inlines and blocks :-P
Block
On Tue, 2006-10-10 at 12:42 +0200, Simon Pepping wrote:
On Mon, Oct 09, 2006 at 11:45:08PM +0200, J.Pietschmann wrote:
Jeremias Maerki wrote:
If anyone has any requirements for XSL-FO 2.0 which I should bring up at
the workshop in Heidelberg next week, please let me know.
More radical
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=40465.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=5335.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=5335.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=40676.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
On Oct 10, 2006, at 07:21, Manuel Mall wrote:
snip /
Jeremias already responded to you and my comments go in the same
direction. Firstly, its great that you want to look at this aspect. I
did investigate support for UAX#14 Unicode compliant line breaking
over
a year ago.
FWIW: a few months
I finished(?) working on the somewhat modified items (1), (2) and (4) of
Jerememias' list.
I plan to clean up to code a bit and then try to submit a patch (there
should be a first time for everything I guess :))
Here is an overview of what has been done - probably belongs in the patch as
well,
Simon Pepping wrote:
Block content in inline content is the natural organization of
displayed formulas and tables. Demanding that FO generating
stylesheets separate them is moving the burden back to them. I am not
in favour of that.
Ah, I start seeing the point. You might have add images as
Andreas L Delmelle wrote:
I was thinking to use an approach analogous to the current refinement
white-space handling: one BidiProcessor stored in the FOEventHandler.
This may have inindented consequences: some output formats expect the
ultimate user client to do BIDI formatting, which means
How do you go about generating the Javadoc FOP documentation?
--
View this message in context:
http://www.nabble.com/Generating-Javadoc-FOP-documentation-tf2419876.html#a6746559
Sent from the FOP - Dev mailing list archive at Nabble.com.
Hi Nicol:
ant -projecthelp
This will give you help about the commands.
So for javadoc do ant javadocs.
HTH,
Patrick
Nicol Bolas wrote:
How do you go about generating the Javadoc FOP documentation?
14 matches
Mail list logo
