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=yAj5NdVZcoHP8lVljVnFdpIrTG4nrdamuqp1K0b/cw0=; b=ANx8qQ7UZ7D3Oit3IbOVa2cNlK/p4tPnw5XBafE3vFL2j82NKouvTDIJZpZ0UkEZzy gatqzf7wzpRp9IYE19UwQw0e5o1DavGqL9qCO2ZFEuE4R82vGWdqsZxyRFefZtyE2eb7 PGsGiuonYqc4b7ytBbe5YZpZuFPiaDEHXFLwEXvJRbbm0S5B+T+IUOAvB0Gy3F24gLfA 9COymAjDTJ2zpl2wkImu/x3wFKWTAF4/dh+ZNkx/Cb1kcNkDDDMC3y/OIM6nYOkxkMsr H8N1eNvxUdu4MfH6b1QxgFeISb7t8uJ+sko1AmLe5mTwMC8HaXeZVg+To41jPLDLizjb JBYg== 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=yAj5NdVZcoHP8lVljVnFdpIrTG4nrdamuqp1K0b/cw0=; b=BIHPt2/z+1ts6Vj6iVNpgV2+RBvkpiYCBdhZvum/aDHbKIBy7vanSk8zaJstLB3ba/ FGqWYL/jsYONN/pugUul5APo/F/D367IHSA8OgPdyxW1zcSIH+R7P0Kj/O1SkaOee9yJ 6fXGd/lCgvsstVBA6uhfegJOXvSS6aCSiiVbm14J4X7qLtvB4t2mRxWf5I2+9huqD8iC tQ6i3W9jZwCNVVFw/XXlBvvHzXOqgGQqpj7kJOQ1hj8NfpIXL+UPSdb6oS2JrQD1LCee YuGcC2X624b+5bpigljfJj3YkJ7SD+apHg/pMKxqlsXOKWc2H6mlpqTz+RB0GV6V0Z8R OJEg== X-Gm-Message-State: AG10YOQBtCIyoKp/71iYE4OHYntfwEDPg8nNvkegS+kv365noiH45r0wpfQ4nbYLjJ9xqBqt/o9ZJhayEstixQ== MIME-Version: 1.0 X-Received: by 10.28.92.195 with SMTP id q186mr20260542wmb.37.1455653980240; Tue, 16 Feb 2016 12:19:40 -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> <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> <201602161715 DOT u1GHFMBB028078 AT envy DOT delorie DOT com> Date: Tue, 16 Feb 2016 11:19:40 -0900 Message-ID: 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]" To: geda-user AT delorie DOT com Content-Type: text/plain; charset=UTF-8 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 On Tue, Feb 16, 2016 at 8:15 AM, DJ Delorie 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. The excuse is that doing that will lead to bugs. The additional expressiveness from a wider character set is minimal and not worth it. I agree with Peter it's better to support a limited set well than a more extensive one inconsistently. Programs should reject all bad input, and that includes input that for whatever reason they don't yet support consistently, even if in theory they could. Britton