Working with speedata publisher is a pleasure and while doing another proof of concept a few questions came up.

The given document needs an permanent (on each page) header and footer outside the general page/content area. That was realized by defining a "Rand" and a smaller "Platzierungsbereich" while placing the header/footer content inside the Rand but outside the Platzierungsbereich.

  <Seitentyp name="Seite rechts" bedingung="sd:ungerade( sd:aktuelle-seite() )">
    <Rand links="2.5cm" rechts="2cm" oben="1.7cm" unten="1cm" />
    <Platzierungsbereich name="text">
        <Platzierungsrahmen breite="{ sd:anzahl-spalten() }" höhe="{ sd:anzahl-zeilen() - 2 }" zeile="2" spalte="1"/>
    </Platzierungsbereich> 
    <BeiSeitenAusgabe>
<!-- header -->
<ObjektAusgeben spalte="1" zeile="1">
            <Textblock breite="12">
              <Absatz schriftart="Kopfzeile" textformat="links"><Wert>Header</Wert></Absatz>
            </Textblock>
          </ObjektAusgeben>
...

In general text ist rendered using "Ausgabe" with target Platzierungsbereich "text" to take care of the header-area if content fits more than one page.

<Datensatz element="Text">
    <Ausgabe bereich="text">
      <Text>
        <Absatz>
            <FürAlle auswahl="*">
                <Wert auswahl="." />
            </FürAlle>
        </Absatz>
....

The reason why i create this issue: If i gonna place a table inside the document i cannot use "Ausgabe" but only "ObjektAusgeben" which doesn't respect the Platzierungsbereich "text" and overwrites the header-area on the second page if the table is longer than one page.

  <Datensatz element="Tab">
  <ObjektAusgeben spalte="1">
    <Tabelle border-collapse="collapse" breite="42" padding="1mm" zeilenabstand="0mm" spaltenabstand="0pt" dehnen="max">
...

Is there a solution for that? The only workaround (i actually see) is to do a first pdf-generation without header/footer and a second run with different configuration to place header/footer outside the pagecontent.

Thanks in advance and kind regards!

It would be quite helpful if the generated documentation could be viewed online. Or am I just blind in seeing the link?

The .protocol file should include the version number of the LuaTeX binary. It helps to debug edge cases (new features such as spot colors and overprint).

I changed one col of the textframe layout.xml example document to a width of 3 units

<Platzierungsbereich name="text">
  <Platzierungsrahmen breite="4" höhe="17" zeile="2" spalte="1"/>
  <Platzierungsrahmen breite="3" höhe="10" zeile="3" spalte="6"/>
  <Platzierungsrahmen breite="4" höhe="24" zeile="1" spalte="11"/>
</Platzierungsbereich>

The middle box is rendered with a 3 units wide however the text flows over 4 units...bug or feature?

Unconfirmed, but very likely :)

one has give 69,99mm instead of 70mm grid size (height?, probably both)

It seems that one can't mix TrueType and OpenType fonts on 64 bit Windows.

Hi Patrick,

I have just been searching for binary Linux releases of Publisher and I have realized two things:

• Binaries aren’t provided for 32bit architectures.
• Linux binaries are older than the Windows or Mac binaries.

Is there any reason, at least for the second issue.

Many thanks for your help,

Pablo

Hi Peter,

this is only a suggestion, but how about including the installation information in the documentation?

It might be extremely useful, since there are times when you don’t have internet access.

Many thanks for your help,

Pablo

Hyphenation patterns for ancient Greek are missing (to be found here).

Just in case you wonder, polytonic Greek is the way modern Greek was written until the monotonic ortography reform in 1982. Hyphenation rules for polytonic Greek and ancient Greek are different.

[Sorry, if the previous explanation was obvious to you.]

Many thanks for your help.

<Layout
  xmlns:sd="urn:speedata:2009/publisher/functions/en"
  xmlns="urn:speedata.de:2009/publisher/en">

  <DefineTextformat name="foo" margin-top="2mm"/>

  <Record element="data">
    <PlaceObject>
      <Table>
        <Tr>
          <Td>
            <Paragraph textformat="foo"/>
          </Td>
        </Tr>
      </Table>
    </PlaceObject>
  </Record>
 </Layout>

gives me:

!LuaTeX error: There should have been a lua <node> here, not an object with type nil!
 ==> Fatal error occurred, no output PDF file produced!

While creating some test-layouts i'm trying to format text bold with B-Tag. In my case it works only for static input and not for value taken from xml.

      <Textblock breite="20" schriftart="Deckblatt">
        <Absatz>
<!-- works -->
          <B><Wert>Dieser statische Text erscheint fett</Wert></B>
<!-- doesn't work -->
          <B><Wert auswahl="titel" /></B>
         <!-- text of "titel"-node will be displayed, but not in bold format -->
        </Absatz>
      </Textblock>

Is this behaviour a bug and is there a workaround?

Kind regards

btw: using version 2.0.0 on MacOSX

If you don't give a file name, the publisher will throw errors.

I'd be interested in some of your modules in a standalone form.
E.g. xpath.

Would you consider moving them to their own projects?

 .foo {padding-right:2mm;padding-left:2mm;valign:top;}

=>

Error: /Users/patrick/work/software/publisher/src/lua/css.lua:58: attempt to perform arithmetic on local 'rule_stop' (a nil value)
stack traceback:
    ...ick/work/software/publisher/src/lua/publisher/spinit.lua:39: in function 'call'
    ...ick/work/software/publisher/src/lua/publisher/spinit.lua:232: in function 'main_loop'
    ...ick/work/software/publisher/src/lua/publisher/spinit.lua:264: in main chunk
    [C]: in function 'require'
    [\directlua]:1: in main chunk

The following code produces a border that encloses the table, but not the contained text.
Any ideas how to create such a bounding box without placing the text in the table.

    <ObjektAusgeben spalte="1" zeile="43" vreferenz="bottom">
        <Rahmen linienstärke="0.5pt">
            <Textblock>
                <Absatz>
                  <Wert>Headline</Wert>
                </Absatz>
            </Textblock>
            <Tabelle breite="42" padding="1mm" zeilenabstand="0mm" spaltenabstand="0pt" dehnen="max">
                <Spalten>
                    <Spalte breite="7" />
                    <Spalte breite="35" />
                </Spalten> 
                    <Tr>
                        <Td><Absatz><Wert>Zelle A</Wert></Absatz></Td>
                        <Td><Absatz><Wert>Zelle B</Wert></Absatz></Td>
                    </Tr>
            </Tabelle>
        </Rahmen>
    </ObjektAusgeben>

When we use PlaceObject with an absolute position (row="3cm" column="5cm") the given lengths are from the top left corner of the page. These should be from the top left corner of the current area.

Hi Patrick,

when I tried to list fonts in Windows, I got the following output:

c:\Documents and Settings\user\Desktop>sp --xml list-fonts

Loading file sdini.lua ......eedata-publisher-windows-i386-1.6.8\sw\lua\sdini.lu
a:64: ...eedata-publisher-windows-i386-1.6.8\sw\lua\sdini.lua:48: attempt to ind
ex local 'attr' (a nil value)
Total run time: 16.1696885s
exit status 1
Total run time: 16.1696885ss

I don’t know whether this might be a bug.

Many thanks for your help,

Pablo

Suppose you have {sd:number-of-columns()} in an attribute of PositioningFrame, it must not be evaluated until the page is setup.

Some characters, such as à, are not present in the output. This is probably due to a behavior in the selene unicode library which doesn't look at complete utf-8 sequences, but only at single bytes. So C3A0 matchs %s. Adding anchors to the pattern fixes that problem.

It would be nice to say something like grid="6x9" instead of cell height / width.

Using the textframe example. I adjusted the SetzeRaser.breite from 1cm to 10cm (for evil reasons):

<Seitenformat breite="16cm" höhe="12cm"/>
<SetzeRaster breite="10cm" höhe="12pt"/>

<Seitentyp name="page" bedingung="true()">
  <Rand links="1cm" rechts="1cm" oben="1cm" unten="1cm"/>
  <Platzierungsbereich name="text">
    <Platzierungsrahmen breite="4" höhe="17" zeile="1" spalte="1"/>
    <Platzierungsrahmen breite="4" höhe="10" zeile="1" spalte="6"/>
    <Platzierungsrahmen breite="4" höhe="24" zeile="1" spalte="11"/>
  </Platzierungsbereich>
</Seitentyp>

<Datensatz element="data">
  <Ausgabe bereich="text">
     <Text>
     <Absatz>
       <Wert auswahl="string(.)"/>
     </Absatz>
    </Text>
  </Ausgabe>
</Datensatz>

Running sp results in an infinite loop showing

Page of type "page" created (3898)
Number of rows: 24, number of columns = 2

Shipout page 3898
Page of type "page" created (3899)
Number of rows: 24, number of columns = 2
Shipout page 3899
Page of type "page" created (3900)
Number of rows: 24, number of columns = 2
Shipout page 3900

on the console - sp never stops.

There seems to be a problem with the correct rendering of the examples.

<?xml version="1.0" encoding="UTF-8"?>
<Layout 
  xmlns="urn:speedata.de:2009/publisher/en" 
  xmlns:sd="urn:speedata:2009/publisher/functions/en">

  <DefineColor name="red" value="#f00"/>

  <Pageformat width="5cm" height="5cm"/>

  <Record element="data">
    <PlaceObject >
      <Frame backgroundcolor="red" framecolor="red">
        <Textblock>
          <Paragraph>
            <Value>Text text text text</Value>
          </Paragraph>
        </Textblock>
      </Frame>
    </PlaceObject>
  </Record>
</Layout>

should give a red box. Instead, its background is white.

Layout:

<Layout xmlns="urn:speedata.de:2009/publisher/en">
  <Record element="data">
    <Message select="'hello from data'"/>
  </Record>
</Layout>

<?xml version="1.0"?>
<!-- WTF, no comment allowed here? -->
<data>
    <titel>Hello world!</titel>
</data>

Breaks

Create an object with size 10x10 and mark allocated cells, they get yellow (OK). If the object is too wide, these cells are not marked as occupied.

Is there any documentation of Stylesheet definitions supported by elements using the "class" attribute like "Absatz"? Maybe i missed something in the reference/documentation section.
(Even a shortcode to the related source-code in repo may help.)

Best regards
M. Deutschmann

Using sprun --docto build the documentation brings up only this result: The file /Users/daniel/Repos/publisher/build/handbuch_publisher/index.html does not exist.

Patrick,

[Excuse me for my stupid (i.e. too basic) question.]

How could I use document merging with Publisher?

I would like to use Publisher for document merging at work and I wonder whether this would be possible without external tools.

Many thanks for your help,

Pablo

Is it possible to create pdf-internal hyperlinks with A-Tag? How to place an anchor and how to format the href-attribute of the A-Tag?

Thanks in advance and kind regards!

<?xml version="1.0"?>
<Layout
  xmlns:sd="urn:speedata:2009/publisher/functions/en"
  xmlns="urn:speedata.de:2009/publisher/en">

  <Record element="data">
    <PlaceObject>
      <Barcode select="'123456789012'" type="EAN13" width="4cm" showtext="yes"/>
    </PlaceObject>
  </Record>
</Layout>

gives this error:

!LuaTeX error: There should have been a lua <node> here, not an object with type nil!
 ==> Fatal error occurred, no output PDF file produced!
Total run time: 311.732ms
exit status 70

After reding this article, I wonder whether it would be possible to format XML sources with only CSS.

It seems that O’Reilly is moving their book publishing from DocBook to HTMLBook.

Maybe it would be interesting to you.

I can generate the pdf file in the examples-de/planeten folder correctly but the english version doen't generate any file. The log file says that there is no error.

Is there a way to retrieve name of the current node like xpath function "name()"?

Error: Function "name" with prefix "" unknown

sp --jobname foo

is supposed to generate foo.pdf? The result PDF is always needs publisher.pdf (tested with the unstable release as of today).

When filling table cells from XPath returns the following error:

/Users/daniel/Repos/publisher/src/lua/xpath.lua:319: bad argument #1 to 'ipairs' (table expected, got nil)stack traceback:
    .../daniel/Repos/publisher/src/lua/publisher/spinit.lua:51: in function 'call'
    .../daniel/Repos/publisher/src/lua/publisher/spinit.lua:250: in function 'main_loop'

            <Tabelle breite="1">
                <Tr>
                    <Td align="center"><Absatz><Bild breite="1" datei="loginpriintsuite.png" /></Absatz></Td>
                </Tr>
                <Tr>
                    <Td align="center"><Absatz><Wert auswahl="ArtikelNr" /></Absatz></Td>
                </Tr>
                <Tr>
                    <Td align="center"><Absatz><Wert auswahl="Bezeichnung" /></Absatz></Td>
                </Tr>
                <Tr>
                    <Td><Absatz><Wert auswahl="UPE" /></Absatz></Td>
                </Tr>
            </Tabelle>

XSLT is too slow for that

"$foo = 'bar'" seems to work, while "$foo='bar'" evaluates to nil. Strange. The space seems to be significant.

I am playing with the publisher example - in particular with issueshape/layout.xml. I changed the "breite" value to 8. My expectation is that the image size decrease and all text would continue to flow around.

  <Sonst>
    <ObjektAusgeben spalte="10" zeile="10" belegen="ja">
      <Bild datei="taschenuhr.pdf" breite="8"/>
    </ObjektAusgeben>
  </Sonst>

However there is some text into the image...bug or feature?

The next release should have some basic CSS documentation

Todo: example

<Layout
  xmlns:sd="urn:speedata:2009/publisher/functions/en"
  xmlns="urn:speedata.de:2009/publisher/en">

  <Record element="data">
    <PlaceObject>
      <Table>
        <Columns>
          <Column width="1*"/>
          <Column width="1*"/>
          <Column width="32.5mm"/>
          <Column width="32.5mm"/>
          <Column width="32.5mm"/>
          <Column width="32.5mm"/>
        </Columns>
        <Tr>
          <Td><Paragraph><Value>Alongword (111.111)</Value></Paragraph></Td>
          <Td><Paragraph><Value>without text</Value></Paragraph></Td>
          <Td colspan="4"><Paragraph><Value>12345</Value></Paragraph></Td>
        </Tr>
      </Table>
    </PlaceObject>
  </Record>
</Layout>

yields

Version: 2.1.32-51d71d60

/tmp/test/publisher/bin/sprun:55: module 'optionparser' not found:
no field package.preload['optionparser']
no file '/opt/texlive2011/bin/universal-darwin/src/lua/optionparser.lua'
no file '/opt/texlive2011/bin/universal-darwin/lib/optionparser.lua'
no file '/opt/texlive2011/bin/universal-darwin/src/lua/common/optionparser.lua'
no file './optionparser.so'
no file '/usr/local/lib/lua/5.1/optionparser.so'
no file '/usr/local/lib/lua/5.1/loadall.so'

The problem comes, when TeXlive is in the PATH.

See example runningsum. The header "first page" is not recognized.

Misaligned superscript in:

<?xml version="1.0" encoding="UTF-8"?>
<Layout 
  xmlns="urn:speedata.de:2009/publisher/en" 
  xmlns:sd="urn:speedata:2009/publisher/functions/en">
  <Options trace="no"/>

  <Record element="data">
    <PlaceObject>
      <Textblock>
        <Paragraph>
          <Value>99</Value><Sup><Value>9</Value></Sup>
        </Paragraph>
      </Textblock>
    </PlaceObject>
  </Record>
</Layout>

Following the guidelines for documentation building process, only this error message shows up:

/Users/daniel/Repos/publisher/bin/sdcontrol:13: module 'optionparser' not found:
    no field package.preload['optionparser']
    no file '/usr/local/texlive/2011/bin/x86_64-darwin/src/lua/optionparser.lua'
    no file '/usr/local/texlive/2011/bin/x86_64-darwin/lib/optionparser.lua'
    no file '/usr/local/texlive/2011/bin/x86_64-darwin/src/lua/common/optionparser.lua'
    no file './optionparser.so'
    no file '/usr/local/lib/lua/5.1/optionparser.so'
    no file '/usr/local/lib/lua/5.1/loadall.so'

Hi Patrick,

I have tried to list the system fonts using the instructions and I got the following result:

c:\Documents and Settings\USUARIO\Escritorio>sp --xml list-fonts
Script file C:\Documents not found
Total run time: 187.5ms
exit status 1
Total run time: 187.5ms

I don’t know whether I’m doing something wrong, but it seems that sp has problems with spaces in directory names.

Just in case it helps,

Pablo

I’m not a coder, and I might be wrong.

I have already luatex installed on my system twice (it comes with TeX Live 2013 and with ConTeXt Standalone).

Wouldn’t it be better to rename the luatex binary to luatex_sp, luatex-sp or something similar to avoid file name collisions.

Many thanks for your help,

Pablo

The new communication feature breaks multiple runs.

Images are not closed, so after a while the system raises a too many open files error.

Todo: example