-# NamedSequencesProv-6.3.0.txt
-# Date: 2013-01-02, 08:37:00 GMT [KW]
+# NamedSequencesProv-7.0.0.txt
+# Date: 2014-01-24, 15:00:00 GMT [KW, LI]
#
-# Unicode Character Database
-# Copyright (c) 1991-2013 Unicode, Inc.
-# For terms of use, see http://www.unicode.org/terms_of_use.html
-# For documentation, see http://www.unicode.org/reports/tr44/
+# Provisional Unicode Named Character Sequences
#
-# Provisional Named Sequences
-# Note: This data file contains those named
+# Note: This data file contains those named character
# sequences which have been designated to be provisional,
# rather than fully approved.
#
+# Copyright (c) 1991-2014 Unicode, Inc.
+# For terms of use, see http://www.unicode.org/terms_of_use.html
+#
# Format:
# Name of Sequence; Code Point Sequence for USI
#
-# Code point sequences in the UCD use spaces as delimiters.
-# The corresponding format for a USI in ISO/IEC 10646 uses
-# comma delimitation and angle brackets. Thus, a named sequence
-# of the form:
+# Code point sequences in the Unicode Character Database
+# use spaces as delimiters. The corresponding format for a
+# UCS Sequence Identifier (USI) in ISO/IEC 10646 uses
+# comma delimitation and angle brackets. Thus, a Unicode
+# named character sequence of the form:
#
# EXAMPLE NAME;1000 1001 1002
#
-# in this data file, would correspond to a 10646 USI as follows:
+# in this data file, would correspond to an ISO/IEC 10646 USI
+# as follows:
#
# <1000, 1001, 1002>
#
+# For more information, see UAX #34: Unicode Named Character
+# Sequences, at http://www.unicode.org/unicode/reports/tr34/
+#
# Note: The order of entries in this file is not significant.
# However, entries are generally in script order corresponding
# to block order in the Unicode Standard, to make it easier
# Provisional entries for NamedSequences.txt.
-# There are currently no provisional named sequences.
+# There are currently no provisional named character sequences.
# ================================================