X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:content-type;
	bh=sl3v4J2y87/vhFEp6M7otAqvGXnMAhnz3K7JW6wMllg=;
	b=kgxSRK1c+qunfFO7KyqkPxKvtRrgvkp+5y9NeiBYGKKptecxE8y6K7rf2mZcXlGMXI
	QZ/MrRZVg0RlZpFRemQxynvdlw4avLU1C0Wti21zl2PwaCurjbTsare1j0IlFgNSEH0N
	P3zkfOERnKid8uhc3nfd7WnOvUk5Mja1LCKu1+8YC4MDRPqdvHguCGViUXkCbjW6ajbO
	F/To7W4m8i1nGIR2gujjB9d8MsGcU4oIa0eUujwV/sutanpd9Ym0jnSErSr6w6FTZh4i
	DMen7zq/Gqz7f4hSkfq+qlfi7bNMkpJoZ5ly2lBZ/ojz5Th8ypl2GytB8Kscf85f2tAg
	RR+A==
MIME-Version:	1.0
X-Received:	by 10.220.175.17 with SMTP id v17mr14429301vcz.0.1409984915739;
	Fri, 05 Sep 2014 23:28:35 -0700 (PDT)
In-Reply-To:	<201409060538.s865cSmr017110@envy.delorie.com>
References:	<CAHUm0tMk1cQm_DPVt_swzTGDA+FRL-37fUougH_3hNaqwR_LOQ AT mail DOT gmail DOT com>
	<201409051618 DOT s85GIdb8024685 AT envy DOT delorie DOT com>
	<5409F1C2 DOT 3090406 AT xs4all DOT nl>
	<201409051752 DOT s85Hqnr2027362 AT envy DOT delorie DOT com>
	<CAOFvGD5S+Gw_TPiuu3VkT53jvLewZbiP6f2BTaFRhJJP7Ai-1Q AT mail DOT gmail DOT com>
	<20140905184829 DOT GH3196 AT cicely7 DOT cicely DOT de>
	<CAOFvGD5NT=mCa24GEfv2UKGam29-h47Q3NFdcx9Gw=pg3n49=g AT mail DOT gmail DOT com>
	<20140905204312 DOT GJ3196 AT cicely7 DOT cicely DOT de>
	<540A22EF DOT 5030701 AT estechnical DOT co DOT uk>
	<201409052113 DOT s85LDfxf001064 AT envy DOT delorie DOT com>
	<CAM2RGhRGb+Vzq8kH1NX=DrZZP7DMMu8b50LkLtsk6-jxYp-DyA AT mail DOT gmail DOT com>
	<CAHUm0tO5ZAE4FM0HF3TvK0LJVEP5ZHGPz6C_fTEvsLMqjdGquw AT mail DOT gmail DOT com>
	<201409060357 DOT s863vvBL013729 AT envy DOT delorie DOT com>
	<CAHUm0tONW9T4zqoj2Be==A2OMoCr310igPgpVkxnu58st4=RtQ AT mail DOT gmail DOT com>
	<201409060459 DOT s864xXhR015788 AT envy DOT delorie DOT com>
	<CAHUm0tND2b+5m0+F2bXNCrA8ZddDLGVx=R5G4r2dSX2dxgreGw AT mail DOT gmail DOT com>
	<201409060538 DOT s865cSmr017110 AT envy DOT delorie DOT com>
Date:	Sat, 6 Sep 2014 15:58:35 +0930
Message-ID:	<CAHUm0tOhuv+75YZgbTnLihnJ8s9SPTPEA4+fMpMQ2BjZ4p1bRA@mail.gmail.com>
Subject:	Re: [geda-user] Chinese glyph rendering in pcb as symbols
From:	Erich Heinzle <a1039181 AT gmail DOT com>
To:	geda-user <geda-user AT delorie DOT com>
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

--047d7b3a7ebe0a97c005025fb2a9
Content-Type: text/plain; charset=UTF-8

>
> But to do a bitmap font, we'd need to convert each pixel into a
> separate polygon (square).
>
> The gerbers for either solution would be huge, though.  Simple stroked
> fonts (like pcb's default) are pretty gerber-friendly.
>

My parsing code turns contiguous vertical, diagonal and horizontal pixels
in the 16x16 bitmap stored in a bdf format into pcb strokes. That is how
the example I attached yesterday was done.

The example attachment also showed a "dot matrix" version of the glyphs for
comparison, if the bitmap is done without conversion into strokes.
Converting bitmap pixels to strokes as I have done is more evolved than dot
matrix, and less evolved than outline fonts, but it scales without losing
legibility and relies on gerber friendly strokes only.

Polygons would enable perfect rendering of outline fonts, but would be less
compact, and the symbol rendering code then has to be extended to support
polygons as well.

It seems the gnu project have released the unifont, which includes the
chinese characters, as a bdf.tar.gz file at

http://unifoundry.com/unifont.html

which, with the right parsing code, could generate stroked pcb symbols for
any of the unifont bitmaps.

Anyway, perhaps a native chinese speaker/reader/user is needed to opine on
the utility of bitmapped fonts or the need for more elegant outline fonts.

Cheers,

Erich.

--047d7b3a7ebe0a97c005025fb2a9
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><div class=3D"gmail_quote">=
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
But to do a bitmap font, we&#39;d need to convert each pixel into a<br>
separate polygon (square).<br>
<br>
The gerbers for either solution would be huge, though.=C2=A0 Simple stroked=
<br>
fonts (like pcb&#39;s default) are pretty gerber-friendly.<br>
</blockquote></div><br></div><div class=3D"gmail_extra">My parsing code tur=
ns contiguous vertical, diagonal and horizontal pixels in the 16x16 bitmap =
stored in a bdf format into pcb strokes. That is how the example I attached=
 yesterday was done.<br><br>The example attachment also showed a &quot;dot =
matrix&quot; version of the glyphs for comparison, if the bitmap is done wi=
thout conversion into strokes. Converting bitmap pixels to strokes as I hav=
e done is more evolved than dot matrix, and less evolved than outline fonts=
, but it scales without losing legibility and relies on gerber friendly str=
okes only.<br><br></div><div class=3D"gmail_extra">Polygons would enable pe=
rfect rendering of outline fonts, but would be less compact, and the symbol=
 rendering code then has to be extended to support polygons as well.<br><br=
>It seems the gnu project have released the unifont, which includes the chi=
nese characters, as a bdf.tar.gz file at<br>=C2=A0<br><a href=3D"http://uni=
foundry.com/unifont.html">http://unifoundry.com/unifont.html</a><br><br></d=
iv><div class=3D"gmail_extra">which, with the right parsing code, could gen=
erate stroked pcb symbols for any of the unifont bitmaps.<br><br></div><div=
 class=3D"gmail_extra">Anyway, perhaps a native chinese speaker/reader/user=
 is needed to opine on the utility of bitmapped fonts or the need for more =
elegant outline fonts.<br><br></div><div class=3D"gmail_extra">Cheers,<br><=
br>Erich.<br></div></div>

--047d7b3a7ebe0a97c005025fb2a9--

- Raw text -