<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 02/04/2013 07:11 AM, IJff, E.G. wrote:<br>
<blockquote
cite="mid:2CCE6758D973944B8B734044891B958012393C1D@PEXMB001A.vu.local"
type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<style type="text/css" id="owaParaStyle"></style>
<div style="direction: ltr;font-family: Tahoma;color:
#000000;font-size: 10pt;">
<div class="column">
<p>L.S.,</p>
<p><br>
</p>
<p>Reading the svn-book 1.7 I found the following lay out
flaws (up to chap. 2, an still reading).</p>
<p>First you will find the text in the book, then my remark.</p>
<p><br>
</p>
<p>Best regards,</p>
<p>Bert</p>
</div>
</div>
</blockquote>
<br>
Bert, <br>
<br>
Thanks for the reportNearly all of this is stuff we know about --
and which largely is outside our decided ability to control. This
book is written in DocBook XML, translated into FO and then
ultimately into the PDF version you read by tooling. Sometimes, the
tooling does stuff wrong. That's what you're seeing. It's ugly, at
times, but we're pretty disinterested in micro-managing the
appearance of the PDF. Our focus is on content. If the rendering
issues are a roadblock to your parsing the book content, though,
perhaps reading the HTML version would work better for you?<br>
</body>
</html>