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

Erin Millard <ezzatron@gmail.com> Sun, 04 September 2016 23:30 UTC

Return-Path: <emwebdev@gmail.com>
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 86DAE12B0EF for <precis@ietfa.amsl.com>; Sun, 4 Sep 2016 16:30:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 8E7cbViHLUqW for <precis@ietfa.amsl.com>; Sun, 4 Sep 2016 16:30:53 -0700 (PDT)
Received: from mail-vk0-x22d.google.com (mail-vk0-x22d.google.com [IPv6:2607:f8b0:400c:c05::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 387F212B097 for <precis@ietf.org>; Sun, 4 Sep 2016 16:30:53 -0700 (PDT)
Received: by mail-vk0-x22d.google.com with SMTP id j189so55591135vkc.2 for <precis@ietf.org>; Sun, 04 Sep 2016 16:30:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=q3KoFhCrihNYZeO8uC9eL50iZWguFQwt/XPaRzMUkW8=; b=YBKnfNaZ6Hqbg1pYci0voM9xIMsVjvOX05+DsghBGikqVJZdNAzUV1DRyygQOF/lZm FDlsUgm7v/tKbT85Jnq8JMstByF7xwqPuHJHlIWj7caK2DaUAV9R/ZMdDHKgwVq57lMk LxKriW6cIbbYG2FmLAPXJmnR8nUFQNFyDyQaxwrDGcrr4y/DPqkuqWEmxVWeqS75m4xb cGISY9gWlAWehBqyq2rIZfvME+gqBCQWp+h3IklcMttF09yjOng69FrxsPlv6BotUujF IunOSvSuSoRdLmmfOvX7dA8123EnBvY7kSGHhFDAv657s5t3uXFaqFX/cXscj3LFgVSC m9CA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=q3KoFhCrihNYZeO8uC9eL50iZWguFQwt/XPaRzMUkW8=; b=CMmBgS34bj10IONWPg1xtArCbNTC6YEqg8AyhzJaU3BslqM+tgiADmW4ga8jd9Oil+ Doptbzy03whs28Wo5EeQs/9b6CO0gWxZOoJU9Dj2z6kL1UR2O7hFjf+NIBPbH8kHoafG +Z/CYgux5Om7GTjn9Pwz6Af2WzEftW3RmL14PLtn5oAhkUYaxY1DmNyriZbSYYiney6S pwoN3QlbYluBImK/+LQ42wJc7bX0U1TbONR93WZhZ7CkNPmqQJEOKP+xLhD0mwv/+Rpv yOTBvCVEbSUzw7NYpeuAVlMAWKEt8PZE1BSz09SzOaAoOjwzeDZ5ocvr/Kelz0TMyjZS 84Cw==
X-Gm-Message-State: AE9vXwP6XbMs0jL1QfebbXOU/lRBf1d9SOVs/sGdAd/eza4XfT2dAFVtv5+2tapU4XZ5gCv3gOV9LCurs2t4UQ==
X-Received: by 10.31.76.2 with SMTP id z2mr14377479vka.105.1473031833883; Sun, 04 Sep 2016 16:30:33 -0700 (PDT)
MIME-Version: 1.0
Sender: emwebdev@gmail.com
Received: by 10.159.55.200 with HTTP; Sun, 4 Sep 2016 16:30:33 -0700 (PDT)
In-Reply-To: <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> <4A1BEC5B-4514-4BF3-AA81-412B94436591@stpeter.im>
From: Erin Millard <ezzatron@gmail.com>
Date: Mon, 5 Sep 2016 09:30:33 +1000
X-Google-Sender-Auth: Tlwn2iMIjWW8PuNpMsmC4RXvBzE
Message-ID: <CADz4d2Y0B5DNnQPi9XTCytDQW8Sge=+p3qRJCs3KfZe3UEy9eA@mail.gmail.com>
To: Peter Saint-Andre <stpeter@stpeter.im>
Content-Type: multipart/alternative; boundary=001a114db7d2339ca6053bb6f3ee
Archived-At: <https://mailarchive.ietf.org/arch/msg/precis/b7XfQxsVM5HILZFDZmkoCRu2YE4>
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 23:31:56 -0000

>
> >>> * §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.


This actually became a bigger issue when attempting to implement PRECIS
prepare in JavaScript for the browser. JavaScript doesn't have native UTF-8
support, so this meant the extra bloat of bringing in a UTF-8 library.

It didn't make a lot of sense to me either, since all the encoding affects
is how you go from string to code points, and vice versa. It had no effect
on the rest of my implementation. I could absolutely be missing something,
but compared to how focused the rest of the spec is, the UTF-8 requirement
seemed like an afterthought.

Can anyone explain which parts of PRECIS are actually predicated on the
original string being encoded in UTF-8?


On 5 September 2016 at 04:54, Peter Saint-Andre <stpeter@stpeter.im>; wrote:

>
>
> > 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
> _______________________________________________
> precis mailing list
> precis@ietf.org
> https://www.ietf.org/mailman/listinfo/precis
>