Pagetypes and issue 608

[Cicorione]

Hi Patrick,

I returning to this argument because perhaps I misunderstood it (most likely).

#608

I have a pagetype for the index that is false() unless it is called. This master takes advantage of the inner and outer margins.

The peculiarity of this master pages is to have positioningarea and positioningframe to flush the auto-populated table.

When I invoke it through the layout.xml it is only applied one time, even though I asked to use the same pagetype at the begin and at the end of the forall loop:

<!-- INDEX SECTION -->
  <!-- [index#4] -->
  <Record element="index">
    <ClearPage pagetype="idx" matter="index" />
    <PlaceObject area="idxcols">
      <Table balance="no" fontfamily="index">
        <ForAll select="idxsection">
          <Tr break-below="no" top-distance="10pt">
            <Td colspan="2" background-color="mpColorA" padding-left="1mm">
              <Paragraph>
                <B>
                  <Value select="@name" />
                </B>
              </Paragraph>
            </Td>
          </Tr>
          <ForAll select="indexentry">
            <Tr>
              <Td>
                <Paragraph>
                  <NoBreak reduce="fontfit">
                    <Value select="concat(@name, '  ')" />
                  </NoBreak>
                </Paragraph>
              </Td>
              <Td align="right">
                <Paragraph>
                  <Value select="@page" />
                </Paragraph>
              </Td>
            </Tr>
         <entry level="info" msg="Create page" type="right" pagenumber="127"></entry> </ForAll>
        </ForAll>
      </Table>
    </PlaceObject>
    <ClearPage pagetype="idx" />
  </Record>

However it is not applying the same pagetype to the following page:

<entry level="debug" msg="Call command" name="ProcessNode" line="108"></entry>
<entry level="debug" msg="Process node" node="index" mode="" pos="1"></entry>
<entry level="debug" msg="Call command" name="ClearPage" line="988"></entry>
<entry level="debug" msg="Call command" name="PlaceObject" line="989"></entry>
<entry level="info" msg="Create page" type="idx" pagenumber="126"></entry>
<!--   A LOT OF REPEATED LINES -->
<entry level="info" msg="Create page" type="right" pagenumber="127"></entry>

The next page is the right master although the matter is honored and the page numeration is correct.

What I am doing wrong? 🤷‍♂️

Thanks... 🙏

[pgundlach]

I hope I understand this correctly: the page type "idx" is created once, then (I assume) some items appear on the page and the next page is not the "idx" type, right?

Page types are detected automatically by the test="..." attribute, unless required explicitly by ClearPage. Therefore the second page in the index is detected by regular means, not by name.

I think what you need is something like this:

<Layout xmlns="urn:speedata.de:2009/publisher/en"
	xmlns:sd="urn:speedata:2009/publisher/functions/en"
	xmlns:sf="justanamespace"
>
	<Function name="sf:printsomething">
		<Param name="count" />
		<Loop select="$count">
			<PlaceObject>
				<Textblock>
					<Paragraph>
						<Value>Hello</Value>
					</Paragraph>
				</Textblock>
			</PlaceObject>
		</Loop>
	</Function>

	<Pagetype name="idx" test="$inIndex">
		<AtPageCreation>
			<PlaceObject>
				<Textblock>
					<Paragraph>
						<Value>page type idx</Value>
					</Paragraph>
				</Textblock>
			</PlaceObject>
		</AtPageCreation>
	</Pagetype>

	<SetVariable variable="inIndex" select="false()" />
	<Record element="data">
		<Value select="sf:printsomething(2)" />
		<SetVariable variable="inIndex" select="true()" />
		<ClearPage />
		<Value select="sf:printsomething(30)" />
		<SetVariable variable="inIndex" select="false()" />
		<ClearPage />
		<Value select="sf:printsomething(2)" />
	</Record>
</Layout>

<Pagetype name="idx" test="$inIndex"> is the selector for the index page type, you need to set inIndex to false() before any page selection starts. Then just switch inIndex to true() if you want to place the index and set it to false after that.

[Cicorione]

Thank you Patrick,

this was perhaps my last blocking issue... 🙏

However this is a little bit counter-intuitive for the way my brain is wired, as a matter of fact I mistakenly thought and used clearpage as a method to force a master overriding, in the same way I would have done with Indesign or Scribus...

I hope to have gotten right... 🙏

[pgundlach]

There are explicit and implicit ClearPage commands. You can set the master for the explicit ClearPage commands, but not for the implicit ones. The second ones are the automatically chosen Clear page if the page is too full.

There could be a "From now on use the following ClearPage master", but there is none. You need to do this with variables.

(Could be a feature... thinking mode)

[Cicorione]

It worked and I got the point, the only downside I see — assuming I what I am going to say is correct — it depends on their position on the layout.

Assuming these are your "masters:"

A: true() [main]
B: false()
C: false()

You can change (through variables) their status:

A:true()
B:false()
C:true() [now overrides A]

But if you need B you must close C, cause it won't work:

A:true()
B:true() [now overrides A]
C:true() [overrides A & B]

The correct way would be:

A:true()
B:false()
C:true() [overrides A]

It is not wrong in anyway, it only requires to keep track of the variables to close and open the right "knobs" when it is needed. Am I right?