/[cmucl]/src/i18n/NormalizationCorrections.txt
ViewVC logotype

Contents of /src/i18n/NormalizationCorrections.txt

Parent Directory Parent Directory | Revision Log Revision Log


Revision 1.4 - (show annotations)
Mon Jun 27 15:11:29 2011 UTC (2 years, 9 months ago) by rtoy
Branch: MAIN
CVS Tags: GIT-CONVERSION, snapshot-2011-09, snapshot-2011-07, HEAD
Changes since 1.3: +3 -3 lines
File MIME type: text/plain
Update to Unicode 6.0.0.


code/unidata.lisp:
o Update unicode version to 6.0.0
o Add pointer to build-unidata.lisp.
tools/build-unidata.lisp:
o Update unicode version to 6.0.0
o Print out directory path so we can see where we're getting the data
  from.


i18n/CaseFolding.txt
i18n/CompositionExclusions.txt
i18n/DerivedNormalizationProps.txt
i18n/NameAliases.txt
i18n/NormalizationCorrections.txt
i18n/SpecialCasing.txt
i18n/UnicodeData.txt
i18n/WordBreakProperty.txt
i18n/tests/NormalizationTest.txt
i18n/tests/WordBreakTest.txt:
o Update with new files from unicode.org.
1 # NormalizationCorrections-6.0.0.txt
2 # Date: 2010-05-19, 11:21:00 PDT [KW]
3 #
4 # This file is a normative contributory data file in the
5 # Unicode Character Database.
6 #
7 # Copyright (c) 1991-2010 Unicode, Inc.
8 # For terms of use, see http://www.unicode.org/terms_of_use.html
9 #
10 # The normalization stabilization policy of the Unicode
11 # Consortium ordinarily precludes any change to the decomposition
12 # for any character, once established in a relevant version
13 # of the UnicodeData.txt data file. However, under certain
14 # exceptional (and rare) conditions, an error in a decomposition
15 # mapping may be discovered that is truly just an unintended
16 # typo in the data, and not a matter of dubious interpretation.
17 #
18 # Whenever such an error may be found, and if it meets the
19 # requirements for possible exceptions to normalization
20 # stability, the correction is entered in this data file,
21 # so that any implementation depending on absolute stability
22 # of normalization, *including* any errors in the data, can
23 # safely reconstruct the exact state of the data tables at
24 # any given version of Unicode.
25 #
26 # Currently this list has exactly six entries in it, one for the
27 # typo found and corrected in Corrigendum #3, and five for
28 # the typos and misidentifications found and corrected in
29 # Corrigendum #4. All efforts
30 # will be made to keep the entries limited to just those fixes.
31 #
32 # Interpretation of the fields:
33 # Field 0: Unicode code point
34 # Field 1: Original (erroneous) decomposition
35 # Field 2: Corrected decomposition
36 # Field 3: Version of Unicode for which the correction was
37 # entered into UnicodeData.txt, in n.n.n format.
38 # Comment: Indicates the Unicode Corrigendum which documents
39 # the correction
40 #
41 # For more information, see UAX #15, Unicode Normalization Forms.
42 #
43 F951;96FB;964B;3.2.0 # Corrigendum 3
44 2F868;2136A;36FC;4.0.0 # Corrigendum 4
45 2F874;5F33;5F53;4.0.0 # Corrigendum 4
46 2F91F;43AB;243AB;4.0.0 # Corrigendum 4
47 2F95F;7AAE;7AEE;4.0.0 # Corrigendum 4
48 2F9BF;4D57;45D7;4.0.0 # Corrigendum 4

  ViewVC Help
Powered by ViewVC 1.1.5