X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
X-Envelope-From:	paubert AT iram DOT es
Date:	Wed, 17 Oct 2012 10:13:19 +0200
From:	Gabriel Paubert <paubert AT iram DOT es>
To:	geda-user AT delorie DOT com
Subject:	Re: [geda-user] Text scaling during zoom in gschem
Message-ID:	<20121017081319.GA16322@visitor2.iram.es>
References:	<507b8d7c DOT 8ad3440a DOT 7926 DOT ffff8637 AT mx DOT google DOT com>
	<20121015092411 DOT 4eca1f3f AT svelte>
	<20121015171327 DOT GA25788 AT localhost DOT localdomain>
	<20121016083227 DOT GB12759 AT visitor2 DOT iram DOT es>
	<20121016141653 DOT GA27435 AT localhost DOT localdomain>
MIME-Version:	1.0
In-Reply-To:	<20121016141653.GA27435@localhost.localdomain>
User-Agent:	Mutt/1.5.20 (2009-06-14)
X-SPF-Received:	2
X-Spamina-Bogosity:	Ham
Reply-To:	geda-user AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	geda-user AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Tue, Oct 16, 2012 at 06:16:53PM +0400, Vladimir Zhbanov wrote:
> On Tue, Oct 16, 2012 at 10:32:27AM +0200, Gabriel Paubert wrote:
> ...
> > Why is there a different font for screen and printing, BTW?
> > 
> > I sometimes carefully place text (labels, whatever...) carefully to
> > not overlap any other graphic element. With different fonts, and 
> > font metrics, this could lead to nasty surprises.
> 
> You can find the answer there:
> http://www.mail-archive.com/geda-user AT moria DOT seul DOT org/msg19923.html
> 
> Browse the thread and you'll probably find the answers to all your
> questions.

Thanks, I did not remember that thread. Bottom line: any code
that generates graphics and does not use cairo should be
considered legacy and ultimately replaced.
 
Unfortunately, for example the recent gsch2pdf code relies
on cairo 1.10 at least, which is not yet in debian-stable.
I also think that I hit a bug (probably in libgeda) on a 
non-x86 machine: the output pdf scale depends on the directory 
in which symbols are found. It looks like a wild pointer/memory
corruption, but I won't be able to debug more before early
November. 

	Gabriel

- Raw text -