Re: [REDESIGN] Line layout manager discussion

Arved, I agree that there is no need to tie the rendering to any particular model, as long as the results are equivalent. The discussions that span this list and the Xslfo-proc-devel list testify that there are many approaches to process of layout. However, if I am reading this correctly,

RE: [REDESIGN] Line layout manager discussion

-Original Message- From: Peter B. West [mailto:[EMAIL PROTECTED]] Sent: May 5, 2002 12:55 AM To: [EMAIL PROTECTED] Subject: Re: [REDESIGN] Line layout manager discussion Arved, I agree that there is no need to tie the rendering to any particular model, as long as the results

Re: cvs commit: xml-fop/docs/xml-docs xml2pdf.xsl

Sorry for the delay - this got stuck in a moderator queue - and I missed it as it had the same size, down to the last byte, as a spam message I got on -all- asf accounts. Dw -- Dirk-Willem van Gulik On 5 May 2002 [EMAIL PROTECTED] wrote: jeremias02/05/05 05:17:42 Modified:docs

Re: Master reference for fo:page-sequence

Thanks. This is now fixed in CVS (Yeah, my first commit!). The two files were already updated for the redesign but not in the maintenance branch. On 03.05.2002 18:20:06 Buchtík, Michal wrote: There are docs/xml2pdf.xsl docs/xml-docs/xml2pdf.xsl in fop-0.20.2-maintain branch with

cvs commit: xml-fop STATUS

jeremias02/05/05 08:49:50 Modified:.Tag: fop-0_20_2-maintain STATUS Log: Updated committer list. Revision ChangesPath No revision No revision 1.47.2.2 +3 -0 xml-fop/STATUS Index: STATUS

cvs commit: xml-fop STATUS

jeremias02/05/05 08:52:35 Modified:.STATUS Log: Updated committer list. Revision ChangesPath 1.49 +8 -3 xml-fop/STATUS Index: STATUS === RCS file: /home/cvs/xml-fop/STATUS,v

Border properties

Hello, I tried to make something out of bug 684. Again, after reading the spec in depth, I'm nearly biting pieces off my keyboard. In the tables.fo examples, the left edge of the table content rectangle is the same as the edge of the reference area, and left border (should I use start edge

DO NOT REPLY [Bug 8815] New: - Irritating overlapping regions in examples

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8815. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

DO NOT REPLY [Bug 8816] New: - content for xsl-footnote-separator doesn't work

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8816. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

Bug report for Fop [2002/05/05]

+---+ | Bugzilla Bug ID | | +-+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned

DO NOT REPLY [Bug 1154] - nested lists more than 3 level depth

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1154. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

DO NOT REPLY [Bug 1261] - problem with rendering of external-graphic in Fop-18

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1261. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

DO NOT REPLY [Bug 1318] - problems with tables (column width and when used in the xsl-after-region)

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1318. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

DO NOT REPLY [Bug 1391] - Bug in border-top-style

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1391. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

DO NOT REPLY [Bug 1474] - fo:external-graphic rendered as block level object

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1474. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

DO NOT REPLY [Bug 1759] - table-omit-footer-at-break sometimes cause crash

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1759. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

RE: Border properties

Comments intermingled.Default reference orientation and lr-tb writing mode assumed. -Original Message- From: J.Pietschmann [mailto:[EMAIL PROTECTED]] Sent: May 5, 2002 1:34 PM To: fop dev Subject: Border properties Hello, I tried to make something out of bug 684. Again, after

Re: [REDESIGN] Line layout manager discussion

Arved, Again, I agree that, in the conceptual area tree described in the spec, blocks embedded in inline-area generating FOs in the fo tree (e.g., fo:inline and fo:basic-link), themselves embedded in a parent fo:block, do not bubble up to the same level as the parent fo:block. Going back to

RE: [REDESIGN] Line layout manager discussion

On Sat, 2002-05-04 at 18:07, Arved Sandstrom wrote: I couldn't tell from the SVG source what you prepared the file with. I would like to use SVG myself. There is no way I am going to handcode it, though (just as with FO). I actually wrote it by hand. I tried using an editor but gave up,