all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: David De La Harpe Golden <david@harpegolden.net>
Cc: emacs-devel@gnu.org
Subject: Re: Unicode 9.0
Date: Thu, 17 Mar 2016 05:42:03 +0200	[thread overview]
Message-ID: <83egb9ahys.fsf@gnu.org> (raw)
In-Reply-To: <56EA1D0B.4060101@harpegolden.net> (message from David De La Harpe Golden on Thu, 17 Mar 2016 02:57:15 +0000)

> From: David De La Harpe Golden <david@harpegolden.net>
> Date: Thu, 17 Mar 2016 02:57:15 +0000
> 
> This may well be something that was going without saying, but just in 
> case / to be pernickety, there's a specific warning on the beta 9 page:
> 
> http://unicode.org/versions/beta-9.0.0.html
> """
> No products or implementations should be released based on the beta UCD 
> data files—use only the final, approved Version 9.0.0 data files, 
> expected in June 2016.
> """
> 
> It is also stated there they have already frozen the code point and 
> character names, and to be honest I haven't even looked at what's new in 
> 9 in any depth. In practice there may well not be any more changes 
> before finalisation of 9, whether emacs-significant changes or otherwise.
> 
> And I'm _not_ objecting to the recent update (a761fbf2) of the files to 
> beta 9 in git for a shakedown during pretest, which I think was what Eli 
> meant anyway, but that's still distinct from an emacs official versioned 
> release tarball.
> 
> I just mean (and this very probably won't even arise in the end): at 
> some future time close to the emacs release, if for some reason unicode 
> 9 still isn't officially final yet, and if for some reason you don't 
> want to delay the emacs release a bit to wait for it... the official 
> emacs release should probably be made with older final definitions, not 
> any beta ones.

I don't see why we should refrain from using the beta files in the
release, if they don't release the official Unicode 9.0 by the time we
are ready.  No reason whatsoever.



      reply	other threads:[~2016-03-17  3:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-11 19:36 Unicode 9.0 Eli Zaretskii
2016-03-11 21:29 ` John Wiegley
2016-03-11 22:01   ` Paul Eggert
2016-03-12 15:53     ` Eli Zaretskii
2016-03-17  2:57       ` David De La Harpe Golden
2016-03-17  3:42         ` Eli Zaretskii [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83egb9ahys.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=david@harpegolden.net \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.