On 3/24/20 3:37 PM, Corentin wrote:
>
>
> On Tue, 24 Mar 2020 at 18:58, Hubert Tong
> <hubert.reinterpretcast_at_[hidden]
> <mailto:hubert.reinterpretcast_at_[hidden]>> wrote:
>
> On Tue, Mar 24, 2020 at 1:41 PM Tom Honermann via SG16
> <sg16_at_[hidden] <mailto:sg16_at_[hidden]>> wrote:
>
> On 3/24/20 10:36 AM, keld--- via SG16 wrote:
> > thee is already an iso std for this namely iso 15897.
> > it is posix compatible and compatible with c and c++
> >
> > and it is compatible with the iana registry, made by some of
> the same people
>
> Keld, I don't understand this reference. From what I can
> tell, ISO
> 15897 doesn't specify a set of encoding names. What we're
> looking for
> is a set of names to use to refer to specific encodings.
>
> http://std.dkuug.dk/cultreg/registrations/chreg.htm
> The "charmap" entries look to be what is being referred to.
>
>
> Please note the incompleteness of this list

I think it would be helpful for a revision of P1885 to list these
additional name sources and to identify the disjunctive union of their
members.

Tom.

>
>
> Tom.
>
> >
> > keld
> >
> >
> > On Tue, Mar 24, 2020 at 10:25:57AM +0000, Peter Brett via
> SG16 wrote:
> >> Hi Corentin,
> >>
> >> Thanks for replying so promptly! I personally agree that
> there is nothing more suitable available.
> >>
> >> One of the suggestions that was made in the UK national
> body meeting was that there could be an International Standard
> nomenclature for text encodings, possibly as part of the
> Unicode effort. Do you think that it would be useful?
> >>
> >> Peter
> >>
> >> From: Corentin <corentin.jabot_at_[hidden]
> <mailto:corentin.jabot_at_[hidden]>>
> >> Sent: 24 March 2020 09:35
> >> To: Peter Brett <pbrett_at_[hidden]
> <mailto:pbrett_at_[hidden]>>
> >> Cc: sg16_at_[hidden] <mailto:sg16_at_[hidden]>;
> Roger Orr <rogero_at_[hidden]
> <mailto:rogero_at_[hidden]>>;
> guy_at_[hidden] <mailto:guy_at_[hidden]>
> >> Subject: Re: UK national body concerns about P1885R1
> 'Naming Text Encodings to Demystify Them'
> >>
> >> EXTERNAL MAIL
> >> Hey!
> >> Thanks for your feedback
> >>
> >> A few things:
> >>
> >> * It does not evolve a lot (Neither the database nor the
> proposal are forward looking - RFC3808 is from 2004)
> >> * There is nothing more complete (or more official)
> >> * It has vendor buy in (form Microsoft and IBM for which it
> maps to their code page), the same names are also used by
> iconv on unix system
> >> * It is widely used by browsers, mail clients
> >> * We have experience with referencing rfc in the standards.
> >> * If this is still a concern, we could duplicate the entire
> thing in the standard - which I would recommend against.
> >>
> >> That standard registry is pivotal to the proposal
> portability. we need to agree on names and meaning.
> >>
> >> I hope that helps,
> >>
> >> Regards,
> >> Corentin
> >>
> >>
> >> On Tue, 24 Mar 2020 at 09:26, Peter Brett
> <pbrett_at_[hidden]
> <mailto:pbrett_at_[hidden]><mailto:pbrett_at_[hidden]
> <mailto:pbrett_at_[hidden]>>> wrote:
> >> Hi Corentin and SG16,
> >>
> >> We discussed P1885R1 briefly in the British Standards
> Institute meeting yesterday.
> >>
> >> We support the general direction of the paper and agree
> that it seeks to solve a real problem. We support further work.
> >>
> >> We have significant concerns about the proposal to rely on
> the IANA registry and RFC2978/RFC3808 process, including a
> normative reference to the Character Sets database. The
> Character Sets database is not an International Standard and
> is maintained by a process that appears to provide neither the
> quality assurance nor the checks and balances built into the
> ISO process.
> >>
> >> Best regards,
> >>
> >> Peter
> >> --
> >> 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
>