Re: [xml2rfc] RFC Bibtex format doi numbering incorrect

"John R Levine" <johnl@taugh.com> Mon, 29 May 2017 21:12 UTC

Return-Path: <johnl@taugh.com>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A542129468 for <xml2rfc@ietfa.amsl.com>; Mon, 29 May 2017 14:12:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=aOwPwGC1; dkim=pass (1536-bit key) header.d=taugh.com header.b=dZfIKJ4u
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Jb_Ys8_raG_z for <xml2rfc@ietfa.amsl.com>; Mon, 29 May 2017 14:12:26 -0700 (PDT)
Received: from miucha.iecc.com (www.iecc.com [IPv6:2001:470:1f07:1126::4945:4343]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 903051201F2 for <xml2rfc@ietf.org>; Mon, 29 May 2017 14:12:26 -0700 (PDT)
Received: (qmail 42769 invoked from network); 29 May 2017 21:12:25 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=a70f.592c8eb9.k1705; bh=hfsgTEL5ZshzFfqfU8OoxcbjYtmI+XnTSeU1JtCcSfw=; b=aOwPwGC1Z72FVaaiLtohXTCcBl4ZGY2mUpaRIe4Y2lprfXWavOX/EeAa+ib+GxJ4r4CMEjFMhJPmUXIhExw31WaG5QIstzXn+bYHlT2LQU55CC97UA8CfVy+RbOSMar9BU/m7e9WkvhewC4qKPh+mSsYecos1pqnQgXqENMemCkMc8I7C8z9SgejJWZBlGo6rAML8F9wnNu+VKPh1bzxvI0Fij2juoYl88BkpgCsUUj6/Gtt7hg722ax0ro6S9dW
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=a70f.592c8eb9.k1705; bh=hfsgTEL5ZshzFfqfU8OoxcbjYtmI+XnTSeU1JtCcSfw=; b=dZfIKJ4u4N1PgMbbUfQnAg+X4LMN0cBlNf+Hilafcy0lmZYLo+poGlBJpQYerV4Qnng6yXIyfG9g7APs6HSSpum/NvgslIf/s2jzMdEdwOu4NPDIWy7Q7hmDYAwOxQX/G7smY87NoyN3+tf9cXZ4SKcUpQ6dLPguxI/hGZn6kIoEQPvCN1xAneMdl3z+ZIsnWdFSRghZBME+uOjumeqarCZAGe0WKb4Fxu7ArD8NLk4rIEkIbzbAIXk8uFRCjgVU
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2/X.509/AEAD) via TCP6; 29 May 2017 21:12:25 -0000
Date: Mon, 29 May 2017 17:12:25 -0400
Message-ID: <alpine.OSX.2.21.1705291711510.50914@ary.qy>
From: John R Levine <johnl@taugh.com>
To: Julian Reschke <julian.reschke@gmx.de>
Cc: xml2rfc@ietf.org
In-Reply-To: <40342552-00c2-ece5-a773-8c7646ebb715@gmx.de>
References: <20170528214929.56669.qmail@ary.lan> <038e5bd1-726c-599d-38cf-a65b7385856b@gmx.de> <a92f6a44-38cf-3c5a-49c8-676596f14c5f@gmail.com> <40342552-00c2-ece5-a773-8c7646ebb715@gmx.de>
User-Agent: Alpine 2.21 (OSX 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/ZY81bZmOoynfQ1Xrfl0mHYfMwU8>
Subject: Re: [xml2rfc] RFC Bibtex format doi numbering incorrect
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc/>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 May 2017 21:12:28 -0000

>>  I don't understand your point: wherever you look up other arbitrary
>>  strings, such as the document title, you can look up the DOI string.
>>  ...
> But I don't.

Then your code is even more broken than we realized.  If you are unable 
to fix it, I'm sure we can find someone who can.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly