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: References: <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> <20140905184829 DOT GH3196 AT cicely7 DOT cicely DOT de> <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> Date: Sat, 6 Sep 2014 13:15:39 +0930 Message-ID: Subject: Re: [geda-user] Chinese glyph rendering in pcb as symbols From: Erich Heinzle To: geda-user 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 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 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
if the usual "Symbol" code can be exte= nded to interpret both traditional Symbol['a' 1200] (...) definitions, and usage where a unicode is q= uoted, 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&q= uot; subdirectory if the definition is not embedded within the pcb file.

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

= ExtendedSymbol['uni68FA' 1200]
{
=C2=A0=C2=A0 SymbolLin= e[x1 y1 x2 y2 800]
=C2=A0=C2=A0 ...
=C2=A0=C2=A0 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 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.

On the fly conversion= of bitmaps may be more error prone than pre-converted elements.
<= 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...
Cheers

Erich.



<= /div>


On Sat, = Sep 6, 2014 at 8:22 AM, Evan Foss <evanfoss AT gmail DOT com> wrot= e:
If you have to brea= k 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."<= br> 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 ty= pe
>> 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<= br> >> 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<= br> > a plain directory that represents the zip file (text files and
> binaries as separate files).



--
Home
http://evanf= oss.googlepages.com/
Work
http://forge.abcd.harvard.edu/gf/project/epl_engineering/= wiki/

--001a11368e805d6d4805025d6b72--