DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:organization:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=KRgqkezf02K/63w6bl94dbnErTH8Qj2RSAOqMK5LRffe3+6XuuA9cgEQaP01dDM7OgROHtl6pze83PSbumP9fnVf50PCevBhrBFjJdGuZDeHr1pGZk0sg1yiJEJMdOrYpsglDGiV0al3uBGQ1NVaRFmLn5hgzJmSxBvw42jl7DU=
Message-ID: <445FC1C7.10704@gmail.com>
Date: Tue, 09 May 2006 00:10:15 +0200
From: Guillaume LELARGE <guillaume.lelarge@gmail.com>
Organization: traduc.org, postgresqlfr.org
User-Agent: Thunderbird 1.5 (X11/20060309)
MIME-Version: 1.0
To: Peter Eisentraut <peter_e@gmx.net>
CC: pgsql-docs@postgresql.org
Subject: Re: French PDF manual
References: <4459A4BC.7060809@gmail.com> <200605081927.53290.peter_e@gmx.net>
In-Reply-To: <200605081927.53290.peter_e@gmx.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit

Peter Eisentraut a écrit :
> Guillaume LELARGE wrote:
>> We started by changing SGML files in a way that makes them
>> syntactically correct and valid with an XML toolchain :
> 
> Well, you can go into the documentation source directory and type 'make 
> postgres.xml' to get an XML formatted DocBook file automatically.
> 
> It has occasionally been suggested to convert the source of the 
> documentation to XML, but while I'm not opposed to that, I don't see 
> any specific advantages coming from such a move.
> 

The PDF manual available on the postgresql web site is quite difficult
to use. For example, take a look at table 9.5 (pages 125 and 126). Text
goes beyond the cells. It's really difficult to read it. Sometimes you
can't read the text because it goes beyond the page : see pages 223 and
345).

I think these are real important issues.


-- 
Guillaume.