X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-Envelope-From: paubert AT iram DOT es Date: Fri, 15 Aug 2014 23:52:33 +0200 From: Gabriel Paubert To: geda-user AT delorie DOT com Subject: Re: [geda-user] rs-274x nits Message-ID: <20140815215233.GA5149@visitor2.iram.es> References: <53EA540E DOT 9000609 AT sonic DOT net> <2aabf5abd73cc057e4a0193bf4a2d101 AT mail DOT gmail DOT com> <53EA7E2C DOT 40804 AT sonic DOT net> <1407881745 DOT 18877 DOT YahooMailNeo AT web120505 DOT mail DOT ne1 DOT yahoo DOT com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1407881745.18877.YahooMailNeo@web120505.mail.ne1.yahoo.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-Spamina-Bogosity: Unsure X-Spamina-Spam-Score: -0.2 (/) X-Spamina-Spam-Report: Content analysis details: (-0.2 points) pts rule name description ---- ---------------------- -------------------------------------------------- -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP 0.8 BAYES_50 BODY: Bayes spam probability is 40 to 60% [score: 0.4605] 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 > However, perhaps the role of spaces could be > clarified. Where are spaces allowed other than after the '0' in a > block comment and within strings? Can spaces exist at the ends of a > string and will they be part of the string or discarded? The latter > is of particular importance since Value Attributes are strings; the > examples never show a space in a value attribute, but spaces are not > expressly forbidden. Well, the format specification is changing quite fast, there are significant differences with respect to spaces between J1 (February 2014) and J3 (July 2014). In J1: "The character code 32 (SP, Space) is reserved for use in comments." In J3: "SP can only be used inside strings and comments. They cannot be used anywhere else, not inside or between commands, not between data blocks, etc." But this last sentence is contradicted by: Strings are made up of all valid characters except the reserved characters SP, CR, LF, ‘%’, ‘*’, ‘,’ and ‘;’. In J1 the comma was not listed as a reserved character. However in the regular expression they give (same in both versions), I have seen neither the square brackets, nor the dollar sign (allowed in names!), nor the backquote nor a few others and there is a dash which is obviously in the wrong place ("+-/" includes the comma!). Furthermore, there seems to be a space before the closing bracket. In other words, it might be worth contacting UCAMCO because the documentation is inconsistent. I believe that the correct regex for strings (provided you use the C locale) is: [][a-zA-Z0-9 !"#$&'()+./:<=>?@\^_`{|}~-] Gabriel