<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#336666" bgcolor="#FFFFFF">
<div class="moz-cite-prefix"><imho><br>
It's my assumption that the purpose of a PDF is to represent a
printed book, so I will typically include all the bits that make
that PDF into a book if printed. There are still lots of people
who print PDFs (or at least parts). If someone reading the PDF
online has to jump over a blank page here or there, that seems
like a minor inconvenience compared to the bad pagination when
printed double sided. Whether you start with page "1" or "i" seems
less important to me and I can totally see the point of forgoing
the roman numbering, since that's a holdover from when the
frontmatter was generated separate from the body. (I do still
prefer the roman numbering, just because it "feels" better to me
though.)<br>
<br>
If you're providing PDFs primarily as "online documentation," that
seems like a bad idea to me. PDF is a horrible format to read
online. It's certainly fine in a pinch or if that's all that is
provided, but a well thought out HTML-based (searchable and fully
indexed) set of online docs, is much more efficient.<br>
</imho><br>
<br>
Cheers,<br>
<br>
...scott<br>
<br>
<br>
On 12/17/14 5:35 PM, Gillian Flato wrote:<br>
</div>
<blockquote
cite="mid:B228401D-C471-4F69-A6EE-6EA533CA5C15@pi-coral.com"
type="cite">
<pre wrap="">Do you guys still follow print protocols and produce PDFs with an even number of pages per chapter, or no, since everyone reads PDFs online and hardly anyone prints a manual anymore?
Thanks!
Gillian Flato
Technical Publications
Pi-Coral, Inc.
<a class="moz-txt-link-abbreviated" href="mailto:gillian.flato@pi-coral.com">gillian.flato@pi-coral.com</a>
</pre>
</blockquote>
<br>
</body>
</html>