I cannot reproduce that with the latest Trunk. However, I found another bug that causes a similar error for which I'll submit a patch shortly. I had a document-v11 document with a "dl" as child of a "ul". The stylesheet didn't foresee that.
Anyway, the error messages that are currently displayed are follow-up errors, not the original validation errors. Why that happens here in Forrest is unclear to me. Normally this doesn't. I probably have to dig deeper at some point. On 04.03.2008 11:34:27 Gav.... wrote: > Hi All, > > Using Trunk and a fresh 'forrest seed-basic' , when I do 'forrest run' I get > > Request URI > > index.pdf > > cause > > Error(Unknown location): For fo:simple-page-master, fo:region-body must be > declared before fo:region-before. > > when viewing its PDF. > > Console output says :- > > WARN - Mismatch: simple-page-master (http://www.w3.org/1999/XSL/Format) vs. > layo > ut-master-set (http://www.w3.org/1999/XSL/Format) > WARN - Mismatch: simple-page-master (http://www.w3.org/1999/XSL/Format) vs. > root > (http://www.w3.org/1999/XSL/Format) > > > I will try again with another new seed and see what happens. > > Gav... > > > > -----Original Message----- > > From: Jeremias Maerki (JIRA) [mailto:[EMAIL PROTECTED] > > Sent: Tuesday, 4 March 2008 6:40 PM > > To: dev@forrest.apache.org > > Subject: [jira] Closed: (FOR-1072) [PATCH] Bugfixes and improvements for > > PDF output plugin > > > > > > [ https://issues.apache.org/jira/browse/FOR- > > 1072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] > > > > Jeremias Maerki closed FOR-1072. > > -------------------------------- > > > > Resolution: Fixed > > > > I think that's it for the moment. > > > > > [PATCH] Bugfixes and improvements for PDF output plugin > > > ------------------------------------------------------- > > > > > > Key: FOR-1072 > > > URL: https://issues.apache.org/jira/browse/FOR-1072 > > > Project: Forrest > > > Issue Type: Improvement > > > Components: Plugin: output.pdf > > > Affects Versions: 0.9-dev > > > Reporter: Jeremias Maerki > > > Fix For: 0.9-dev > > > > > > Attachments: forrest-pdf-touchup.patch, forrest-pdf- > > touchup2.patch, forrest-pdf-touchup3.patch > > > > > > > > > I've been playing with Forrest Trunk to get the FOP website to work. I > > found a number of problems which I've fixed with the attached patch. The > > changes in detail: > > > - PDFs generated from an FAQ page inserted the section number (1.1, 1.2 > > etc.) twice in front of the section title. I've just filtered it now. It > > may not be the best way to fix this. > > > - Added a bookmark entry for the table of contents if it is enabled. > > > - Added keep-with-next.within-column="always" for all section titles, > > header elements of note/warning/fixme boxes and table captions. The new > > FOP supports keeps so you should use them. Otherwise, page break decision > > can be really ugly. > > > - Added keep-with-previous.within-column="always" for note/warning/fixme > > boxes so the don't land on a new page as first elements. This preserves > > the context. > > > - table rows with th elements are now placed in the fo:table-header, so > > the headers are repeated on each page the table spans. > > > - Used proportional-column-width(1) instead of a fixed width calculation > > for the column widths which automatically makes use of the whole page > > width regardless of the page margin settings. > > > - Fixed placement of page number and document title depending on > > "double-sided" setting. --> Page number to the "outside" and document > > title to the "inside". > > > - Filtered out link elements with no href (which are created by html-to- > > document.xsl for "<a name=..."). Forrest 0.7 didn't generate them as links > > at all but trunk does. Maybe that's wrong in the first place. > > > I'd appreciate a quick turn-around with this patch (if possible) as this > > would allow us to switch to Forrest Trunk for the FOP 0.95 release (we > > want to eat our own dogfood). Without this patch, our compliance PDF page > > fails due to the "<link name=" in it. Thanks a lot! > > > > -- > > This message is automatically generated by JIRA. > > - > > You can reply to this email to add a comment to the issue online. > > > > > > > > -- > > Internal Virus Database is out-of-date. > > Checked by AVG Free Edition. > > Version: 7.5.516 / Virus Database: 269.20.9 - Release Date: 2/20/2008 > > 12:00 AM Jeremias Maerki