X-Authentication-Warning: delorie.com: mail set sender to geda-help-bounces using -f X-Recipient: geda-help AT delorie DOT com Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Apple Message framework v1085) Subject: Re: [geda-help] gEDA unicode in Windows From: John Doty In-Reply-To: <1353273569.20740.4.camel@localhost> Date: Sun, 18 Nov 2012 21:08:28 -0700 Message-Id: <281EB50E-778C-4AFA-B5DA-69B9ACF8F943@noqsi.com> References: <20120810185145 DOT GA29860 AT localhost DOT localdomain> <1353273569 DOT 20740 DOT 4 DOT camel AT localhost> To: geda-help AT delorie DOT com X-Mailer: Apple Mail (2.1085) Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id qAJ48Xqx003961 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 Nov 18, 2012, at 2:19 PM, Peter Clifton 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. That's my experience. I can place Japanese text in a schematic without trouble, it renders correctly on screen, but PostScript interpreters barf at printed output. > > I vaguely recall that certain symbols (possibly including omega) did > previously print to post-script correctly, Yes, Ω has worked OK for awhile. But in general, the printing code cannot cope with Unicode. John Doty Noqsi Aerospace, Ltd. http://www.noqsi.com/ jpd AT noqsi DOT com