<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Quality &amp; Debugging on speedata Publisher</title>
    <link>/en/manual/quality/</link>
    <description>Recent content in Quality &amp; Debugging on speedata Publisher</description>
    <generator>Hugo</generator>
    <language>en</language>
    <atom:link href="/en/manual/quality/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Quality assurance and PDF comparison</title>
      <link>/en/manual/quality/qualityassurance/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/en/manual/quality/qualityassurance/</guid>
      <description>&lt;p&gt;To assure that new versions of the speedata Publisher produce the exact the same results as before, it has a built in functionality to check for unwanted changes of behavior.&lt;/p&gt;&#xA;&lt;p&gt;The idea is as follows: with a layout file and a “good” result (a reference PDF) the publisher can check whether the current version of the publisher gets the same result. For that one has to create a layout and data XML file, run the speedata Publisher and save the result under the name reference.pdf. When the publisher is invoked with sp compare &lt;directory&gt; it will re-create the document and compare, page by page, if the resulting PDF is visually the same as the previously created file reference.pdf.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Troubleshooting / Debugging</title>
      <link>/en/manual/quality/troubleshooting/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/en/manual/quality/troubleshooting/</guid>
      <description>&lt;p&gt;The output does not always work as it should. Sometimes objects are too wide, sometimes the wrong text format is used and sometimes the table does not look as it should. In order to prevent troubleshooting from becoming too difficult, the speedata Publisher provides various aids. For this there is the command &lt;Trace&gt;, which offers different switches. These are (by default):&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; class=&#34;chroma&#34;&gt;&lt;code class=&#34;language-xml&#34; data-lang=&#34;xml&#34;&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;&lt;span class=&#34;nt&#34;&gt;&amp;lt;Trace&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;    &lt;span class=&#34;na&#34;&gt;assignments=&lt;/span&gt;&lt;span class=&#34;s&#34;&gt;&amp;#34;no&amp;#34;&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;    &lt;span class=&#34;na&#34;&gt;objects=&lt;/span&gt;&lt;span class=&#34;s&#34;&gt;&amp;#34;no&amp;#34;&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;    &lt;span class=&#34;na&#34;&gt;verbose=&lt;/span&gt;&lt;span class=&#34;s&#34;&gt;&amp;#34;no&amp;#34;&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;    &lt;span class=&#34;na&#34;&gt;grid=&lt;/span&gt;&lt;span class=&#34;s&#34;&gt;&amp;#34;no&amp;#34;&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;    &lt;span class=&#34;na&#34;&gt;gridallocation=&lt;/span&gt;&lt;span class=&#34;s&#34;&gt;&amp;#34;no&amp;#34;&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;    &lt;span class=&#34;na&#34;&gt;hyphenation=&lt;/span&gt;&lt;span class=&#34;s&#34;&gt;&amp;#34;no&amp;#34;&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;    &lt;span class=&#34;na&#34;&gt;kerning=&lt;/span&gt;&lt;span class=&#34;s&#34;&gt;&amp;#34;no&amp;#34;&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;    &lt;span class=&#34;na&#34;&gt;textformat=&lt;/span&gt;&lt;span class=&#34;s&#34;&gt;&amp;#34;no&amp;#34;&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;    &lt;span class=&#34;nt&#34;&gt;/&amp;gt;&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;dl&gt;&#xA;&lt;dt&gt;&lt;code&gt;assignments&lt;/code&gt;&lt;/dt&gt;&#xA;&lt;dd&gt;Displays the value of the assignment (&lt;SetVariable&gt;) on the console.&lt;/dd&gt;&#xA;&lt;dt&gt;&lt;code&gt;objects&lt;/code&gt;&lt;/dt&gt;&#xA;&lt;dd&gt;Draws a line around individual objects.&lt;/dd&gt;&#xA;&lt;dt&gt;&lt;code&gt;verbose&lt;/code&gt;&lt;/dt&gt;&#xA;&lt;dd&gt;Increases the output on the console (log file).&lt;/dd&gt;&#xA;&lt;dt&gt;&lt;code&gt;grid&lt;/code&gt;&lt;/dt&gt;&#xA;&lt;dd&gt;Draws the grid. See section &lt;a href=&#34;/en/manual/basics/grid/&#34;&gt;Grid&lt;/a&gt;.&lt;/dd&gt;&#xA;&lt;dt&gt;&lt;code&gt;gridallocation&lt;/code&gt;&lt;/dt&gt;&#xA;&lt;dd&gt;Draws the grid allocation. See section &lt;a href=&#34;/en/manual/basics/grid/&#34;&gt;Grid&lt;/a&gt;.&lt;/dd&gt;&#xA;&lt;dt&gt;&lt;code&gt;hyphenation&lt;/code&gt;&lt;/dt&gt;&#xA;&lt;dd&gt;Marks the places where the words may be hyphenated.&lt;/dd&gt;&#xA;&lt;dt&gt;&lt;code&gt;kerning&lt;/code&gt;&lt;/dt&gt;&#xA;&lt;dd&gt;Mark the place where the font inserts a kerning (HarfBuzz mode).&lt;/dd&gt;&#xA;&lt;dt&gt;&lt;code&gt;text format&lt;/code&gt;&lt;/dt&gt;&#xA;&lt;dd&gt;Creates a tooltip above each line of text, showing the text format used. See the example in the Text Formats section.&lt;/dd&gt;&#xA;&lt;/dl&gt;&#xA;&lt;h2&gt;Messages&lt;span id=&#34;messages&#34; style=&#34;position:absolute;margin-top:-5rem;&#34;&gt;&lt;/span&gt;&#xA;    &lt;a href=&#34;#messages&#34; class=&#34;heading-anchor&#34; aria-hidden=&#34;true&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;Besides the possibilities provided by the command &lt;code&gt;&amp;lt;Trace&amp;gt;&lt;/code&gt;, there is also the possibility to output messages in the log file:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Performance Considerations</title>
      <link>/en/manual/quality/performance/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/en/manual/quality/performance/</guid>
      <description>&lt;p&gt;When processing large documents or documents with many formatting operations, performance can become an important consideration. This chapter describes various strategies to optimize the typesetting speed of the speedata Publisher.&lt;/p&gt;&#xA;&lt;h2&gt;HTML Parsing&lt;span id=&#34;html-parsing&#34; style=&#34;position:absolute;margin-top:-5rem;&#34;&gt;&lt;/span&gt;&#xA;    &lt;a href=&#34;#html-parsing&#34; class=&#34;heading-anchor&#34; aria-hidden=&#34;true&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;One of the most significant performance factors is HTML parsing in paragraphs. By default, the Publisher parses HTML tags like &lt;code&gt;&amp;lt;b&amp;gt;&lt;/code&gt;, &lt;code&gt;&amp;lt;i&amp;gt;&lt;/code&gt;, &lt;code&gt;&amp;lt;span&amp;gt;&lt;/code&gt;, etc. in all text content. This parsing happens for every paragraph and can be expensive, especially in documents with many small text blocks.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
