X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
X-TCPREMOTEIP: 207.224.51.38
X-Authenticated-UID: jpd AT noqsi DOT com
Content-Type: multipart/signed; boundary="Apple-Mail=_BA9E70ED-3DD6-4206-8D61-D51897E4E2E7"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Subject: Re: [geda-user] pcb import schematic crash, parantheses in netname
X-Pgp-Agent: GPGMail 2.5.2
From: John Doty <jpd AT noqsi DOT com>
In-Reply-To: <201602161814.u1GIE4N8030809@envy.delorie.com>
Date: Tue, 16 Feb 2016 11:48:23 -0700
Message-Id: <DB4746A0-011C-45FD-B52B-B8B140678481@noqsi.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> <CAJXU7q9d9VqBmqabKfE3M3banZ8jn2c3LaWxBSK9_YCm9XN3_w AT mail DOT gmail DOT com> <201602161814 DOT u1GIE4N8030809 AT envy DOT delorie DOT com>
To: geda-user AT delorie DOT com
X-Mailer: Apple Mail (2.1878.6)
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


--Apple-Mail=_BA9E70ED-3DD6-4206-8D61-D51897E4E2E7
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252


On Feb 16, 2016, at 11:14 AM, DJ Delorie <dj AT delorie DOT com> wrote:

>=20
>> 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..)
>=20
> You're talking about "what are legal characters for refdes's and
> netnames" but I'm talking about "what characters should gnetlist be
> able to handle properly".  At the level of "what strings get passed
> through without gnetlist crashing" it should be UTF-8.

gschem works fine with UTF-8. gnetlist doesn=92t crash when it sees =
UTF-8, although back ends generally seem to substitute =93?=94 for UTF-8 =
characters in output for some reason, even though the data passed to the =
back end is proper. Something about Guile output, I think.

>=20
> Sure there are syntax-related characters like / and - but those aren't
> problems *for gnetlist* as long as it passes them downstream
> correctly.
>=20
> If we decide we want to allow characters like / and - in netnames,
> refdes's, and whatnot, then we need to come up with a way for those
> names to be communicated between gschem and downstream without
> corruption or confusion - assuming downstream has a way of doing so.
> gsch2pcb uses '-' between refdes and pin, but File->Import doesn't,
> for example, so if we want to allow '-' in a netname, either gsch2pcb
> needs to be prepared to see two '-'s or we have to deprecate it in
> favor of File->Import.
>=20

As far as I know, the only character gschem can=92t put into a refdes or =
netname is NULL. So, a robustly coded back end should, in principle, =
alias anything in UTF-8 that the downstream will find troublesome. Most =
of our back ends are not that fussy.

John Doty              Noqsi Aerospace, Ltd.
http://www.noqsi.com/
jpd AT noqsi DOT com



--Apple-Mail=_BA9E70ED-3DD6-4206-8D61-D51897E4E2E7
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJWw274AAoJEF1Aj/0UKykRgLkP/A5wioV0mm2EIAi9/HVckS+f
sVZBidlc73c9/KPKmX7z5q5ZTMQ+owMFCQJrnsvvjga3N/sjF1Yt6BCu8RPkE/XM
QiLUspJIH7FlQlQ0gIDp41ew/kimkBMx6Kn/y/0DCwsIokU429GqzxdSrtg+XcMT
/cs5ueIUVkMYKzgTlx790XIGKB73ivYL7twSjyZwFI3jwO1K74qntg+zMn+sHDaj
4ZRo9oMLpHVxM4fASlXNbAb3EjgUFagTjmbzZk1XbVcb5iIxjACnHiBcgzdzo+tF
9c+908oHUbwcgKHPBA6o1T5O1NAvJ/BV6dfRCFMjYw+m187CfsyTmXu9e11Uv0ph
0CYaVFiJhWmp8xzeVlexKzY/pzdP1GzfAGTGzSewj8mFGkM/ZMoSmEhjnkBi6XZW
t806W/5siEVY99kd4ZBwtKTgV/CdUj9KUwzhlfZmm9J6+fDjSJfvlBOi8UiitsLo
K31fuvCDeWPOljxdD1gTrEDnGvgx9IrDlhWLtfDrSXIQIuJwSfV1hFvkiy1x0B9v
AOU5fXDQHy+vYqXqZ5syaxczEjJSBuDlaJESlhkvUtCXnsZvLBUfe4tGJApU8Frr
aZfZLju+9Vjtk3NDACMznl9ZixamCjQtlb60RZIJJHCX+AxfB6qvOidA+YGYRXsX
LWsJZ3BnbkmoCg+rMzZF
=JMq5
-----END PGP SIGNATURE-----

--Apple-Mail=_BA9E70ED-3DD6-4206-8D61-D51897E4E2E7--