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=eO8tnSEUZnqX/prBczqHYt+PoCG1XGpeVWEP7eUVkK4=;
        b=RnRmW+kaU91z2m3aq6xqLqDB+owhgMalxaib7gI6Y7y5N3DaSLW/wTwdrUfp4NkNj4
         l3d5kImD1caPMKOn/24mNdhoL8+3dJjUSnaOr5GqYrUX9JVVggCg2irj380sXrulaiCT
         VuFUuoELrYGnLMyDHCC9+bbSeZbWBOhMU39gOzRYKEfqWQ6rn7/OESJS+Yrk6LgnJfXB
         kX9MNW7VEFedMZoNLO1uOZwQDi6FRPn4d/1iWaxVnoKVxj5FEx420c5TUMC86pxwh96I
         lTyBCuUC96areSJ08WrByPqlERddabuspLWKw7hb4cMJRQ9jKM6xWEwq1mOKsFdwirZh
         7G/Q==
MIME-Version: 1.0
X-Received: by 10.52.83.227 with SMTP id t3mr10273993vdy.20.1409975140046;
 Fri, 05 Sep 2014 20:45:40 -0700 (PDT)
In-Reply-To: <CAM2RGhRGb+Vzq8kH1NX=DrZZP7DMMu8b50LkLtsk6-jxYp-DyA@mail.gmail.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>
Date: Sat, 6 Sep 2014 13:15:39 +0930
Message-ID: <CAHUm0tO5ZAE4FM0HF3TvK0LJVEP5ZHGPz6C_fTEvsLMqjdGquw@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>
Content-Type: multipart/alternative; boundary=001a11368e805d6d4805025d6b72
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
Precedence: bulk

--001a11368e805d6d4805025d6b72
Content-Type: text/plain; charset=UTF-8

if the usual "Symbol" code can be extended to interpret both traditional
Symbol['a' 1200] (...) definitions, and usage where a unicode is quoted,
i.e. Symbol['U+68FA' 1200] (...), the issue is just where to store the
glyphs.

Perhaps for unicode symbols, PCB could look in a "fonts" or "elements" or
"glyphs" subdirectory if the definition is not embedded within the pcb file.

An alternative is perhaps an extended symbol, and again, PCB would know to
look in a "fonts" or "elements" or "glyphs" subdirectory. The ordinary
"Symbol" could then continue to use the default_font without change, i.e.

ExtendedSymbol['uni68FA' 1200]
{
   SymbolLine[x1 y1 x2 y2 800]
   ...
   SymbolLine[x1 y1 x2 y2 800]
}

A simple tar.gz or a simple text file (much like a .bdf document) of the
Firefly bitmaps converted into discrete pcb compatible symbols, dropped
into a /fonts or /glyphs subdirectory would be a pretty easy way for people
to add chinese/japanese etc support or new glyphs to their installation.

On the fly conversion of bitmaps may be more error prone than pre-converted
elements.

If the PCB file format becomes binary, it would increase the barriers to
users contributing to the project. Text format helps with troubleshooting a
great deal, and automated production of symbols etc...

Cheers

Erich.





On Sat, Sep 6, 2014 at 8:22 AM, Evan Foss <evanfoss AT gmail DOT com> wrote:

> If you have to break out a text editor then you are ether...
> 1. On the bleeding edge of what the tool can do.
> 2. Breaking the unix common sense of "Don't fight the tool."
> 3. Finding a lot of bugs in the tool.
>
> I do resort to text editing for changing PCB silk screen text and for
> renumbering footprints after I have the drawn dimensions correct. What
> are you doing?
>
> -Evan
>
>
>
> On Fri, Sep 5, 2014 at 5:13 PM, DJ Delorie <dj AT delorie DOT com> wrote:
> >
> >> I and many others use gschem and pcb files in version control of
> >> some sort. The text file format is a huge bonus for us. Any zip type
> >> compression to package a file is a bad move as it breaks version
> >> control. I also love being able to hack at the PCB file in a text
> >> editor...
> >
> > I would assume that a "pcb file" could be just the text file (no
> > binaries attached), or a zip file (for distribution or archiving), or
> > a plain directory that represents the zip file (text files and
> > binaries as separate files).
>
>
>
> --
> Home
> http://evanfoss.googlepages.com/
> Work
> http://forge.abcd.harvard.edu/gf/project/epl_engineering/wiki/
>

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

<div dir=3D"ltr"><div><div>if the usual &quot;Symbol&quot; code can be exte=
nded to interpret both traditional
 Symbol[&#39;a&#39; 1200] (...) definitions, and usage where a unicode is q=
uoted, i.e. Symbol[&#39;U+68FA&#39; 1200] (...), the issue is just where to=
 store the glyphs.<br><div><br></div><div>Perhaps for unicode symbols, PCB =
could look in a &quot;fonts&quot; or &quot;elements&quot; or &quot;glyphs&q=
uot; subdirectory if the definition is not embedded within the pcb file.<br=
></div><div><br></div>An alternative is perhaps an extended symbol, and aga=
in, PCB would know to look in a &quot;fonts&quot; or &quot;elements&quot; o=
r &quot;glyphs&quot; subdirectory. The ordinary &quot;Symbol&quot; could th=
en continue to use the default_font without change, i.e.<br></div><div><br>=
ExtendedSymbol[&#39;uni68FA&#39; 1200]<br>{<br></div>=C2=A0=C2=A0 SymbolLin=
e[x1 y1 x2 y2 800]<br>=C2=A0=C2=A0 ...<br>=C2=A0=C2=A0 SymbolLine[x1 y1 x2 =
y2 800]<br>}<br><br></div><div>A simple tar.gz or a simple text file (much =
like a .bdf document) of the Firefly bitmaps converted into discrete pcb co=
mpatible symbols, dropped into a /fonts or /glyphs subdirectory would be a =
pretty easy way for people to add chinese/japanese etc support or new glyph=
s to their installation.<br></div><div><br></div><div>On the fly conversion=
 of bitmaps may be more error prone than pre-converted elements.<br></div><=
div><br></div><div>If the PCB file format becomes binary, it would increase=
 the barriers to users contributing to the project. Text format helps with =
troubleshooting a great deal, and automated production of symbols etc...<br=
><br></div><div>Cheers<br><br>Erich.<br></div><div><br><br></div><div><br><=
/div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Sat, =
Sep 6, 2014 at 8:22 AM, Evan Foss <span dir=3D"ltr">&lt;<a href=3D"mailto:e=
vanfoss AT gmail DOT com" target=3D"_blank">evanfoss AT gmail DOT com</a>&gt;</span> wrot=
e:<br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;b=
order-left:1px solid rgb(204,204,204);padding-left:1ex">If you have to brea=
k out a text editor then you are ether...<br>
1. On the bleeding edge of what the tool can do.<br>
2. Breaking the unix common sense of &quot;Don&#39;t fight the tool.&quot;<=
br>
3. Finding a lot of bugs in the tool.<br>
<br>
I do resort to text editing for changing PCB silk screen text and for<br>
renumbering footprints after I have the drawn dimensions correct. What<br>
are you doing?<br>
<br>
-Evan<br>
<div><div><br>
<br>
<br>
On Fri, Sep 5, 2014 at 5:13 PM, DJ Delorie &lt;<a href=3D"mailto:dj AT delorie=
.com" target=3D"_blank">dj AT delorie DOT com</a>&gt; wrote:<br>
&gt;<br>
&gt;&gt; I and many others use gschem and pcb files in version control of<b=
r>
&gt;&gt; some sort. The text file format is a huge bonus for us. Any zip ty=
pe<br>
&gt;&gt; compression to package a file is a bad move as it breaks version<b=
r>
&gt;&gt; control. I also love being able to hack at the PCB file in a text<=
br>
&gt;&gt; editor...<br>
&gt;<br>
&gt; I would assume that a &quot;pcb file&quot; could be just the text file=
 (no<br>
&gt; binaries attached), or a zip file (for distribution or archiving), or<=
br>
&gt; a plain directory that represents the zip file (text files and<br>
&gt; binaries as separate files).<br>
<br>
<br>
<br>
</div></div><span><font color=3D"#888888">--<br>
Home<br>
<a href=3D"http://evanfoss.googlepages.com/" target=3D"_blank">http://evanf=
oss.googlepages.com/</a><br>
Work<br>
<a href=3D"http://forge.abcd.harvard.edu/gf/project/epl_engineering/wiki/" =
target=3D"_blank">http://forge.abcd.harvard.edu/gf/project/epl_engineering/=
wiki/</a><br>
</font></span></blockquote></div><br></div></div>

--001a11368e805d6d4805025d6b72--