Re: [xml2rfc] [Rfc-markdown] New xml2rfc release: v2.12.1

Henrik Levkowetz <henrik@levkowetz.com> Mon, 29 October 2018 21:57 UTC

Return-Path: <henrik@levkowetz.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 ACA00131030; Mon, 29 Oct 2018 14:57:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 Jf6UUkpMOxoK; Mon, 29 Oct 2018 14:57:44 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:126c::1:2a]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B563D13102A; Mon, 29 Oct 2018 14:57:44 -0700 (PDT)
Received: from h-37-140.a357.priv.bahnhof.se ([94.254.37.140]:54622 helo=tannat.localdomain) by zinfandel.tools.ietf.org with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <henrik@levkowetz.com>) id 1gHFXb-0000Nn-S1; Mon, 29 Oct 2018 14:57:44 -0700
To: Miek Gieben <miek@miek.nl>
References: <E1gH6Wn-0002ca-CU@durif.tools.ietf.org> <20181029204446.xwjkdfdpj7sbhvsr@miek.nl> <0455bd48-3392-bb4c-f510-c57489792606@levkowetz.com> <20181029214325.5i3rrv55dpamvbsa@miek.nl>
Cc: xml2rfc-dev@ietf.org, xml2rfc@ietf.org
From: Henrik Levkowetz <henrik@levkowetz.com>
Message-ID: <a614b58e-0d4c-67d0-77f9-f5b6b66d7ff1@levkowetz.com>
Date: Mon, 29 Oct 2018 22:57:36 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <20181029214325.5i3rrv55dpamvbsa@miek.nl>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="AVIS1SM3RBqwkWf0mqb5W5BGQKOAaakod"
X-SA-Exim-Connect-IP: 94.254.37.140
X-SA-Exim-Rcpt-To: xml2rfc@ietf.org, xml2rfc-dev@ietf.org, miek@miek.nl
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000)
X-SA-Exim-Scanned: Yes (on zinfandel.tools.ietf.org)
X-Clacks-Overhead: GNU Terry Pratchett
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/345fSbAyv_wuv-yHrWK4GcDbaPg>
Subject: Re: [xml2rfc] [Rfc-markdown] New xml2rfc release: v2.12.1
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
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 Oct 2018 21:57:47 -0000

On 2018-10-29 22:43, Miek Gieben wrote:
> [dropping rfc-markdown]
> 
>>Hi Miek,
>>
>>The package is available on pypi: https://pypi.org/project/google-i18n-address/
>>If it's a matter of permitting an earlier version, I think that should be
>>quite possible.  If it's a matter of working around a complete absence, it's
>>more tricky.  Could you provide a bit more details on what options we have to
>>work with?
> 
> this creates a deb package: py2dsc-deb xml2rfc-2.12.1.orig.tar.gz, that would 
> install before, but now needs the google package.
> 
> py2dsc-deb fails for that pypi package (somewhere in testing, go figure).

Mph.  Might be worth looking into.

When I was asking for options, I wanted to explore if earlier versions of the
i18n-address package would work; whether it might work to pull it into the
xml2rfc distribution, and other possibilities, if you have suggestions.

> I don't want hold xml2rfc back by insisting older OSs should be installed 
> though. What do I miss when hack the google-i18n stuff out?

Country-specific address formatting.  Without it, you'll be stuck with the
fallback, which is very americentric for the text output, somewhat less so
for the html output (but not very refined).  I'd hate to see it go.


	Henrik