<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>printing css</title>
	<atom:link href="http://printingcss.com/?feed=rss2" rel="self" type="application/rss+xml" />
	<link>http://printingcss.com</link>
	<description>turning HTML and CSS into PDF by way of Prince</description>
	<lastBuildDate>Mon, 24 Oct 2011 19:59:57 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>Pointing to figures in JavaScript</title>
		<link>http://printingcss.com/?p=73</link>
		<comments>http://printingcss.com/?p=73#comments</comments>
		<pubDate>Mon, 24 Oct 2011 19:59:57 +0000</pubDate>
		<dc:creator>howcome</dc:creator>
				<category><![CDATA[Sample documents]]></category>

		<guid isPermaLink="false">http://printingcss.com/?p=73</guid>
		<description><![CDATA[In books, it is common to refer to figures &#8220;on page x&#8221;, or &#8220;on the next page&#8221;. In Prince 7, authors can refer to figures (and other elements) by way of page numbers, but there is no way to detect when a figure is on the next or previous page. Prince 8 introduces a way [...]]]></description>
			<content:encoded><![CDATA[<p>In books, it is common to refer to figures &#8220;on page x&#8221;, or &#8220;on the next page&#8221;. In Prince 7, authors can refer to figures (and other elements) by way of page numbers, but there is no way to detect when a figure is on the next or previous page. Prince 8 introduces a way to do this: The text can be automatically changed based on where the figure ends up. This is accomplished through a simple JavaScript. Here is the <a href="http://www.princexml.com/howcome/2011/here/index.html">HTML document</a> and here is the <a href="http://www.princexml.com/howcome/2011/here/index.pdf">resulting PDF file</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://printingcss.com/?feed=rss2&amp;p=73</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Creating an index in JavaScript</title>
		<link>http://printingcss.com/?p=64</link>
		<comments>http://printingcss.com/?p=64#comments</comments>
		<pubDate>Mon, 21 Mar 2011 22:21:16 +0000</pubDate>
		<dc:creator>howcome</dc:creator>
				<category><![CDATA[Sample documents]]></category>

		<guid isPermaLink="false">http://printingcss.com/?p=64</guid>
		<description><![CDATA[We know that a table of contents can be created in Javascript, but what about an index? Can JavaScript be used to automatically generate an index, like those found at the back of books? The answer is yes. To a point. In this example, some terms in the document have been tagged for inclusion in [...]]]></description>
			<content:encoded><![CDATA[<p>We know that a table of contents can be <a href="http://printingcss.com/?p=61">created in Javascript</a>, but what about an index? Can JavaScript be used to automatically generate an index, like those found at the back of books? The answer is yes. To a point. In <a href="http://www.princexml.com/howcome/2011/musick/musick.html">this example</a>, some terms in the document have been tagged for inclusion in the index. The script attached to the page looks for these tags (span elements, actually), and creates an alphabetized list of pointers to them. Thereafter, Prince adds page numbers by way of CSS. The <a href="http://www.princexml.com/howcome/2011/musick/musick.pdf">resulting PDF file</a> has an index at the end. Some things are missing, though: commas between page numbers and the collapsing of equal page numbers into one link. The latter is tricky to achieve as the script runs before page numbers are generated.</p>
]]></content:encoded>
			<wfw:commentRss>http://printingcss.com/?feed=rss2&amp;p=64</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Welcome, JavaScript</title>
		<link>http://printingcss.com/?p=61</link>
		<comments>http://printingcss.com/?p=61#comments</comments>
		<pubDate>Sat, 19 Mar 2011 13:35:07 +0000</pubDate>
		<dc:creator>howcome</dc:creator>
				<category><![CDATA[Sample documents]]></category>

		<guid isPermaLink="false">http://printingcss.com/?p=61</guid>
		<description><![CDATA[Prince 8 adds support for JavaScript which can — using the DOM — manipulate the content of the document. One example is the table of contents, which can be generated dynamically by a small script that (a) scans the documents for chapter headings, (b) generates a list with elements pointing to the chapter headings, and [...]]]></description>
			<content:encoded><![CDATA[<p>Prince 8 adds support for JavaScript which can — using the DOM — manipulate the content of the document. One example is the table of contents, which can be generated dynamically by a small script that (a) scans the documents for chapter headings, (b) generates a list with elements pointing to the chapter headings, and (c) inserts the list at the start of the document. To show of this new feature, we have <q>Oliver Twist</q> &mdash; a classic literary work with lots of chapters &mdash; and added a small JavaScript along with a CSS snippet. Here&#8217;s <a href="http://www.princexml.com/howcome/2011/oliver-twist/oliver-twist.html">the HTML source file</a> and the <a href="http://www.princexml.com/howcome/2011/oliver-twist/oliver-twist.pdf">resulting PDF file</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://printingcss.com/?feed=rss2&amp;p=61</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
		<item>
		<title>Prince, the 7th</title>
		<link>http://printingcss.com/?p=1</link>
		<comments>http://printingcss.com/?p=1#comments</comments>
		<pubDate>Mon, 10 Jan 2011 19:09:16 +0000</pubDate>
		<dc:creator>howcome</dc:creator>
				<category><![CDATA[Sample documents]]></category>

		<guid isPermaLink="false">http://printingcss.com/?p=1</guid>
		<description><![CDATA[To showcase the formatting magic that Prince can do, we have created one document packed with effects. The HTML document, which is contained in a 13k file, is packed with features: bi-directional text, OpenType features, CSS3 footnotes, web fonts (including WOFF), and CSS3 page floats. You can download the PDF document or the HTML source. [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.princexml.com/howcome/2010/magic/prince7.pdf"><img class=sample src="http://www.princexml.com/howcome/2010/magic/prince7.png" alt="" width="91" height="91" /></a>To showcase the formatting magic that Prince can do, we have created one document packed with effects. The HTML document, which is contained in a 13k file, is packed with features: bi-directional text, OpenType features, CSS3 footnotes, web fonts (including WOFF), and CSS3 page floats. You can download the <a href="http://www.princexml.com/howcome/2010/magic/prince7.pdf">PDF document</a> or the <a href="http://www.princexml.com/howcome/2010/magic/prince7.html">HTML source</a>. To produce the same PDF document from on your own computer, you should have the <em>Arno Pro</em> font installed. </p>
]]></content:encoded>
			<wfw:commentRss>http://printingcss.com/?feed=rss2&amp;p=1</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Ibsen reconstructed</title>
		<link>http://printingcss.com/?p=20</link>
		<comments>http://printingcss.com/?p=20#comments</comments>
		<pubDate>Mon, 10 Jan 2011 18:30:28 +0000</pubDate>
		<dc:creator>howcome</dc:creator>
				<category><![CDATA[Sample documents]]></category>

		<guid isPermaLink="false">http://printingcss.com/?p=20</guid>
		<description><![CDATA[Henrik Ibsen&#8217;s collected poems were first printed in 1871. The first edition was, as were most books at the time, set in lead by skilled printers. In 2010, I recreated the first edition in HTML and CSS. The «Steinschrift» and «Elzevir» fonts that were used by the printers in 1871 have not been transferred to [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://people.opera.com/howcome/2010/ibsen/#english"><img class=sample src="http://www.princexml.com/howcome/2011/ibsen/ibsen-sample.png" alt="" width="91" height="91" /></a></p>
<p>Henrik Ibsen&#8217;s collected poems were first printed in 1871. The first edition was, as were most books at the time, set in lead by skilled printers. In 2010, I recreated the first edition in <a href="http://people.opera.com/howcome/2010/ibsen">HTML</a> and CSS. The «Steinschrift» and «Elzevir» fonts that were used by the printers in 1871 have not been transferred to the digital domain, but lookalikes were found. The <a href="http://people.opera.com/howcome/2010/ibsen/tiltrykkeriet/digte.pdf">resulting PDF file</a> was printed in 100 copies and bound the old-fashioned way.</p>
]]></content:encoded>
			<wfw:commentRss>http://printingcss.com/?feed=rss2&amp;p=20</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The Guardian&#8217;s secrets &#8212; leaked!</title>
		<link>http://printingcss.com/?p=34</link>
		<comments>http://printingcss.com/?p=34#comments</comments>
		<pubDate>Mon, 10 Jan 2011 18:20:54 +0000</pubDate>
		<dc:creator>howcome</dc:creator>
				<category><![CDATA[Sample documents]]></category>

		<guid isPermaLink="false">http://printingcss.com/?p=34</guid>
		<description><![CDATA[Using Prince, web content can easily be recast into PDF. To show how this can be done, we have recreated a PDF newspaper from The Guardian. The text and images were extracted from the original PDF file and the content was encoded in HTML. Using Prince, a new PDF file was created. (Original PDF, HTML, [...]]]></description>
			<content:encoded><![CDATA[<p><a href="/samples/g24/recast.pdf"><img class=sample src="http://www.princexml.com/images/g24.png" alt="Newspaper" width="91" height="91" /></a></p>
<p>Using Prince, web content can easily be recast into PDF. To show how this can be done, we have recreated a PDF newspaper from <a href="http://www.guardian.co.uk">The Guardian</a>. The text and images were extracted from the original PDF file and the content was encoded in HTML. Using Prince, a new PDF file was created. (<a href="http://www.princexml.com/samples/g24/original.pdf">Original PDF</a>, <a href="http://www.princexml.com/samples/g24/recast.html">HTML</a>, <a href="http://www.princexml.com/samples/g24/recast.pdf">Prince-generated PDF</a>) </p>
]]></content:encoded>
			<wfw:commentRss>http://printingcss.com/?feed=rss2&amp;p=34</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Fiction: hard to write, easy to format</title>
		<link>http://printingcss.com/?p=32</link>
		<comments>http://printingcss.com/?p=32#comments</comments>
		<pubDate>Mon, 10 Jan 2011 18:19:52 +0000</pubDate>
		<dc:creator>howcome</dc:creator>
				<category><![CDATA[Sample documents]]></category>

		<guid isPermaLink="false">http://printingcss.com/?p=32</guid>
		<description><![CDATA[Using the boom! microformat, it&#8217;s easy to create books from HTML. Mark Burgess wrote his novel, called Slogans, in LaTeX. We converted it to HTML and added a few class names from the boom! vocabulary. Also, the boom! style sheet was modified in a few places to create the kind of presentation the author wanted. [...]]]></description>
			<content:encoded><![CDATA[<p><a href="/samples/slogans/slogans.pdf"><img class=sample src="http://www.princexml.com/images/slogans.png" alt="Fiction" width="91" height="91" /></a></p>
<p>Using the <a href="http://www.alistapart.com/articles/boom">boom! microformat</a>, it&#8217;s easy to create books from HTML. <a href="http://www.iu.hio.no/~mark/">Mark Burgess</a> wrote his novel, called Slogans, in LaTeX. We converted it to HTML and added a few class names from the boom! vocabulary. Also, the boom! style sheet was modified in a few places to create the kind of presentation the author wanted. Notice how the content of the back cover is shown first in the HTML version. We encourage you to read the novel and let the author know if you like it. (<a href="/samples/slogans/slogans.html">HTML</a>, <a href="/samples/slogans/boom.css">boom! style sheet</a>, <a href="/samples/slogans/slogans.pdf">Prince-generated PDF</a>)</p>
]]></content:encoded>
			<wfw:commentRss>http://printingcss.com/?feed=rss2&amp;p=32</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Boom! A microformat for books</title>
		<link>http://printingcss.com/?p=30</link>
		<comments>http://printingcss.com/?p=30#comments</comments>
		<pubDate>Mon, 10 Jan 2011 18:18:32 +0000</pubDate>
		<dc:creator>howcome</dc:creator>
				<category><![CDATA[Sample documents]]></category>

		<guid isPermaLink="false">http://printingcss.com/?p=30</guid>
		<description><![CDATA[In 2005, Addison-Wesley published a book that was formatted by Prince. Cascading Style Sheets &#8211; Designing for the web by H&#229;kon Wium Lie and Bert Bos describes the power of CSS. To prove how powerful it can be, the authors decided to use CSS in the production process. They later described their approach in an [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://people.opera.com/howcome/2005/ala/sample.pdf"><img class=sample src="http://www.princexml.com/images/cssdftw4crop.png" alt="CSS book" width="91" height="91" /></a></p>
<p>In 2005, Addison-Wesley published a book that was formatted by Prince. <cite>Cascading Style Sheets &#8211; Designing for the web</cite> by H&#229;kon Wium Lie and Bert Bos describes the power of CSS. To prove how powerful it can be, the authors decided to use CSS in the production process. They later described their approach in an article on <a href="http://www.alistapart.com">A list apart</a>: <a href="http://www.alistapart.com/articles/boom">Printing a Book with CSS: Boom!</a>. Prince is currently the only product which is able to produce print-quality PDF files from HTML and CSS files. (<a href="http://people.opera.com/howcome/2005/ala sample.html">HTML</a>, <a href="http://people.opera.com/howcome/2005/ala/boom.css">CSS</a>, <a href="http://people.opera.com/howcome/2005/ala/sample.pdf">PDF</a>)</p>
]]></content:encoded>
			<wfw:commentRss>http://printingcss.com/?feed=rss2&amp;p=30</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Product catalogs</title>
		<link>http://printingcss.com/?p=28</link>
		<comments>http://printingcss.com/?p=28#comments</comments>
		<pubDate>Mon, 10 Jan 2011 18:16:02 +0000</pubDate>
		<dc:creator>howcome</dc:creator>
				<category><![CDATA[Sample documents]]></category>

		<guid isPermaLink="false">http://printingcss.com/?p=28</guid>
		<description><![CDATA[Product catalogs are complex publications where errors can be fatal. Increasingly, they are offered both on the web and in print. By producing both versions from the same set of files, errors can be minimized. We have created a ficticious product catalog for fine flags that show how a PDF product catalog can be produced [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.princexml.com/howcome/2008/flags/flags.pdf"><img class=sample src="http://www.princexml.com/howcome/2008/flags/flags-sample.png" alt="" width="91" height="92" /></a></p>
<p>Product catalogs are complex publications where errors can be fatal. Increasingly, they are offered both on the web and in print. By producing both versions from the same set of files, errors can be minimized. We have created a ficticious product catalog for fine flags that show how a PDF product catalog can be produced from a simple HTML file (<a href="http://www.princexml.com/howcome/2008/flags/flags.pdf">PDF</a>, <a href="http://www.princexml.com/howcome/2008/flags/flags.html">HTML with CSS</a>). The flags themselves are <a href="http://en.wikipedia.org/wiki/Category:SVG_flags">SVG files</a> fetched from Wikipedia. Notice how the table is run into two columns. The table header and footer is repeated in both columns. The headers and footers reflect information (product codes and country names) from the pages. The background of the front page is one SVG image that is automatically repeated.</p>
]]></content:encoded>
			<wfw:commentRss>http://printingcss.com/?feed=rss2&amp;p=28</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Using Gentium as web fonts</title>
		<link>http://printingcss.com/?p=11</link>
		<comments>http://printingcss.com/?p=11#comments</comments>
		<pubDate>Wed, 28 Apr 2010 21:29:00 +0000</pubDate>
		<dc:creator>howcome</dc:creator>
				<category><![CDATA[Sample documents]]></category>

		<guid isPermaLink="false">http://printingcss.com/?p=11</guid>
		<description><![CDATA[Gentium is a beautiful font with an unusually wide range of characters. It has been developed by SIL and released under a liberal license. Therefore, it&#8217;s an ideal webfont which Prince can put to good use. In this sample document (HTML, CSS, PDF), we replace the main heading with another string by way of the [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.princexml.com/howcome/2008/webfonts/teng.pdf"><img class=sample src="http://www.princexml.com/howcome/2008/webfonts/gentium-sample.png" alt="" width="91" height="91" /></a><a href="http://scripts.sil.org/cms/scripts/page.php?site_id=nrsi&amp;item_id=Gentium">Gentium</a> is a beautiful font with an unusually wide range of characters. It has been developed by <a href="http://www.sil.org">SIL</a> and released under a <a href="http://scripts.sil.org/cms/scripts/page.php?site_id=nrsi&amp;item_id=OFL">liberal license</a>. Therefore, it&#8217;s an ideal webfont which Prince can put to good use. In this sample document (<a href="http://www.princexml.com/howcome/2008/webfonts/teng.html">HTML</a>, <a href="http://www.princexml.com/howcome/2008/webfonts/teng.css">CSS</a>, <a href="http://www.princexml.com/howcome/2008/webfonts/teng.pdf">PDF</a>), we replace the main heading with another string by way of the &#8216;content&#8217; property in CSS. The replacement is nonsensical in the sense that the glyphs have been borrowed from different scripts. But it looks neat!</p>
]]></content:encoded>
			<wfw:commentRss>http://printingcss.com/?feed=rss2&amp;p=11</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

