Replying so that this message is reflected in the SG16 list archives due
to an archive failure following the transition to the new SG16 mailing list.

Tom.

On 11/18/19 8:27 PM, Steve Downey via SG16 wrote:
> Other than the bureaucracy of getting a new line into Normative
> References, I think making the reference to TR31 explicit would be
> helpful, rather than making people bounce through the standards docs,
> in _addition_ to a reference to the Unicode Standard.
>
> On Mon, Nov 18, 2019 at 1:54 PM Steven R. Loomis via SG16
> <sg16_at_[hidden] <mailto:sg16_at_[hidden]>> wrote:
>
> Hello,
> https://www.unicode.org/reports/about-reports.html#Types may also
> be helpful.
>
> > A Unicode Standard Annex (UAX) forms an integral part of the
> Unicode Standard, but is published as a separate document. The
> Unicode Standard may require conformance to normative content in a
> Unicode Standard Annex, if so specified in the Conformance chapter
> of that version of the Unicode Standard. The version number of a
> UAX document is always the same as the version of the Unicode
> Standard of which it forms a part.
>
> As noted in the link Tom gave, use the URL with the hyphen in it
> (such as tr31-31.html) to reference a specific version.
>
> Hope this helps,
>
> --
> Steven R. Loomis | @srl295 | git.io/srl295 <http://git.io/srl295>
> (IBM)
>
>
>
> > El nov. 18, 2019, a las 10:48 a. m., Tom Honermann via SG16
> <sg16_at_[hidden] <mailto:sg16_at_[hidden]>> escribió:
> >
> > On 11/18/19 5:04 PM, Steve Downey via SG16 wrote:
> >> Yes, once we add the identifier rules. Although I'm not sure if
> it's technically part of the Unicode Standard or a separate standard.
> > It is a "Standard Annex" according to
> https://www.unicode.org/reports/tr31/tr31-31.html. I'm not sure
> how "standard annexes", "technical standards", and "technical
> reports" are differentiated; they all have link names of "tr##".
> >
> > Guidance for how to reference the annexes is available at
> http://www.unicode.org/versions/index.html#Unicode_Standard_Annexes.
> >
> > Tom.
> >
> >>
> >> On Mon, Nov 18, 2019 at 12:00 PM Zach Laine via SG16
> <sg16_at_[hidden] <mailto:sg16_at_[hidden]>> wrote:
> >> That sounds pretty clearly like Annex #31 needs to be added to
> the standard's normative references, independent of 10646.
> >>
> >> Zach
> >>
> >> On Mon, Nov 18, 2019 at 6:10 AM Steve Downey via SG16
> <sg16_at_[hidden] <mailto:sg16_at_[hidden]>> wrote:
> >> Annex U just says:
> >>
> >> The Unicode Consortium publishes a document "UAX 31 –
> Identifier and Pattern Syntax" to assist in the
> >> standard treatment of identifiers in UCS character-based
> parsers. Those specifications are recommended
> >> for determining the list of UCS characters suitable for use in
> identifiers. The document is available at
> >>
> >> http://www.unicode.org/reports/tr31/.
> >>
> >> On Mon, Nov 18, 2019, 06:20 <keld_at_[hidden]
> <mailto:keld_at_[hidden]>> wrote:
> >> yes I would think so, but I prefer to use ISo specks when possible.
> >>
> >> keld
> >>
> >> On Sun, Nov 17, 2019 at 06:16:23PM -0500, Steve Downey wrote:
> >> > Probably the same as TR31 from the Unicode Standard?
> >> >
> >> > https://unicode.org/reports/tr31/
> >> >
> >> > We will be revisiting using that for 23, and have not ruled
> out treating it
> >> > as fixing a defect report.
> >> >
> >> >
> >> >
> >> > On Sun, Nov 17, 2019, 17:22 <keld_at_[hidden]
> <mailto:keld_at_[hidden]>> wrote:
> >> >
> >> > > the annex of 10646 in question is Annex U (informative)
> Characters in
> >> > > identifiers .
> >> > >
> >> > >
> >> > > keld
> >> > >
> >> > > On Sun, Nov 17, 2019 at 08:48:52AM +0100, keld_at_[hidden]
> <mailto:keld_at_[hidden]> wrote:
> >> > > >
> >> > > > I think weshould use the spec in iso 10646 on characters
> to be used for
> >> > > identifiers,
> >> > > > this is most likely the same as the unicode spec.
> >> > > >
> >> > > > keld
> >> > > >
> >> > > > On Sat, Nov 02, 2019 at 09:26:53AM +0100, Corentin wrote:
> >> > > > > Hello.
> >> > > > > Attached to SG-7, SG-16 and at this link
> >> > > > > https://isocpp.org/files/papers/D1953R0.pdf is a late
> paper (mostly
> >> > > > > targeting the hallway track) about the impact of
> Unicode identifiers
> >> > > on the
> >> > > > > reflection proposals
> >> > > > >
> >> > > > > Regards,
> >> > > > >
> >> > > > > Corentin
> >> > > >
> >> > > > > _______________________________________________
> >> > > > > SG16 Unicode mailing list
> >> > > > > Unicode_at_[hidden]
> <mailto:Unicode_at_[hidden]>
> >> > > > > http://www.open-std.org/mailman/listinfo/unicode
> >> > > >
> >> > > > _______________________________________________
> >> > > > SG16 Unicode mailing list
> >> > > > Unicode_at_[hidden]
> <mailto:Unicode_at_[hidden]>
> >> > > > http://www.open-std.org/mailman/listinfo/unicode
> >> > > _______________________________________________
> >> > > SG16 Unicode mailing list
> >> > > Unicode_at_[hidden]
> <mailto:Unicode_at_[hidden]>
> >> > > http://www.open-std.org/mailman/listinfo/unicode
> >> > >
> >> --
> >> SG16 mailing list
> >> SG16_at_[hidden] <mailto:SG16_at_[hidden]>
> >> https://lists.isocpp.org/mailman/listinfo.cgi/sg16
> >> --
> >> SG16 mailing list
> >> SG16_at_[hidden] <mailto:SG16_at_[hidden]>
> >> https://lists.isocpp.org/mailman/listinfo.cgi/sg16
> >>
> >
> >
> >
> > --
> > SG16 mailing list
> > SG16_at_[hidden] <mailto:SG16_at_[hidden]>
> > https://lists.isocpp.org/mailman/listinfo.cgi/sg16
>
> --
> SG16 mailing list
> SG16_at_[hidden] <mailto:SG16_at_[hidden]>
> https://lists.isocpp.org/mailman/listinfo.cgi/sg16
>
>