delorie.com/archives/browse.cgi   search  
Mail Archives: geda-user/2016/02/25/12:23:59

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=date:from:to:subject:message-id:in-reply-to:references:mime-version
:content-type:content-transfer-encoding;
bh=YwtjDGFxuX9bAsfYOmk/isWEEjiJPXi2vIIz6GHGNFE=;
b=LAk/nTWnkt9rLj3+sFUsol+5ZH8piLGbHAOUZZBwR4fb91kIEzuzDfZhchU6W7b8St
NOSpfG86VcGlVmx03NXLIHB1JiFl0Ti2/adaXqs8I/MTLQAGCTFdgwEDCB82MbmpnWQt
yofLaL7dpbOMatMYPApQRxLt6z5aeyATC9N5/l+AZUzt+4i1Dh1Ivcv+v1Hc6LOdpNBC
XF+tYpjeH2vFY06yBHCY6m8mXDQzjPMt+IPgMM/sAgA1EUBnJG47xSCH49XIBiU+3Pj0
kGORQS5OyqnyfvWzJ1fyE6poVvRnkC7LeLFhH/CWKaC1l2d/k/MLv4vib9BeFFyQCUB0
DTnw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:date:from:to:subject:message-id:in-reply-to
:references:mime-version:content-type:content-transfer-encoding;
bh=YwtjDGFxuX9bAsfYOmk/isWEEjiJPXi2vIIz6GHGNFE=;
b=fbW1mS+FQqzghj/BIYgcNW4617gLGqcpZjKinnnyJbyk6nch+7bclEcmIXJzQXPj4O
90ZJz71RF+PFAsQpSqJDpjgncUbQ3r/5C+jySCOSrRa2rrBJ174ja2f8jdBMGebPZy0P
FPpD2ZBkPMs8WUb2cddf0FqoQbaG9jhtFH1qnTxYOds6ihSnmJ5cx4ED8u5lt46dYADy
TMTjFL3Nq0KIWATE87DtoKXOUZB1HjAc6ITYmyM23okHPqOJoVPSLvKJ2WxsOVbMV1dF
DgEmFgWr2mcEO1dK4gGhKE8PsPgCZeH1WDXHlDcPYkR8+dkNjAiTRjXf2Tl++ErYWPsS
tPDA==
X-Gm-Message-State: AG10YORdftQh6IHfGFXBT+MsbA/DeCFWUxHLvetnKw7nD7snhQW1AdXw1mgTJTDxSFzzHQ==
X-Received: by 10.25.79.16 with SMTP id d16mr13918463lfb.73.1456421026298;
Thu, 25 Feb 2016 09:23:46 -0800 (PST)
Date: Thu, 25 Feb 2016 18:23:39 +0100
From: "Nicklas Karlsson (nicklas DOT karlsson17 AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To: geda-user AT delorie DOT com
Subject: Re: [geda-user] pcb import schematic crash, parantheses in netname
Message-Id: <20160225182339.a00134d1ca145e558c849b6f@gmail.com>
In-Reply-To: <DF33EEFC-7459-4EF2-945F-BAA8E83E1A61@noqsi.com>
References: <20160215215221 DOT fd472794e7b9446a243bfc40 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>
<59CE9019-7A!
56-49D6-BC2B-680A7253B055 AT noqsi 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>
X-Mailer: Sylpheed 3.5.0beta1 (GTK+ 2.24.25; x86_64-pc-linux-gnu)
Mime-Version: 1.0
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 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 gschem, which supports a variety of downstreams, each with its own needs, and a wide international community. The tool kit has no clear boundary.
> 
> John Doty              Noqsi Aerospace, Ltd.
> http://www.noqsi.com/
> jpd AT noqsi DOT com

Agree, for user allowing any UTF-8 character in any string is simple and consistent. For developer there may however be need for characters with special meaning.


Nicklas Karlsson

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019