X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=acXJsaaMsEwpxUvbc/Bk74ey23WerKoj9H6Pq6Md2Pk=; b=Hc/lFJ0gsQQL7ywgFIy47IxA7RwhRPjJyBIvh+hT11EFXO7NBjURGqBjyGWG7Jved8 RId0p+zARwLLbmEKIDDLyCD7/SiZTUMrU1yBjKvN7k//FFZIiyFfiQ/kmHqYeaUDf6RQ 1xGfb9887iFELSsXYvVthPvJcg41qN2poggrHvE1xJjdca3KQEMjrA2/l4YYZ1JlGDjZ nkOJo1kwgNRbTTxxglbK2omeULGB0GizQkycpbAVHC4O0tJfbjWHe+WeJjFclwmMjq+g 5X+DN6Q4X2RnPsgD51wFMJU9lRUZloRpYN4d5EC8SRzWvuiH8/62WeSQdyy6Gk8O+auu 7FdQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=acXJsaaMsEwpxUvbc/Bk74ey23WerKoj9H6Pq6Md2Pk=; b=QDQfGIkmTIljmOYSZUvmnoC7NDaSnogE6EnLSLtTFHk/mtbCRqsW2Gc4weg+eA7Mu8 PhBVYrwLmeZpYczLOtIoNBjGqG0CagVG58XpnnMJhyP2PqQUJBhLt5ol/ixKVgrb10Ga z2p5Lg0gvsmL2WugZDFd9Du5hE5xnHr4h5cn5aVf6IX3hK/prUWqB3naaeCjn9pZfcUn ptMiQa27ATFZaNl5aGJUk4hWDObp2XVO77T0pSp5Bb5gT6PuT2z0cPxwi24cnwaPrOPX ASirgXtUH9XkeZY3ZUOxxEL1/mEz/S1GReP4cYPC0JcQQM75q+UA2V5NYE8U4vjd8FI0 KQ0w== X-Gm-Message-State: AEkooutkyA4cA2xUr9y1ybzogUfP3c8AYU1081/3n4jB/cVwXdgA2U/S30XIMOBrcNVh7kqeNibOZeV7yssjaA== X-Received: by 10.31.199.135 with SMTP id x129mr10724446vkf.27.1469624006898; Wed, 27 Jul 2016 05:53:26 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: From: "Chad Parker (parker DOT charles AT gmail DOT com) [via geda-user AT delorie DOT com]" Date: Wed, 27 Jul 2016 08:53:26 -0400 Message-ID: Subject: Re: [geda-user] [pcb] Font Characters Stored in pcb File? To: geda-user AT delorie DOT com Content-Type: multipart/alternative; boundary=001a114847aee277c505389d80a3 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 --001a114847aee277c505389d80a3 Content-Type: text/plain; charset=UTF-8 Compatibility and consistency are good reasons. Has the font ever changed before? Another solution might be to give the font a name, say, "pcb font 2016", and reference the name of the font in the text definition, or perhaps have a line somewhere in the file that specifies the font to use in the design. Then the fonts could be stored internal to pcb. If the font is tweaked, give it a new name. Existing layouts call out the old name, and get the intended font. And if someone decided to implement other fonts at some point, it would also give the user a way to make a selection. --Chad On Tue, Jul 26, 2016 at 9:45 PM, Kai-Martin Knaak wrote: > Chad Parker wrote: > > > I noticed that when I save a brand new pcb file (File->New, > > File->Save As...) with nothing in it, just a completely empty file, > > that the file was actually 30k. When I looked at it, I saw that > > there appears to be the definition for the default font stored in > > the file. > > > > I was just curious about why this is? What were the considerations > > that factored into this design decision? I apologize if I missed > > this somewhere in the docs. > > > IMHO, the intention is to make sure layouts stay exactly the same if > the pcb it is opened with a different version of pcb. This different > (future) version may be equipped with a different default font. > > A change of fonts is potentially disruptive as text can be placed in > copper. E.g. a wider font may cause shorts with traces. However, > because the font actually used is embedded in the file, all copper > will come out as intended. > > That said, when I edit pcb files manually, I find the 30 kB font > section slightly awkward, too. A solution to achieve a more "clean" > layout file while still maintaining reliability would be to declare > the current default font in pcb source to be "static". Developers > would vow to never change it in future versions of pcb. This is less > ludicrous than it sounds. There are many more aspects that are never > to be changed if we want to make sure that old designs still render > the same with future versions of pcb. > > ---<)kaimartin(>--- > > --001a114847aee277c505389d80a3 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Compatibility and consistency are good reasons.
Has the font ever changed before?

Another solution might be to giv= e the font a name, say, "pcb font 2016", and reference the name o= f the font in the text definition, or perhaps have a line somewhere in the = file that specifies the font to use in the design. Then the fonts could be = stored internal to pcb. If the font is tweaked, give it a new name. Existin= g layouts call out the old name, and get the intended font. And if someone = decided to implement other fonts at some point, it would also give the user= a way to make a selection.

--Chad

On Tue, Jul 26, 2016 at 9:45 PM, Ka= i-Martin Knaak <kmk AT familieknaak DOT de> wrote:
Chad Parker wrote:

> I noticed that when I save a brand new pcb file (File->New,
> File->Save As...) with nothing in it, just a completely empty file,=
> that the file was actually 30k. When I looked at it, I saw that
> there appears to be the definition for the default font stored in
> the file.
>
> I was just curious about why this is? What were the considerations
> that factored into this design decision? I apologize if I missed
> this somewhere in the docs.
>
IMHO, the intention is to make sure layouts=C2=A0 stay exactly the s= ame if
the pcb it is opened with a different version of pcb. This different
(future) version may be equipped with a different default font.

A change of fonts is potentially disruptive as text can be placed in
copper. E.g. a wider font may cause shorts with traces. However,
because the font actually used is embedded in the file, all copper
will come out as intended.

That said, when I edit pcb files manually, I find the 30 kB font
section slightly awkward, too. A solution to achieve a more "clean&quo= t;
layout file while still maintaining reliability would be to declare
the current default font in pcb source to be "static". Developers=
would vow to never change it in future versions of pcb. This is less
ludicrous than it sounds. There are many more aspects that are never
to be changed if we want to make sure that old designs still render
the same with future versions of pcb.

---<)kaimartin(>---


--001a114847aee277c505389d80a3--