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=googlemail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:content-type;
	bh=VmKcADbSWvP6Qh1KDn434MuXkkzsBjFEGsgQzmzvJUc=;
	b=k+WJ/egEh1c0XGoKFNqusl2VCwvcSH04r17v7kULEridryfFU06rd03atLBvTbM5mK
	PRRm0sCFilHOBD72MVV21NOCr2kJbcpmuxjxP010lioKognc2WlxQpdZ0VniSKeU6TpZ
	1BGzjVvdPTrIIT/tngmj2EeDCpJq2tKswXazNgIowFv2MAkoLyAuTFYIjuquxfkUyiCl
	Smg2i7QvWpJJjKzNasAGnysNGGXBhEVbeK2/cXGjtkHNR3ws4Cj45BsjqdSoxZyIkHxE
	+G6D6El65bzZZBMNH/q6ZjUu63h1xU4bjZ+eII6bl93B3C2dOP2HZd6ymO1KIOay5xmg
	08pg==
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:date
	:message-id:subject:from:to:content-type;
	bh=VmKcADbSWvP6Qh1KDn434MuXkkzsBjFEGsgQzmzvJUc=;
	b=h6deUOhmhb4uiCkZFlj6+UoCI0CpCG5TP98Jre2t9NuGHOBU0XTPNNPIvMDQHg8Jed
	rB/TcooXXpAw0pxii36lvoQeGbju6ngkA/oEANEjvG6odTBl7OcrKsc4h/88wT1AXasT
	mwSiQuLG2izySJD9PoWBuDRnhZwayjZsa9f2CFQKxPu3Qbn6nfjaYfoLGoffVm4vxObI
	6aIDASbJnGOfpFKSw38K8Y4NNs2AKOJGtFj1s3KKS0S1NHyoPWpgc8fKQQryF9+vt1IT
	it9Kp1L9i7PdVJQAFJwbzvRseQspnHC9FzYqc9fbziRynGciLDnOZPUbeQjPLektfpGe
	xTaA==
X-Gm-Message-State:	AG10YOT0BNV07Uv00KV1RERVeE+F3sHQ+8pGpe+7Lsc7TJvKzQfDG2BV0epnedz1dyPPhCTYKVvo1fHRo/nMqQ==
MIME-Version:	1.0
X-Received:	by 10.60.94.82 with SMTP id da18mr17986967oeb.40.1455645814157;
	Tue, 16 Feb 2016 10:03:34 -0800 (PST)
In-Reply-To:	<201602161715.u1GHFMBB028078@envy.delorie.com>
References:	<20160215215221 DOT fd472794e7b9446a243bfc40 AT gmail DOT com>
	<201602152055 DOT u1FKtM4K011038 AT envy DOT delorie DOT com>
	<20160215220938 DOT bbc7eaa59d827cd0b261ea97 AT gmail DOT com>
	<D3167F4D-4750-49F8-9125-BDC4937F5C69 AT noqsi DOT com>
	<201602152135 DOT u1FLZrw9012774 AT envy DOT delorie DOT com>
	<7F210DE7-0A0B-42F9-ABBE-2C2768621186 AT noqsi DOT com>
	<20160216081722 DOT 1065cbed6653d3da4ffc7498 AT gmail DOT com>
	<201602160724 DOT u1G7Ox26001785 AT envy DOT delorie DOT com>
	<20160216085628 DOT b70143c330cd4da98a4603d3 AT gmail DOT com>
	<201602160805 DOT u1G85d8c003148 AT envy DOT delorie DOT com>
	<20160216092912 DOT 7f7439f703b49175a21dbb1b AT gmail DOT com>
	<CAJXU7q_w5NunkojiCr36RHRTq0hJ+PZP1e0GumTRMoGXcvgRXQ AT mail DOT gmail DOT com>
	<201602161715 DOT u1GHFMBB028078 AT envy DOT delorie DOT com>
Date:	Tue, 16 Feb 2016 18:03:34 +0000
Message-ID:	<CAJXU7q9d9VqBmqabKfE3M3banZ8jn2c3LaWxBSK9_YCm9XN3_w@mail.gmail.com>
Subject:	Re: [geda-user] pcb import schematic crash, parantheses in netname
From:	"Peter Clifton (petercjclifton AT googlemail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To:	gEDA User Mailing List <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

--089e011603f6abfaab052be6f3f9
Content-Type: text/plain; charset=UTF-8

Ok, that is one approach..

On the other hand, we already use "/" for discerning hierarchy, so that
already implies a certain restriction of legal characters within a net-name
portion. I'm sure we may also run into problems with our existing format,
with "-", where "-" is present in the net-name, and/or pin-name. (U1-1,
U2-2 etc..)


Peter



On 16 February 2016 at 17:15, DJ Delorie <dj AT delorie DOT com> wrote:

>
> > DJ... You wrote the action stuff, and the new import tool, what are your
> > thoughts on legal character set?  (Should it match whatever we can read
> in
> > .net files? Any idea what that allows? (I'm not currently at my
> computer).
>
> I'm going to stick with "UTF-8" and quote anything the action syntax
> uses.  I.e. make it an exlude list (via quoting), not an include list.
>
> We may not support all of UTF-8 everywhere, but that's no excuse not
> to aim for that target whenever we touch the code.
>

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

<div dir=3D"ltr"><div><div>Ok, that is one approach..<br><br></div>On the o=
ther hand, we already use &quot;/&quot; for discerning hierarchy, so that a=
lready implies a certain restriction of legal characters within a net-name =
portion. I&#39;m sure we may also run into problems with our existing forma=
t, with &quot;-&quot;, where &quot;-&quot; is present in the net-name, and/=
or pin-name. (U1-1, U2-2 etc..)<br><br></div><div><br></div><div>Peter<br><=
br><br></div></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote=
">On 16 February 2016 at 17:15, DJ Delorie <span dir=3D"ltr">&lt;<a href=3D=
"mailto:dj AT delorie DOT com" target=3D"_blank">dj AT delorie DOT com</a>&gt;</span> wro=
te:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-=
left:1px #ccc solid;padding-left:1ex"><span class=3D""><br>
&gt; DJ... You wrote the action stuff, and the new import tool, what are yo=
ur<br>
&gt; thoughts on legal character set?=C2=A0 (Should it match whatever we ca=
n read in<br>
&gt; .net files? Any idea what that allows? (I&#39;m not currently at my co=
mputer).<br>
<br>
</span>I&#39;m going to stick with &quot;UTF-8&quot; and quote anything the=
 action syntax<br>
uses.=C2=A0 I.e. make it an exlude list (via quoting), not an include list.=
<br>
<br>
We may not support all of UTF-8 everywhere, but that&#39;s no excuse not<br=
>
to aim for that target whenever we touch the code.<br>
</blockquote></div><br></div>

--089e011603f6abfaab052be6f3f9--

- Raw text -