<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1400" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face="Courier New" size=2>Just a note to mention that if you remove
the id attribute, then any bookmark or cross reference that points to that
element will no longer work in the PDF.</FONT></DIV>
<DIV><FONT face="Courier New" size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Bob Stayton<BR>Sagehill Enterprises<BR>DocBook
Consulting<BR><A
href="mailto:bobs@sagehill.net">bobs@sagehill.net</A></FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<BLOCKQUOTE
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV
style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B>
<A title=Douglas_Morrison@contractor.amat.com
href="mailto:Douglas_Morrison@contractor.amat.com">Douglas_Morrison@contractor.amat.com</A>
</DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A title=xep-support@renderx.com
href="mailto:xep-support@renderx.com">xep-support@renderx.com</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Tuesday, June 15, 2004 8:46
AM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> Re: [xep-support] A3 pages and
Landscape Pages</DIV>
<DIV><BR></DIV><BR><FONT face=sans-serif size=2>Ken,</FONT> <BR><BR><FONT
face=sans-serif size=2>Thanks very much for that reply - it has helped to
clarify the issues involved.</FONT> <BR><BR><FONT face=sans-serif size=2>I
agree that there is a problem knowing what to do with various attributes on
the blocks. In the case of Docbook xsl (from Norman Walsh) the only attribute
on the block element is the id attribute. I am not quite sure what use is made
of it, but for my application I don't think it would matter of the block was
removed. In the xsl exported by Arbortext Styler I am not sure what the full
range of attributes could be, but none that I have seen are essential for my
purposes (as far as I know).</FONT> <BR><BR><FONT face=sans-serif size=2>If I
remove the blocks, the output form the xslt will be something like:</FONT>
<BR><BR><FONT face=sans-serif size=2><fo:page-sequence</FONT> <BR><FONT
face=sans-serif size=2> <fo:flow</FONT> <BR><FONT
face=sans-serif size=2> A</FONT> <BR><FONT
face=sans-serif size=2> <fo:page-sequence</FONT>
<BR><FONT face=sans-serif size=2>
<fo:flow</FONT> <BR><FONT face=sans-serif size=2>
B</FONT> <BR><FONT face=sans-serif
size=2> </fo:flow</FONT> <BR><FONT
face=sans-serif size=2>
</fo:page-sequence</FONT> <BR><FONT face=sans-serif size=2>
C</FONT> <BR><FONT face=sans-serif size=2>
</fo:flow</FONT> <BR><FONT face=sans-serif
size=2></fo:page-sequence</FONT> <BR><BR><FONT face=sans-serif size=2>What
I was suggesting was that the W3 standard ought to allow such nesting. It
would then be up to XEP to extract three parts to make three sibling page
concepts. So it would then not be an xslt problem, but the far preferable
"someone else's problem"!</FONT> <BR><BR><FONT face=sans-serif size=2>However
there would still be issues with some page-sequence attributes (eg
force-page-count) that would need to be addressed. XEP could also handle
nesting within fo:blocks provided the interpretation of attributes were
consistent with user requirements - which may or may not be a problem.</FONT>
<BR><BR><FONT face=sans-serif size=2>To be really general, the transitions to
different page geometries should not have to be symmetrically placed in the
source xml. Modifying your example, the source could be</FONT> <BR><BR><FONT
size=2><TT> <block<BR> A<BR>
<block<BR> B<BR>
<block<BR> C<BR>
<?switchpage master-reference="A3Landscape"/><BR>
<block<BR>
X<BR> </block<BR>
<block<BR>
Y<BR> </block<BR>
<block<BR>
Z<BR> </block<BR>
D<BR> </block<BR>
E<BR> </block<BR>
<?switchpage master-reference="A4Portrait"/><BR>
F<BR> </block<BR></TT></FONT><BR><FONT face=sans-serif
size=2>Furthermore, the actual transition could even be mid-block. An
attribute of the switchpage pi could say "carry on writing to the current
page, but when that is full, change to the new pageset and continue writing
into that". I anticipate that there could be implementation problems, and
there may be other strong objections.</FONT> <BR><BR><FONT face=sans-serif
size=2>As it may be some time before W3 and XEP allow such nesting, I think my
best way forward may well be to remove the unecessary blocks and emit a
psmi:page-sequence and use your ingenious solution. The output from the
first xslt pass would then be something like:</FONT> <BR><BR><FONT
face=sans-serif size=2><fo:page-sequence</FONT> <BR><FONT face=sans-serif
size=2> <fo:flow</FONT> <BR><FONT face=sans-serif
size=2> A</FONT> <BR><FONT face=sans-serif
size=2> <psmi:page-sequence
master-reference="A3Landscape"/></FONT> <BR><FONT face=sans-serif
size=2> B</FONT> <BR><FONT face=sans-serif
size=2> <psmi:page-sequence
master-reference="A4Portrait"/></FONT> <BR><FONT face=sans-serif
size=2> C</FONT> <BR><FONT face=sans-serif
size=2> </fo:flow</FONT> <BR><FONT face=sans-serif
size=2></fo:page-sequence</FONT> <BR><BR><FONT face=sans-serif size=2>And
then the above would be transformed using your wonderful psmi.xsl.</FONT>
<BR><BR><FONT face=sans-serif size=2>Regards, Doug x2571</FONT>
<BR><BR><FONT face=sans-serif size=2>The content of this message is Applied
Materials Confidential. If you are not the intended recipient and have
received this message in error, any use or distribution is prohibited.
Please notify me immediately by reply e-mail and delete this message
from your computer system. Thank you.</FONT> <BR><BR><BR><BR>
<TABLE width="100%" border=1>
<TBODY>
<TR vAlign=top>
<TD><BR><BR><BR><FONT face=sans-serif size=1><B>"G. Ken Holman"
<gkholman@CraneSoftwrights.com></B></FONT> <BR><FONT
face=sans-serif size=1>Sent by: owner-xep-support@renderx.com</FONT>
<BR><FONT face=sans-serif size=1>11/06/2004 17:11</FONT> <BR><FONT
face=sans-serif size=1>Please respond to xep-support</FONT>
<TD><FONT face=Arial size=1> </FONT><BR><FONT
face=sans-serif size=1> To:
xep-support@renderx.com</FONT> <BR><FONT face=sans-serif
size=1> cc:
</FONT> <BR><FONT face=sans-serif size=1>
Subject: Re: [xep-support] A3 pages
and Landscape Pages</FONT> <BR><FONT face=sans-serif size=2>
</FONT></TR></TBODY></TABLE><BR><BR><BR><FONT size=2><TT>At 2004-06-11
15:15 +0100, Douglas_Morrison@contractor.amat.com wrote:<BR>>Thanks very
much for that suggestion. One problem for me is the <BR>>requirement to
insert the psmi marker as a direct child of fo:flow. The <BR>>xsl I am
using could put in several nested fo:blocks before reaching the
<BR>>element that requires the change in page geometry. I'm not sure how to
get <BR>>round that.<BR>><BR>>It seems to me the best solution would
be to allow nested pagesets and <BR>>process them accordingly. Why
not?<BR><BR>Consider the situation where one has nested blocks and the need
for a page:<BR><BR> <block<BR> A<BR>
<block<BR> B<BR>
<block<BR> C<BR>
<page<BR>
<block<BR> X<BR>
</block<BR>
<block<BR>
Y<BR> </block<BR>
<block<BR>
Z<BR>
</block<BR> </page<BR>
D<BR>
</block<BR> E<BR>
</block<BR> F<BR> </block<BR><BR>In the object
hierarchy, "D", "E" and "F" have the same properties as "A", <BR>"B", and "C".
Would that imply the same kinds of blocks in the <BR>newly-created page
sequence? If so, what happens to those properties of <BR>the blocks that
apply at the start of the block (initial property set, <BR>space-before,
etc.)? Padding? backgrounds?<BR><BR>And if that were all determined,
what would the XSLT be to extract the <BR>three parts above into three sibling
page concepts ... the recursive-call <BR>requirements are, I believe, doable
but very awkward and not easily <BR>generalizable.<BR><BR>I've assessed that
"process them accordingly" is untenable and messy in the <BR>general case ....
I'd be interested to hear proposals for general solutions <BR>to such
situations.<BR><BR>..................... Ken<BR><BR>--<BR>Public training 3
days XSLT & 2 days XSL-FO: Phoenix,AZ 2004-08-23<BR>World-wide on-site
corporate, govt. & user group XML/XSL training.<BR>G. Ken Holman
mailto:gkholman@CraneSoftwrights.com<BR>Crane Softwrights Ltd.
http://www.CraneSoftwrights.com/f/<BR>Box 266, Kars,
Ontario CANADA K0A-2E0 +1(613)489-0999 (F:-0995)<BR>Male Breast
Cancer Awareness http://www.CraneSoftwrights.com/f/bc<BR>Legal business
disclaimers:
http://www.CraneSoftwrights.com/legal<BR><BR>-------------------<BR>(*)
To unsubscribe, send a message with words 'unsubscribe xep-support'<BR>in the
body of the message to majordomo@renderx.com from the address<BR>you are
subscribed from.<BR>(*) By using the Service, you expressly agree to these
Terms of Service
http://www.renderx.com/tos.html<BR></TT></FONT><BR></BLOCKQUOTE></BODY></HTML>