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=dnfOQH0kOoymyYAQeHTpuyd6QuNwty8DZSrzVNpiVHw=; b=NRVsx4/UJH8qiShSzSepSyLfmacWKjYJ9W01F+BYdEneKygNUtaMjL9u7bQhgwId3y NApXsBfJY8qcbUjqr0+yuoQIqu9u9qjX5SQg//LS4nGt4c8+LrNLHUnwNeggzDPhU09Q 6wpuivjPlx5bn0AY9pKBpBqVnEsJUzsIK9mst2p1QA1I59oSl/6iVulpEdhFHkqzpa3K Oehdek6ThqmbqL0ih/4HOSDB7gbaM9htIGL1c9a3zmhU6KNyAaGYxhyVcdnl3DSkaW5p PoQVBmEDfJ+QMUfQ91+qALGqOopkVoFsCQttmOnkEoonBK9KLEpJz3wkC7vOqcDYX0LX zoiw== MIME-Version: 1.0 X-Received: by 10.52.245.66 with SMTP id xm2mr2445135vdc.36.1409242391917; Thu, 28 Aug 2014 09:13:11 -0700 (PDT) In-Reply-To: <201408281531.s7SFVGWn020908@envy.delorie.com> References: <201408281531 DOT s7SFVGWn020908 AT envy DOT delorie DOT com> Date: Fri, 29 Aug 2014 01:43:11 +0930 Message-ID: Subject: Re: [geda-user] Fonts for PCB Designer From: Erich Heinzle To: geda-user AT delorie DOT com Content-Type: multipart/alternative; boundary=001a11c257aa2c390a0501b2d030 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 --001a11c257aa2c390a0501b2d030 Content-Type: text/plain; charset=UTF-8 I have revised the license to GPL v2 to simplify things. My bad on the terminology for PCB, I'd seen it referred to as such amongst geda PCB instructions somewhere, I thought. I have fixed that. These fonts are a simple drop in replacement for default_font, which at this stage lives in /geda/pcb/src So, no UTF is needed. In the absence of a mechanism for selecting fonts in PCB, the only idea I had was a subdirectory in src named fonts The utility is standalone, only uses stdio, and has an attached README.txt users.on.net/~esh/geda/pcb/src/fonts/README.txt for some reason the FTP server does not like listing README.txt or README files. The gothic and sans fonts use the normal ASCII/US keyboard mapping The cyrillic font uses a keyboard mapping based on the Hershey fonts as distributed. There are four or more types of cyrillic keyboard mapping, so I have just thrown in a glyph table to assist anyone trying to use it. This is my first bit of c code that does anything useful, so makefiles might take a bit of time, but I'll give it a crack. I will try and do a diff on on my local filesystem changes and submit it, but it will be ~ 0.5MB. Cheers, Erich On Fri, Aug 29, 2014 at 1:01 AM, DJ Delorie wrote: > > > If someone with git credentials could commit them, that would be > > appreciated. > > Cool stuff! But before they can be committed anywhere, some comments... > > * commit *where*? The url just has a few files with no README or > diff. The typical git process would be for you to "git > format-patch" to extract your local commit of the files into an > email that someone else could commit upstream. > > * You specify GPL 3 but pcb uses GPL 2. While normally this isn't a > problem, using a different license may result is confusion or > perhaps legal problems later on. > > * "PCB Designer" is Allegro's layout tool. gEDA's tool is just "PCB" > or "gEDA/PCB". > > * Could you give some examples of how PCB can use a non-ASCII font? > We haven't added support for UTF or (officially) Latin-1. Or does > the user need to know how to map ASCII symbols to different glyphs > in your fonts? If so, that mapping would need to be documented too. > > * We'd also need a diff for all the Makefiles and stuff to make sure > the *.c is built and everything is included in the distribution > tarball. > --001a11c257aa2c390a0501b2d030 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I have revised the license to GPL= v2 to simplify things.

My bad on the terminology for PCB, I&#= 39;d seen it referred to as such amongst geda PCB instructions somewhere, I= thought. I have fixed that.

These fonts are a simple drop in replacement for default_font, wh= ich at this stage lives in /geda/pcb/src
So, no UTF is needed= .

In the absence of a mechanism for selecting fonts= in PCB, the only idea I had was a subdirectory in src named fonts

The utility is standalone, only uses stdio, and has an attached R= EADME.txt

users.on.net/~esh/geda/pcb/src/fonts/README.txt

for some reason the FTP server does not like listing README.txt or README f= iles.

The gothic and sans fonts use the normal ASCII/= US keyboard mapping

The cyrillic font uses a keyboard map= ping based on the Hershey fonts as distributed.
There are four or more types of cyrillic keyboard mapping, so I have just t= hrown in a glyph table to assist anyone
trying to use it.

<= div>This is my first bit of c code that does anything useful, so makefiles = might take a bit of time, but I'll give it a crack.

I will try and do a diff on on my local filesystem changes a= nd submit it, but it will be ~ 0.5MB.

Cheers,

Erich





On Fri, Aug 29, 2014 at 1:01 AM, DJ Delo= rie <dj AT delorie DOT com> wrote:

> If someone with git credentials could commit them, that would be
> appreciated.

Cool stuff!=C2=A0 But before they can be committed anywhere, some com= ments...

* commit *where*?=C2=A0 The url just has a few files with no README or
=C2=A0 diff.=C2=A0 The typical git process would be for you to "git =C2=A0 format-patch" to extract your local commit of the files into an=
=C2=A0 email that someone else could commit upstream.

* You specify GPL 3 but pcb uses GPL 2.=C2=A0 While normally this isn't= a
=C2=A0 problem, using a different license may result is confusion or
=C2=A0 perhaps legal problems later on.

* "PCB Designer" is Allegro's layout tool.=C2=A0 gEDA's t= ool is just "PCB"
=C2=A0 or "gEDA/PCB".

* Could you give some examples of how PCB can use a non-ASCII font?
=C2=A0 We haven't added support for UTF or (officially) Latin-1.=C2=A0 = Or does
=C2=A0 the user need to know how to map ASCII symbols to different glyphs =C2=A0 in your fonts?=C2=A0 If so, that mapping would need to be documented= too.

* We'd also need a diff for all the Makefiles and stuff to make sure =C2=A0 the *.c is built and everything is included in the distribution
=C2=A0 tarball.

--001a11c257aa2c390a0501b2d030--