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:date:message-id:subject:from:to
	:content-type;
	bh=yV0dFiuv0SjNZWwRW0NFr2aJbEPKUtVYzg3SvCdEgJA=;
	b=qdx2yoPtw4aVqHErVh/jBTaEjP5+KHeRUAnwixs+OR0YwwKbuSLzmCzb0zYM9SxOAD
	Es3cGXefjKjIKcOIm6k4qPdQh9aAJ+bxbeYZOf40VFSjPh8uzQEhOTTnytCYoNVpfxBI
	5bPfRT5+RrU4Xpq2Pe6TzMzzzTen3cCvzp2N7kj/kvc1uUuQuBDtRF+K+xP2oeZ+t7UQ
	G36dJf0g8UOu0PeUxoEk4x2UB4Dyb2EQqKGJug/l8ZLE7K4fdNX0RZV+RIcYhRFEVShV
	ezZ22rlfq6UBt9ug7+HHNqf9PXbRwKbRy0tKadsSLPpj5Ypk1dxRzmEanN91iDNsOtgd
	XEpg==
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=yV0dFiuv0SjNZWwRW0NFr2aJbEPKUtVYzg3SvCdEgJA=;
	b=JrXM1PjMSUIeTCyDe8L+YubYOPmT91ol5IR2AT5zhX9y7gnG/Qy+sPRWpSg0DLrM5z
	sLMe/1Wnx8BkkMQEjw9FPDjP/ZYBxIias5uNyp/FUGi0zwTy5ahjtJiJAeOzQKv+BSWo
	kW+4qPmMqyjjApn2Omwz5CJL+I5tjJCbXSaYxl0GXHB6r6/tDWam2kFcvNxq6yCZIn0S
	8kEUTOqQyBTCeYz9qUvDP0M5G/ZPO+00qDDD6pJtS+/3KM14T71UYLLRGJYDW8aXS522
	jNBQXWt8p6IHD0nMpZA2aqxfyupT2I/An2faSuBFlvJkpvIZCgYcQhMZGvZDONca29iN
	o1zg==
X-Gm-Message-State:	AG10YOSFCMHyTFJ4tkKLyXHfNorO+Ab+/jFkqwuupl2vRFqpN87lnC5L8qtPQlE5hoUNvo3gfl/mH1m86jAg+g==
MIME-Version:	1.0
X-Received:	by 10.194.90.137 with SMTP id bw9mr46043836wjb.120.1456427045684;
	Thu, 25 Feb 2016 11:04:05 -0800 (PST)
In-Reply-To:	<DF33EEFC-7459-4EF2-945F-BAA8E83E1A61@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>
	<CAC4O8c9jr_b376SpuUk5HrJApP1c75oxsEBemn-i_xtC-rt-Zw AT mail DOT gmail DOT com>
	<201602162032 DOT u1GKWL7Y005291 AT envy DOT delorie DOT com>
	<CAC4O8c-ig=0UVAqagNXH_DBmC9uVQDu3Y1Gx7LBGmRCo0-_kVQ AT mail DOT gmail DOT com>
	<E75ECBB6-14E7-437A-B374-E0CF86BDFF1A AT noqsi DOT com>
	<CAC4O8c8z4JiJr=mgA+co4pX-yxu_pVsXpeKRYqneuxZNnYqh8g AT mail DOT gmail DOT com>
	<CAC4O8c-Hb+gpG3umUuRLUXTu5Vm3phYg56Y7mySFcHb2s_TAbA AT mail DOT gmail DOT com>
	<ABF671E8-1F11-4F8B-8F1D-C28E7EB68051 AT noqsi DOT com>
	<CAC4O8c9xQVC2W78b=1Yyk4vvrBaJpXsy8Fs_1C7wo=kPb6ON=A AT mail DOT gmail DOT com>
	<DF33EEFC-7459-4EF2-945F-BAA8E83E1A61 AT noqsi DOT com>
Date:	Thu, 25 Feb 2016 10:04:05 -0900
Message-ID:	<CAC4O8c8ce4sLhSGeoi_-RjiWhgrSnEu2m8tVSh9tRyb_=-G1FQ@mail.gmail.com>
Subject:	Re: [geda-user] pcb import schematic crash, parantheses in netname
From:	"Britton Kerin (britton DOT kerin AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To:	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

On Thu, Feb 25, 2016 at 5:39 AM, John Doty <jpd AT noqsi DOT com> wrote:
>
> On Feb 25, 2016, at 12:40 AM, Britton Kerin (britton DOT kerin AT gmail DOT com) [via geda-user AT delorie DOT com] <geda-user AT delorie DOT com> wrote:
>
>>
>> No, for a tool kit sane behavior involves a certain amount of
>> consistency.
>
> Yes. Allowing any UTF-8 character in any string is simple and consistent. Arbitrary rules make it harder for the user. This is especially true for

And pcb doesn't do it.  So in the case of gEDA, it's inconsistent, not
consistent, and the current rules are arbitrary, not predictable.  It
might be great if pcb handled it (debatable IMO) did but it doesn't,
and you're not volunteering to fix it.  So you're attitude is screw
pcb users (new ones in particular), I'm not even gonna set one
deconsistification switch so they can have a less buggy experience.  I
think that's a bad attitude but you're obviously decided about it and
we're repeating ourselves, so I'm done with this thread now.

Britton

- Raw text -