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=4562>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4562 XSL 1.0 uses "master-reference" now, not "master-name" Summary: XSL 1.0 uses "master-reference" now, not "master-name" Product: Fop Version: all Platform: All OS/Version: All Status: NEW Severity: Major Priority: Other Component: page-master/layout AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] The XSL 1.0 Recommendation uses the "master-reference" property on the elements single-page-master-reference, repeatable-page-master-reference, conditional-page-master-reference and (notably) page-sequence. The standard changed this from "master-name" about two revisions ago. "master-name" is still used, but only to name page masters, not to reference them. This had me really confused, because I was writing FO by following the standard and FOP was failing to render them. This change means that all the examples that come with FOP are now technically incorrect, and it means that FOP itself cannot render even the simplest standard FO examples. The diagnostic output says that "master-reference" is being ignored (but it doesn't mention that you should use "master-name" instead, this is what confused me). And later it crashes with the all too familiar "ERROR: null". The fix appears to be very simple for someone familiar with the code, which would not be me. I would suggest accepting either property, with a warning when the old one is used. cheers, -- Jamie Lokier --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]