X-Authentication-Warning: delorie.com: mail set sender to geda-help-bounces using -f
X-Recipient: geda-help AT delorie DOT com
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=date:from:to:subject:message-id:mail-followup-to:references
         :mime-version:content-type:content-disposition
         :content-transfer-encoding:in-reply-to:user-agent;
        bh=zqIDV3U7dolRb6UzSA4nqtmSP9r9CipcGQHJvHFgJyc=;
        b=YUFGvFcApONojnpRikgdWbEneXWtTwZBns4jQ5pB3xQ4jcPM9V06p1NqckOOXEJ0wD
         nk4CQS8DnMCAQCmLdU557Z8OgYYDmnojsjkqo7CdC9kJxbX35aX5O749Y1ZzXYukaCKz
         7qkxj5HfeTFrgFM1IxqOBgBTQgKIgidX4T385mM/SwD0xRyLN90EWsDLXt/2n+p7PF1Y
         F1u6gc1CurZE6J7TGPW53COIudd2ev8WMAP1FXpM0zDdM8GZqA2uS+qKH46DJgrWULD/
         dMpoQiGl95zVv5kx1a1SxdQqp4yHSw+5P6hQDFbOZnJ2eE5FiLNnxiwXcrT/PDHl1ehz
         7XRg==
Date: Mon, 19 Nov 2012 21:02:13 +0400
From: Vladimir Zhbanov <vzhbanov AT gmail DOT com>
To: geda-help AT delorie DOT com
Subject: Re: [geda-help] gEDA unicode in Windows
Message-ID: <20121119170213.GA805@localhost.localdomain>
Mail-Followup-To: geda-help AT delorie DOT com
References: <CALAx6z+PMLsX3Eur-5XhH2PvSov=zux=keYagFK8QQsxLCT8KA AT mail DOT gmail DOT com>
 <20120810185145 DOT GA29860 AT localhost DOT localdomain>
 <1353273569 DOT 20740 DOT 4 DOT camel AT localhost>
 <1573288 DOT jXLjm2htlG AT harrington DOT peter-b DOT co DOT uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <1573288.jXLjm2htlG@harrington.peter-b.co.uk>
User-Agent: Mutt/1.5.21 (2010-09-15)
Reply-To: geda-help AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: geda-help AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

On Sun, Nov 18, 2012 at 10:52:21PM +0000, Peter TB Brett wrote:
...
> > Actually, I don't think gschem copes properly with _printing_ generic
> > unicode symbols. On-screen should work just fine, but IIRC, the
> > printing code has not yet been updated to use cairo rendering.
> 
> I'm confused. What was the bug 720218 patch set about?  I'm sure that 
> printing unicode symbols should work... I have many schematics that use 
> mu, Omega etc. and they seem to print fine (on Linux)!

The patchset was about incorrect glyphs in Postscript. Unfortunately, It
cannot fix a fact that some printing fonts don't contain some glyphs
(like Nimbus Sans not containing cyrillic ones). Therefore in some cases
a workaround would be to change the printing font. I use this workaround
very often because Nimbus Sans is the default font to substitute for
Helvetica in Debian.  For example, I can see all these symbols on my
screen: µ μ Ω Ω; but only first (mu) is visible in my output Postscript
when the font is Helvetica, and only first (mu) and third (omega) when
the font is Arial. Two others are showing as square boxes.

-- 
http://vzhbanov.byethost33.com