summaryrefslogtreecommitdiff
path: root/Admin/README.update
diff options
context:
space:
mode:
authorBruno Haible <bruno@clisp.org>2021-12-31 19:41:25 +0100
committerBruno Haible <bruno@clisp.org>2021-12-31 19:41:25 +0100
commita051c863a4d82ccad43f28a985bfcc4e30c9dfce (patch)
tree33aab4cf78660240be987fdc2e2995c035d15568 /Admin/README.update
parenta61e78d8edc1beeeeb0c0818eb96ca8d09592296 (diff)
downloadlibunistring-a051c863a4d82ccad43f28a985bfcc4e30c9dfce.tar.gz
Update maintainer instructions and scripts.
Diffstat (limited to 'Admin/README.update')
-rw-r--r--Admin/README.update18
1 files changed, 13 insertions, 5 deletions
diff --git a/Admin/README.update b/Admin/README.update
index 8d50baf..dc8ebd8 100644
--- a/Admin/README.update
+++ b/Admin/README.update
@@ -13,14 +13,22 @@ environment variables
- UCD, which points to the directory containing the Unicode UCD
Before updating, read the Unicode release note carefully and
-understand any changes that might affect Gnulib. In particular,
-changes in the text segmentation algorithms (provided by unilbrk.h,
-uniwbrk.h, unigbrk.h) often require manual adjustment of source files.
-
-The release notes are typically available at:
+understand any changes that might affect Gnulib. The release notes are
+typically available at:
https://unicode.org/versions/Unicode<VERSION>/
+In particular, changes in the text segmentation algorithms often
+require manual adjustment of source files:
+
+ - For unigbrk/ updates, look at the revision history of UAX #29
+ <https://www.unicode.org/reports/tr29/>, section 3.
+ - For uniwbrk/ updates, look at the revision history of UAX #29
+ <https://www.unicode.org/reports/tr29/>, section 4.
+ - For unilbrk/ updates, look at the revision history of UAX #14
+ <https://www.unicode.org/reports/tr14/>.
+
+
* Regenerating the Gnulib source code
The source files in Gnulib are updated using a couple of tools: