IETF Logo Mail Archive

Re: [precis] I-D Action: draft-ietf-precis-7700bis-01.txt

Peter Saint-Andre <stpeter@stpeter.im> Sun, 04 September 2016 18:54 UTC

Return-Path: <stpeter@stpeter.im>
X-Original-To: precis@ietfa.amsl.com
Delivered-To: precis@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7755412B0C3 for <precis@ietfa.amsl.com>; Sun, 4 Sep 2016 11:54:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.41
X-Spam-Level:
X-Spam-Status: No, score=-3.41 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.508, SPF_HELO_PASS=-0.001, SPF_PASS=-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 OWPS_D44HAIL for <precis@ietfa.amsl.com>; Sun, 4 Sep 2016 11:54:35 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id EF3E012B0C1 for <precis@ietf.org>; Sun, 4 Sep 2016 11:54:34 -0700 (PDT)
Received: from [10.66.239.125] (unknown [166.177.123.46]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 6BB854003C; Sun, 4 Sep 2016 12:54:44 -0600 (MDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (1.0)
From: Peter Saint-Andre <stpeter@stpeter.im>
X-Mailer: iPhone Mail (13G36)
In-Reply-To: <CAHbk4R+ibZ8bbn6jk1b+-V0gxu=u6C4abqw37JaZJwZOyb0NZQ@mail.gmail.com>
Date: Sun, 04 Sep 2016 12:54:31 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <4A1BEC5B-4514-4BF3-AA81-412B94436591@stpeter.im>
References: <20160505174255.20595.13753.idtracker@ietfa.amsl.com> <CAHbk4RJVGUxrMYoOX6e7Z924C1Na-uhYsc8SKScBa3rc4j-1jQ@mail.gmail.com> <f6a03acb-4454-d17d-610a-ab87751f57d5@stpeter.im> <CAHbk4R+ibZ8bbn6jk1b+-V0gxu=u6C4abqw37JaZJwZOyb0NZQ@mail.gmail.com>
To: Sam Whited <sam@samwhited.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/precis/iY0SDqwjiu9IYqSdVneC8EGnLLA>
Cc: peter@filament.com, precis@ietf.org
Subject: Re: [precis] I-D Action: draft-ietf-precis-7700bis-01.txt
X-BeenThere: precis@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Preparation and Comparison of Internationalized Strings <precis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/precis>, <mailto:precis-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/precis/>
List-Post: <mailto:precis@ietf.org>
List-Help: <mailto:precis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/precis>, <mailto:precis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 04 Sep 2016 18:54:36 -0000


> On Sep 4, 2016, at 8:28 AM, Sam Whited <sam@samwhited.com> wrote:
> 
> On Sat, Sep 3, 2016 at 4:21 PM, Peter Saint-Andre <stpeter@stpeter.im> wrote:
>>> * §2.1: "May any instances of non-ASCII space be mapped…" sounds odd,
>>> should this just say "Instances of non-ASCII space should be mapped…"
>> 
>> Typo: s/May/Map/
> 
> That makes the document read: "Map any instances of non-ASCII space be
> mapped to ASCII space"; the "be mapped" still needs to be removed in
> the current draft.

Oops. Easy enough to fix, though!
> 
>>> * §2.2 Specifies that UTF-8 MUST be used as the encoding; do we really
>>> want to limit this to UTF-8 only? Is this for comparison purposes?
>>> Then again, 99.99% of the time UTF-8 is what you should be using
>>> anyways, so I'm not sure that it matters.
>> 
>> UTF-8 is your friend, and everything in PRECIS is UTF-8.
> 
> PRECIS is mostly encoding agnostic; implementations might favor a
> specific encoding, but I don't think anything in the spec specifically
> *needs* UTF-8. That being said, there are so few reasons to use
> anything other than UTF-8 that I don't think it really matters, it was
> just curious to me that some of the PRECIS related specs called out
> UTF-8 and some didn't.

I thought they all did, but will double-check.

Thanks!

Peter

v2.23.0 | Report a Bug | By Email