Re: [Tools-discuss] UTF-8 box characters with wavy lines in XML2RFC v3 draft

Tom Pusateri <pusateri@bangj.com> Wed, 06 November 2019 02:39 UTC

Return-Path: <pusateri@bangj.com>
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E28EC12002E for <tools-discuss@ietfa.amsl.com>; Tue, 5 Nov 2019 18:39:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=bangj.com
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 fPVAxDF4fKbf for <tools-discuss@ietfa.amsl.com>; Tue, 5 Nov 2019 18:39:06 -0800 (PST)
Received: from oj.bangj.com (69-77-154-174.static.skybest.com [69.77.154.174]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EEE3E120154 for <tools-discuss@ietf.org>; Tue, 5 Nov 2019 18:39:05 -0800 (PST)
Received: from [172.16.10.110] (mta-107-13-246-59.nc.rr.com [107.13.246.59]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by oj.bangj.com (Postfix) with ESMTPSA id F27542D771; Tue, 5 Nov 2019 21:39:04 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=bangj.com; s=201907; t=1573007945; bh=AITwzOUU/DOyUt8rpaLKwaPvLW/9neJ1hFW+Q3IVcMQ=; h=From:Subject:Date:In-Reply-To:Cc:To:References:From; b=JdTa7vGVrh5m8HziSf8vao43nxbG/1wSlx4gJorXZutUdn8T8S60x4l7MHZGtmTRV wXJ6h/ONy+Zh1D9omFjL9W4QKZqc9f3KmUA2oZ1ZCuKkbk4ijeSbG66zUf/tF0yEtn azNxa2e52wd7XZnbq0NpbZWlYUhQKYqruUEEsH2PLUp78KiVvTpVnzh9XF1grQ/Wh/ u8LtktV48tWca+nVGFlgN2C+EMrktX6Si+e9H7m5B8Hftx3P91j6GrN3AKPXirz70A gyzg3oR7qND8e1zRE27p1VikTN6CZUvmKuu41ku0EAxT/vBHL7UUwL+JvAIuEk9dFT 7PbjbYC3x6BqQ==
From: Tom Pusateri <pusateri@bangj.com>
Message-Id: <8BE4B9D2-4145-43C4-AA9E-2DAE68F2765F@bangj.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_6454F2E2-DD02-4A7A-B043-38C4D2309E01"
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3601.0.10\))
Date: Tue, 5 Nov 2019 21:39:04 -0500
In-Reply-To: <eca7be6d-dabe-21b1-725f-36c897940382@nostrum.com>
Cc: Tom Pusateri <pusateri=40bangj.com@dmarc.ietf.org>, tools-discuss <tools-discuss@ietf.org>
To: Adam Roach <adam@nostrum.com>
References: <157288484424.16663.3995065379449438987.idtracker@ietfa.amsl.com> <E2A5257F-8926-4570-81E1-288DDDC6DA34@bangj.com> <eca7be6d-dabe-21b1-725f-36c897940382@nostrum.com>
X-Mailer: Apple Mail (2.3601.0.10)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/VDcmKKEuitwqY7ukW_Do5fGY3Gc>
Subject: Re: [Tools-discuss] UTF-8 box characters with wavy lines in XML2RFC v3 draft
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-discuss/>
List-Post: <mailto:tools-discuss@ietf.org>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Nov 2019 02:39:09 -0000

We were told on this list that box characters were allowed in artwork.

Tom

> On Nov 5, 2019, at 9:33 PM, Adam Roach <adam@nostrum.com>; wrote:
> 
> While v3 allows Unicode characters, it's not a free-for-all anything-goes permission. RFC 7997 outlines the nine very narrowly scoped ways that Unicode can be used in v3 documents. I can't find one that covers the use in your draft. Which one do you think applies?
> 
> /a
> 
> On 11/5/19 7:21 PM, Tom Pusateri wrote:
>> Hi,
>> 	As a follow up to DKG’s comments about v3 submissions and UTF-8 box characters, we recently submitted this draft.
>> 
>> We did get the new v3 HTML version referenced in the document datatracker if you click the “status” link below, you will see the first HTML link is the new version.
>> We also got the old HTML version using the htmlized link in the document datatracker. This seems unnecessary to me.
>> 
>> But below, you see two htmlized links in the outgoing email and neither of these refer to the new v3 HTML version.
>> 
>> I would like to see both of these links removed and replaced with a link to the v3 HTML version in the announcement email.
>> 
>> Also, note how the box characters in the v3 HTML version end up are unaligned? There is probably something going wrong here in the CSS or maybe our source but I’m not sure what. Maybe we’re not using the correct vertical bar? Any help on that would be appreciated so we don’t get wavy lines.
>> 
>> Thanks,
>> Tom
>> 
>>> Begin forwarded message:
>>> 
>>> From: internet-drafts@ietf.org <mailto:internet-drafts@ietf.org>
>>> Subject: New Version Notification for draft-pusateri-dnsop-update-timeout-04.txt
>>> Date: November 4, 2019 at 11:27:24 AM EST
>>> To: "Tim Wattenberg" <mail@timwattenberg.de <mailto:mail@timwattenberg.de>>, "Tom Pusateri" <pusateri@bangj.com <mailto:pusateri@bangj.com>>
>>> 
>>> 
>>> A new version of I-D, draft-pusateri-dnsop-update-timeout-04.txt
>>> has been successfully submitted by Tim Wattenberg and posted to the
>>> IETF repository.
>>> 
>>> Name:		draft-pusateri-dnsop-update-timeout
>>> Revision:	04
>>> Title:		DNS TIMEOUT Resource Record
>>> Document date:	2019-11-04
>>> Group:		Individual Submission
>>> Pages:		17
>>> URL:            https://www.ietf.org/internet-drafts/draft-pusateri-dnsop-update-timeout-04.txt <https://www.ietf.org/internet-drafts/draft-pusateri-dnsop-update-timeout-04.txt>
>>> Status:         https://datatracker.ietf.org/doc/draft-pusateri-dnsop-update-timeout/ <https://datatracker.ietf.org/doc/draft-pusateri-dnsop-update-timeout/>
>>> Htmlized:       https://tools.ietf.org/html/draft-pusateri-dnsop-update-timeout-04 <https://tools.ietf.org/html/draft-pusateri-dnsop-update-timeout-04>
>>> Htmlized:       https://datatracker.ietf.org/doc/html/draft-pusateri-dnsop-update-timeout <https://datatracker.ietf.org/doc/html/draft-pusateri-dnsop-update-timeout>
>>> Diff:           https://www.ietf.org/rfcdiff?url2=draft-pusateri-dnsop-update-timeout-04 <https://www.ietf.org/rfcdiff?url2=draft-pusateri-dnsop-update-timeout-04>
>>> 
>>> Abstract:
>>>   This specification defines a new DNS TIMEOUT resource record (RR)
>>>   that associates a lifetime with one or more zone resource records.
>>>   It is intended to be used to transfer resource record lifetime state
>>>   between a zone's primary and secondary servers and to store lifetime
>>>   state during server software restarts.
>>> 
>>> 
>>> 
>>> 
>>> Please note that it may take a couple of minutes from the time of submission
>>> until the htmlized version and diff are available at tools.ietf.org <http://tools.ietf.org/>;.
>>> 
>>> The IETF Secretariat
>>> 
>> 
>> 
>> 
>> ___________________________________________________________
>> Tools-discuss mailing list
>> Tools-discuss@ietf.org <mailto:Tools-discuss@ietf.org>
>> https://www.ietf.org/mailman/listinfo/tools-discuss <https://www.ietf.org/mailman/listinfo/tools-discuss>
>> 
>> Please report datatracker.ietf.org and mailarchive.ietf.org
>> bugs at http://tools.ietf.org/tools/ietfdb <http://tools.ietf.org/tools/ietfdb>
>> or send email to datatracker-project@ietf.org <mailto:datatracker-project@ietf.org>
>> 
>> Please report tools.ietf.org bugs at
>> http://tools.ietf.org/tools/issues <http://tools.ietf.org/tools/issues>
>> or send email to webmaster@tools.ietf.org <mailto:webmaster@tools.ietf.org>
> 
> ___________________________________________________________
> Tools-discuss mailing list
> Tools-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/tools-discuss
> 
> Please report datatracker.ietf.org and mailarchive.ietf.org
> bugs at http://tools.ietf.org/tools/ietfdb
> or send email to datatracker-project@ietf.org
> 
> Please report tools.ietf.org bugs at
> http://tools.ietf.org/tools/issues
> or send email to webmaster@tools.ietf.org