Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Commit eb324a3

Browse files
markusicumarkusicu
authored
Unicode 15.1 version numbers (#340)
1 parent fcd638a commit eb324a3

File tree

15 files changed

+92
-22
lines changed

15 files changed

+92
-22
lines changed

‎.github/workflows/build-jsp.yml

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -43,16 +43,16 @@ jobs:
4343
run: >
4444
mkdir -pv $(pwd)/output/Generated/ &&
4545
mvn -s .github/workflows/mvn-settings.xml -B exec:java
46-
-Dexec.mainClass="org.unicode.text.UCD.Main" -Dexec.args="version 15.0.0 build MakeUnicodeFiles"
46+
-Dexec.mainClass="org.unicode.text.UCD.Main" -Dexec.args="version 15.1.0 build MakeUnicodeFiles"
4747
-pl unicodetools -DCLDR_DIR=${GITHUB_WORKSPACE}/cldr
48-
-DUNICODETOOLS_REPO_DIR=$(pwd) -DUVERSION=15.0.0
48+
-DUNICODETOOLS_REPO_DIR=$(pwd) -DUVERSION=15.1.0
4949
-DUNICODETOOLS_GEN_DIR=$(pwd)/output/Generated
5050
env:
5151
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
5252
- name: Run unicodetools tests
5353
run: >
5454
mvn -s .github/workflows/mvn-settings.xml -B test -pl unicodetools
55-
-DCLDR_DIR=${GITHUB_WORKSPACE}/cldr -T 1C -Dparallel=classes -DUNICODETOOLS_REPO_DIR=$(pwd) -DUVERSION=15.0.0 -DUNICODETOOLS_GEN_DIR=$(pwd)/output/Generated
55+
-DCLDR_DIR=${GITHUB_WORKSPACE}/cldr -T 1C -Dparallel=classes -DUNICODETOOLS_REPO_DIR=$(pwd) -DUVERSION=15.1.0 -DUNICODETOOLS_GEN_DIR=$(pwd)/output/Generated
5656
env:
5757
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
5858
- name: Package JSPs

‎.github/workflows/cli-build-instructions.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -9,8 +9,8 @@ on:
99
- '*'
1010

1111
env:
12-
CURRENT_UVERSION: 15.0.0
13-
PREVIOUS_UVERSION: 14.0.0
12+
CURRENT_UVERSION: 15.1.0
13+
PREVIOUS_UVERSION: 15.0.0
1414

1515
jobs:
1616

‎unicodetools/data/ucd/dev/PropertyValueAliases.txt

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
1-
# PropertyValueAliases-15.0.0.txt
2-
# Date: 2022-08-05, 23:42:17 GMT
1+
# PropertyValueAliases-15.1.0.txt
2+
# Date: 2022-09-30
33
# © 2022 Unicode®, Inc.
44
# Unicode and the Unicode Logo are registered trademarks of Unicode, Inc. in the U.S. and other countries.
55
# For terms of use, see https://www.unicode.org/terms_of_use.html
@@ -91,6 +91,7 @@ age; 12.1 ; V12_1
9191
age; 13.0 ; V13_0
9292
age; 14.0 ; V14_0
9393
age; 15.0 ; V15_0
94+
age; 15.1 ; V15_1
9495
age; NA ; Unassigned
9596

9697
# Alphabetic (Alpha)

‎unicodetools/data/ucd/dev/auxiliary/GraphemeBreakTest.html

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,8 +6,8 @@
66
</style></head>
77
<body bgcolor='#FFFFFF'>
88
<h2>Grapheme_Cluster_Break Chart</h2>
9-
<p><b>Unicode Version:</b> 15.0.0</p>
10-
<p><b>Date:</b> 2021-11-24, 21:43:39 GMT</p>
9+
<p><b>Unicode Version:</b> 15.1.0</p>
10+
<p><b>Date:</b> 2022-10-05, 16:37:09 GMT</p>
1111
<p>This page illustrates the application of the Grapheme_Cluster_Break specification. The material here is informative, not normative.</p> <p>The first chart shows where breaks would appear between different sample characters or strings. The sample characters are chosen mechanically to represent the different properties used by the specification.</p><p>Each cell shows the break-status for the position between the character(s) in its row header and the character(s) in its column header. The × symbol indicates no break, while the ÷ symbol indicated a break. The cells with × are also shaded to make it easier to scan the table. For example, in the cell at the intersection of the row headed by “CR” and the column headed by “LF”, there is a × symbol, indicating that there is no break between CR and LF.</p>
1212
<p>After the heavy blue line in the table are additional rows, either with different sample characters or for sequences. Some column headers may be composed, reflecting “treat as” or “ignore” rules.</p>
1313
<p>If your browser handles titles (tooltips), then hovering the mouse over the row header will show a sample character of that type. Hovering over a column header will show the sample character, plus its abbreviated general category and script. Hovering over the intersected cells shows the rule number that produces the break-status. For example, hovering over the cell at the intersection of LVT and T shows ×, with the rule 8.0. Checking below the table, rule 8.0 is “( LVT | T) × T”, which is the one that applies to that case. Note that a rule is invoked only when no lower-numbered rules have applied.</p>

‎unicodetools/data/ucd/dev/auxiliary/LineBreakTest.html

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,8 +6,8 @@
66
</style></head>
77
<body bgcolor='#FFFFFF'>
88
<h2>Line_Break Chart</h2>
9-
<p><b>Unicode Version:</b> 15.0.0</p>
10-
<p><b>Date:</b> 2021-11-24, 21:43:40 GMT</p>
9+
<p><b>Unicode Version:</b> 15.1.0</p>
10+
<p><b>Date:</b> 2022-10-05, 16:37:11 GMT</p>
1111
<p>This page illustrates the application of the Line_Break specification. The material here is informative, not normative.</p> <p>The first chart shows where breaks would appear between different sample characters or strings. The sample characters are chosen mechanically to represent the different properties used by the specification.</p><p>Each cell shows the break-status for the position between the character(s) in its row header and the character(s) in its column header. The × symbol indicates no break, while the ÷ symbol indicated a break. The cells with × are also shaded to make it easier to scan the table. For example, in the cell at the intersection of the row headed by “CR” and the column headed by “LF”, there is a × symbol, indicating that there is no break between CR and LF.</p>
1212
<p>Some column headers may be composed, reflecting “treat as” or “ignore” rules.</p>
1313
<p>If your browser handles titles (tooltips), then hovering the mouse over the row header will show a sample character of that type. Hovering over a column header will show the sample character, plus its abbreviated general category and script. Hovering over the intersected cells shows the rule number that produces the break-status. For example, hovering over the cell at the intersection of H3 and JT shows ×, with the rule 26.03. Checking below the table, rule 26.03 is “JT | H3 × JT”, which is the one that applies to that case. Note that a rule is invoked only when no lower-numbered rules have applied.</p>

‎unicodetools/data/ucd/dev/auxiliary/SentenceBreakTest.html

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,8 +6,8 @@
66
</style></head>
77
<body bgcolor='#FFFFFF'>
88
<h2>Sentence_Break Chart</h2>
9-
<p><b>Unicode Version:</b> 15.0.0</p>
10-
<p><b>Date:</b> 2021-11-24, 21:43:58 GMT</p>
9+
<p><b>Unicode Version:</b> 15.1.0</p>
10+
<p><b>Date:</b> 2022-10-05, 16:37:36 GMT</p>
1111
<p>This page illustrates the application of the Sentence_Break specification. The material here is informative, not normative.</p> <p>The first chart shows where breaks would appear between different sample characters or strings. The sample characters are chosen mechanically to represent the different properties used by the specification.</p><p>Each cell shows the break-status for the position between the character(s) in its row header and the character(s) in its column header. The × symbol indicates no break, while the ÷ symbol indicated a break. The cells with × are also shaded to make it easier to scan the table. For example, in the cell at the intersection of the row headed by “CR” and the column headed by “LF”, there is a × symbol, indicating that there is no break between CR and LF.</p>
1212
<p>Some column headers may be composed, reflecting “treat as” or “ignore” rules.</p>
1313
<p>If your browser handles titles (tooltips), then hovering the mouse over the row header will show a sample character of that type. Hovering over a column header will show the sample character, plus its abbreviated general category and script. Hovering over the intersected cells shows the rule number that produces the break-status. For example, hovering over the cell at the intersection of ATerm and Close shows ×, with the rule 9.0. Checking below the table, rule 9.0 is “SATerm Close* × ( Close | Sp | ParaSep )”, which is the one that applies to that case. Note that a rule is invoked only when no lower-numbered rules have applied.</p>

‎unicodetools/data/ucd/dev/auxiliary/WordBreakTest.html

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,8 +6,8 @@
66
</style></head>
77
<body bgcolor='#FFFFFF'>
88
<h2>Word_Break Chart</h2>
9-
<p><b>Unicode Version:</b> 15.0.0</p>
10-
<p><b>Date:</b> 2021-11-24, 21:43:58 GMT</p>
9+
<p><b>Unicode Version:</b> 15.1.0</p>
10+
<p><b>Date:</b> 2022-10-05, 16:37:36 GMT</p>
1111
<p>This page illustrates the application of the Word_Break specification. The material here is informative, not normative.</p> <p>The first chart shows where breaks would appear between different sample characters or strings. The sample characters are chosen mechanically to represent the different properties used by the specification.</p><p>Each cell shows the break-status for the position between the character(s) in its row header and the character(s) in its column header. The × symbol indicates no break, while the ÷ symbol indicated a break. The cells with × are also shaded to make it easier to scan the table. For example, in the cell at the intersection of the row headed by “CR” and the column headed by “LF”, there is a × symbol, indicating that there is no break between CR and LF.</p>
1212
<p>After the heavy blue line in the table are additional rows, either with different sample characters or for sequences, such as “ALetter MidLetter”. Some column headers may be composed, reflecting “treat as” or “ignore” rules.</p>
1313
<p>If your browser handles titles (tooltips), then hovering the mouse over the row header will show a sample character of that type. Hovering over a column header will show the sample character, plus its abbreviated general category and script. Hovering over the intersected cells shows the rule number that produces the break-status. For example, hovering over the cell at the intersection of ExtendNumLet and ALetter shows ×, with the rule 13.2. Checking below the table, rule 13.2 is “ExtendNumLet × (AHLetter | Numeric | Katakana)”, which is the one that applies to that case. Note that a rule is invoked only when no lower-numbered rules have applied.</p>

‎unicodetools/src/main/java/org/unicode/idna/GenerateIdnaTest.java

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -177,7 +177,7 @@ int generateTests(int lines) throws IOException {
177177
// See https://github.com/unicode-org/unicodetools/issues/100 "Whither 13.1.0?"
178178
lastVersion = "13.0.0";
179179
}
180-
int ucdTypesLastVersion = UCD_Types.AGE140;
180+
int ucdTypesLastVersion = UCD_Types.AGE150;
181181
String ucdTypesLastVersionString = UCD_Types.AGE_VERSIONS[ucdTypesLastVersion];
182182
if (!ucdTypesLastVersionString.equals(lastVersion)) {
183183
throw new AssertionError(

‎unicodetools/src/main/java/org/unicode/props/GenerateEnums.java

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -213,11 +213,13 @@ public static String getNameStuff2(final String enumName) {
213213
+ enumName
214214
+ ".class, this, shortName, otherNames);\n"
215215
+ " }\n"
216+
+ " @Override\n"
216217
+ " public PropertyNames<"
217218
+ enumName
218219
+ "> getNames() {\n"
219220
+ " return names;\n"
220221
+ " }\n"
222+
+ " @Override\n"
221223
+ " public String getShortName() {\n"
222224
+ " return names.getShortName();\n"
223225
+ " }\n"

0 commit comments

Comments
 (0)