organicmaps/icu
13
Fork 0
mirror of https://github.com/unicode-org/icu.git synced 2025-04-05 21:45:37 +00:00
Code Issues 1 Projects Releases Wiki Activity Actions 12

ICU-21508 Rename 'master' to 'main' in docs, maven files, scripts, etc

Browse source 
See #1664
This commit is contained in:
Hugo van der Merwe 2021-03-23 01:23:36 +00:00
parent 227c729b0e
commit 0ad4614a04
58 changed files with 202 additions and 202 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
.ci-builds/.azure-exhaustive-tests.yml
View file

@ -3,14 +3,14 @@
# Note: The exhaustive test configuration is in a separate file
# so that it can be run independently from the regular builds.
#
# Only run the exhaustive tests on the master and maint branches, and
# Only run the exhaustive tests on the main and maint branches, and
# also batch up any pending changes so that we will only have at most
# one build running at a given time (since they take a long time).
trigger:
batch: true
branches:
include:
- master
- main
- maint/maint-*
paths:
include:

4
.ci-builds/.azure-valgrind.yml
View file

@ -6,14 +6,14 @@
# The Ubuntu images don't have valgrind installed by default, so we need
# install it first.
#
# Only run valgrind on the master and maint branches, and
# Only run valgrind on the main and maint branches, and
# batch up any pending changes so that we will only have at most
# one build running at a given time (since it takes time).
trigger:
batch: true
branches:
include:
- master
- main
- maint/maint-*
paths:
include:

2
.github/workflows/icu_ci.yml vendored
View file

@ -8,7 +8,7 @@ name: GHA CI
on:
push:
branches:
- master
- main
- 'maint/maint*'
pull_request:
branches: '**'

12
README.md
View file

@ -11,17 +11,17 @@ The ICU project is under the stewardship of [The Unicode Consortium](https://www
![ICU Logo](./tools/images/iculogo_64.png)
### 🔴🔴🔴 Special Notice About Branch Renaming 🔴🔴🔴
We plan to rename the `master` branch to `main` branch around March 24-25, 2021. You may need to rename your branch in your local git repo and change your normal git command to reflect the changes after that. See also https://github.com/github/renaming
Around March 24-25, 2021 we renamed the `master` branch to `main`. You may need to rename your branch in your local git repo and change your normal git command to reflect this change. See also https://github.com/github/renaming
### Build Status (`master` branch)
### Build Status (`main` branch)
Build | Status
------|-------
GitHub Actions | [![GHA CI](https://github.com/unicode-org/icu/workflows/GHA%20CI/badge.svg)](https://github.com/unicode-org/icu/actions?query=workflow%3A%22GHA+CI%22)
Azure Pipelines | [![Build Status](https://dev.azure.com/ms/icu/_apis/build/status/unicode-org/CI?branchName=master)](https://dev.azure.com/ms/icu/_build/latest?definitionId=360&branchName=master)
Azure Pipelines (Exhaustive Tests) | [![Build Status](https://dev.azure.com/ms/icu/_apis/build/status/unicode-org/CI-Exhaustive-Main?branchName=master)](https://dev.azure.com/ms/icu/_build/latest?definitionId=361&branchName=master)
Azure Pipelines (Valgrind ICU4C) | [![Build Status](https://dev.azure.com/ms/icu/_apis/build/status/unicode-org/CI-Valgrind-Main?branchName=master)](https://dev.azure.com/ms/icu/_build/latest?definitionId=362&branchName=master)
AppVeyor | [![Build status](https://ci.appveyor.com/api/projects/status/6ev1ssb6efahsvs2/branch/master?svg=true)](https://ci.appveyor.com/project/unicode-org/icu/branch/master)
Azure Pipelines | [![Build Status](https://dev.azure.com/ms/icu/_apis/build/status/unicode-org/CI?branchName=main)](https://dev.azure.com/ms/icu/_build/latest?definitionId=360&branchName=main)
Azure Pipelines (Exhaustive Tests) | [![Build Status](https://dev.azure.com/ms/icu/_apis/build/status/unicode-org/CI-Exhaustive-Main?branchName=main)](https://dev.azure.com/ms/icu/_build/latest?definitionId=361&branchName=main)
Azure Pipelines (Valgrind ICU4C) | [![Build Status](https://dev.azure.com/ms/icu/_apis/build/status/unicode-org/CI-Valgrind-Main?branchName=main)](https://dev.azure.com/ms/icu/_build/latest?definitionId=362&branchName=main)
AppVeyor | [![Build status](https://ci.appveyor.com/api/projects/status/6ev1ssb6efahsvs2/branch/main?svg=true)](https://ci.appveyor.com/project/unicode-org/icu/branch/main)
Fuzzing | [![Fuzzing Status](https://oss-fuzz-build-logs.storage.googleapis.com/badges/icu.svg)](https://bugs.chromium.org/p/oss-fuzz/issues/list?sort=-opened&can=1&q=proj:icu)

2
docs/_config.yml
View file

@ -83,7 +83,7 @@ gh_edit_link_text: "Edit this page on GitHub."
gh_edit_repository: "https://github.com/unicode-org/icu"
# NOTE: Since we serve the docs out of the "docs" folder, we need to include that here even though
# it is technically *not* part of the branch name.
gh_edit_branch: "master/docs"
gh_edit_branch: "main/docs"
# Can be "tree" or "edit". Edit takes the user to jump into the editor immediately.
gh_edit_view_mode: "tree"

2
docs/index.md
View file

@ -12,7 +12,7 @@ License & terms of use: http://www.unicode.org/copyright.html
# ICU Documentation
[![ICU logo](https://github.com/unicode-org/icu-docs/raw/master/img/iculogo_64.png)](http://site.icu-project.org/)
[![ICU logo](https://github.com/unicode-org/icu-docs/raw/main/img/iculogo_64.png)](http://site.icu-project.org/)
## ICU User Guide

10
docs/processes/fuzzer_targets.md
View file

@ -12,7 +12,7 @@ target for an ICU API and its integration into the ICU build process.
### Directory and naming conventions
Fuzzer targets are exclusively in directory
[`source/test/fuzzer/`](https://github.com/unicode-org/icu/tree/master/icu4c/source/test/fuzzer)
[`source/test/fuzzer/`](https://github.com/unicode-org/icu/tree/main/icu4c/source/test/fuzzer)
and end with `_fuzzer.cpp`. Only files with such ending are recognized and executed as fuzzer
targets by the OSS-Fuzz system.
@ -32,7 +32,7 @@ fuzzer-controlled data of size `size` bytes. Part or all of this data is then pa
ICU API under test.
Fuzzer target
[`collator_rulebased_fuzzer.cpp`](https://github.com/unicode-org/icu/blob/master/icu4c/source/test/fuzzer/collator_rulebased_fuzzer.cpp)
[`collator_rulebased_fuzzer.cpp`](https://github.com/unicode-org/icu/blob/main/icu4c/source/test/fuzzer/collator_rulebased_fuzzer.cpp)
illustrates the basic elements.
```
@ -76,7 +76,7 @@ to assure that the code is syntactically correct and, as a sanity check, execute
manner, i.e. with minimal testdata and without ASAN or MSAN analysis.
Add the new fuzzer target to the list of targets in the `FUZZER_TARGETS` variable in
[`Makefile.in`](https://github.com/unicode-org/icu/blob/master/icu4c/source/test/fuzzer/Makefile.in).
[`Makefile.in`](https://github.com/unicode-org/icu/blob/main/icu4c/source/test/fuzzer/Makefile.in).
The new fuzzer target will then be built and executed as part of a normal ICU4C unit test run. Note
that each fuzzer target becomes executable on its own. As such it is linked with the code in
`fuzzer_driver.cpp`, which contains the `main()` function.
@ -86,13 +86,13 @@ that each fuzzer target becomes executable on its own. As such it is linked with
Any fuzzer seed data for a fuzzer target goes into a file with name `<fuzzer_target>_seed_corpus.txt`.
In many cases the input parameter of the ICU API under test is of type `UnicodeString`, in case
of which the seed data should be in UTF-16 format. As an example,see
[collator_rulebased_fuzzer_seed_corpus.txt](https://github.com/unicode-org/icu/blob/master/icu4c/source/test/fuzzer/collator_rulebased_fuzzer_seed_corpus.txt).
[collator_rulebased_fuzzer_seed_corpus.txt](https://github.com/unicode-org/icu/blob/main/icu4c/source/test/fuzzer/collator_rulebased_fuzzer_seed_corpus.txt).
### Guidelines and tips
* Leave all randomness to the fuzzer. If a random selection of any kind is needed (e.g., of a
locale), then use bytes from the fuzzer data to make the selection
([example](https://github.com/unicode-org/icu/blob/master/icu4c/source/test/fuzzer/break_iterator_fuzzer.cpp)).
([example](https://github.com/unicode-org/icu/blob/main/icu4c/source/test/fuzzer/break_iterator_fuzzer.cpp)).
* In many cases ICU unit tests can provide seed data or at least ideas for seed data. If the API
under test requires a Unicode string then make sure that the seed data is in UTF-16 encoding.
This can be achieved with e.g. the 'iconv' command or using an editor that saves text in UTF-16.

2
docs/processes/release/tasks/updating-measure-unit.md
View file

@ -115,7 +115,7 @@ will be considered new for the next release too.
## Updating units.txt and unitConstants
The standard ldml2icu process is used to update ICU's resource files (see
[cldr-icu-readme.txt](https://github.com/unicode-org/icu/blob/master/icu4c/source/data/cldr-icu-readme.txt)).
[cldr-icu-readme.txt](https://github.com/unicode-org/icu/blob/main/icu4c/source/data/cldr-icu-readme.txt)).
CLDR's units.xml defines conversion rates in terms of some constants defined in
`unitConstants`.

4
docs/processes/rules_update.md
View file

@ -17,7 +17,7 @@ This is not a cook book process. Familiarity with ICU break iterator behavior an
The changes will typically come from a proposed update to Unicode UAX 29 or UAX 14,
or from CLDR based tailorings to these specifications.
As an example, see [CLDR proposal for Extended Indic Grapheme Clusters](https://github.com/unicode-org/cldr/tree/master/common/properties/segments).
As an example, see [CLDR proposal for Extended Indic Grapheme Clusters](https://github.com/unicode-org/cldr/tree/main/common/properties/segments).
Often ICU will implement draft versions of proposed specification updates, to check that they are complete and consistent, and to identify any issues before they are released.
@ -209,7 +209,7 @@ The rule updates are done first for ICU4C, and then ported (code changes) or mov
by this test have not yet been.
Make the updates to the test rules and re-run. The rule syntax is described in
[icu4c/source/test/testdata/break_rules/README.md](https://github.com/unicode-org/icu/blob/master/icu4c/source/test/testdata/break_rules/README.md)
[icu4c/source/test/testdata/break_rules/README.md](https://github.com/unicode-org/icu/blob/main/icu4c/source/test/testdata/break_rules/README.md)
The test reference rules are in this same directory.
Again, after everything appears to be working, let the test run for an extended length of time. Long runs are especially important with the more complex break rule sets, such as line break.

6
docs/userguide/boundaryanalysis/break-rules.md
View file

@ -35,7 +35,7 @@ ICU includes rules for the standard boundary types (word, line, etc.).
Applications may also create customized break iterators from their own rules.
ICU's built-in rules are located at
[icu/icu4c/source/data/brkitr/rules/](https://github.com/unicode-org/icu/tree/master/icu4c/source/data/brkitr/rules).
[icu/icu4c/source/data/brkitr/rules/](https://github.com/unicode-org/icu/tree/main/icu4c/source/data/brkitr/rules).
These can serve as examples when writing your own, and as starting point for
customizations.
@ -271,7 +271,7 @@ The dictionary implementation, on receiving a range of text, will map it to a
specific dictionary based on script, and then delegate to that dictionary for
subdividing the range into words.
See, for example, this snippet from the [line break rules](https://github.com/unicode-org/icu/blob/master/icu4c/source/data/brkitr/rules/line.txt):
See, for example, this snippet from the [line break rules](https://github.com/unicode-org/icu/blob/main/icu4c/source/data/brkitr/rules/line.txt):
```
# Dictionary character set, for triggering language-based break engines. Currently
@ -401,7 +401,7 @@ Here is the syntax for the boundary rules. (The EBNF Syntax is given below.)
## Additional Sample Code
**C/C++**
See [icu/source/samples/break/](https://github.com/unicode-org/icu/tree/master/icu4c/source/samples/break/)
See [icu/source/samples/break/](https://github.com/unicode-org/icu/tree/main/icu4c/source/samples/break/)
in the ICU source distribution for code samples showing the use of ICU boundary analysis.
## Details about Dictionary-Based Break Iteration

4
docs/userguide/boundaryanalysis/index.md
View file

@ -531,13 +531,13 @@ will generally be slower.
The source code for the ICU break rules for the standard boundary types is
located in the directory
[icu4c/source/data/brkitr/rules](https://github.com/unicode-org/icu/tree/master/icu4c/source/data/brkitr/rules).
[icu4c/source/data/brkitr/rules](https://github.com/unicode-org/icu/tree/main/icu4c/source/data/brkitr/rules).
These files will be built, and the corresponding binary state tables
incorporated into ICU's data, by the standard ICU4C build process.
The dictionary word lists used by word break, and for some languages, line break
are in
[icu4c/source/data/brkitr/dictionaries](https://github.com/unicode-org/icu/tree/master/icu4c/source/data/brkitr/dictionaries).
[icu4c/source/data/brkitr/dictionaries](https://github.com/unicode-org/icu/tree/main/icu4c/source/data/brkitr/dictionaries).
The same data is used by both ICU4C and ICU4J. In the normal ICU build process,
the source data is processed into a binary form using ICU4C, and the resulting

4
docs/userguide/collation/api.md
View file

@ -60,7 +60,7 @@ language tag syntax ("el-u-kf-upper"). Keywords and values are case-insensitive.
See the [LDML Collation spec, Collation
Settings](http://www.unicode.org/reports/tr35/tr35-collation.html#Collation_Settings),
and the [data
file](https://github.com/unicode-org/cldr/blob/master/common/bcp47/collation.xml) listing
file](https://github.com/unicode-org/cldr/blob/main/common/bcp47/collation.xml) listing
the valid collation keywords and their values. (The deprecated attributes
kh/colHiraganaQuaternary and vt/variableTop are not supported.)
@ -698,7 +698,7 @@ API is provided. Each attribute has its own setter API of the form
2. ICU Design doc: "Collation v2" (<http://site.icu-project.org/design/collation/v2>)
3. Mark Davis: "ICU Collation Design Document"
(<https://htmlpreview.github.io/?https://github.com/unicode-org/icu-docs/blob/master/design/collation/ICU_collation_design.htm>)
(<https://htmlpreview.github.io/?https://github.com/unicode-org/icu-docs/blob/main/design/collation/ICU_collation_design.htm>)
3. The Unicode Standard, chapter 5, "Implementation guidelines"
(<http://www.unicode.org/uni2book/ch05.pdf>)

2
docs/userguide/collation/customization/ignorepunct.md
View file

@ -48,7 +48,7 @@ See also
* [UCA: Variable
Weighting](http://www.unicode.org/reports/tr10/#Variable_Weighting)
* [LDML: Setting
Options](https://htmlpreview.github.io/?https://github.com/unicode-org/cldr/blob/master/docs/ldml/tr35-collation.html#Setting_Options)
Options](https://htmlpreview.github.io/?https://github.com/unicode-org/cldr/blob/main/docs/ldml/tr35-collation.html#Setting_Options)
Here is an overview of the sorting results with these options.

2
docs/userguide/collation/customization/index.md
View file

@ -1015,7 +1015,7 @@ UCARules:process(uca_rules){"../unidata/UCARules.txt"}
```
in
[source/data/coll/root.txt](https://github.com/unicode-org/icu/blob/master/icu4c/source/data/coll/root.txt)
[source/data/coll/root.txt](https://github.com/unicode-org/icu/blob/main/icu4c/source/data/coll/root.txt)
can be commented out or deleted.
## Cautions

2
docs/userguide/conversion/converters.md
View file

@ -832,4 +832,4 @@ target[targetsize] = 0; /* NULL termination */
## Conversion Examples
See the [ICU Conversion Examples](https://github.com/unicode-org/icu/blob/master/icu4c/source/samples/ucnv/convsamp.cpp) for more information.
See the [ICU Conversion Examples](https://github.com/unicode-org/icu/blob/main/icu4c/source/samples/ucnv/convsamp.cpp) for more information.

2
docs/userguide/conversion/data.md
View file

@ -529,7 +529,7 @@ all shared mappings should be in the base table. (The base table data structure
is more compact than the extension table data structure.)
ICU provides the ucmkbase tool in the
[ucmtools](https://github.com/unicode-org/icu-data/tree/master/charset/source/ucmtools)
[ucmtools](https://github.com/unicode-org/icu-data/tree/main/charset/source/ucmtools)
collection to do this.
For example, the following illustrates how to use ucmkbase to make a base .ucm

4
docs/userguide/conversion/index.md
View file

@ -136,7 +136,7 @@ Unicode.
together with a standard/platform name. This allows you to get different
converters for the same ambiguous charset name (like "Shift-JIS"),
depending on the standard or platform specified. See the
[convrtrs.txt](https://github.com/unicode-org/icu/blob/master/icu4c/source/data/mappings/convrtrs.txt)
[convrtrs.txt](https://github.com/unicode-org/icu/blob/main/icu4c/source/data/mappings/convrtrs.txt)
alias table, the [Using Converters](converters.md) chapter and [API
references](https://unicode-org.github.io/icu-docs/apidoc/released/icu4c/ucnv_8h.html) .
@ -147,7 +147,7 @@ Unicode.
"escape callback" function that turns unmappable Unicode code points
into corresponding escape sequences, preventing data loss. See the API
references and the [ucnv sample
code](https://github.com/unicode-org/icu/tree/master/icu4c/source/samples/ucnv/)
code](https://github.com/unicode-org/icu/tree/main/icu4c/source/samples/ucnv/)
.
9. **Never modify a conversion table.** Instead, use existing ones that

8
docs/userguide/datetime/timezone/index.md
View file

@ -148,7 +148,7 @@ The [ICU Data](../../icudata.md) section of this user guide gives more
information on how ICU loads resources.
The ICU resource files required for time zone data updates are posted at
<https://github.com/unicode-org/icu-data/tree/master/tzdata/icunew>. The
<https://github.com/unicode-org/icu-data/tree/main/tzdata/icunew>. The
required resource files for ICU version 44 and newer are
* zoneinfo64.res
@ -162,7 +162,7 @@ For ICU configurations that load data from a .dat package file, replace the time
zone resources in that file.
1. Download the new .res files from
`https://github.com/unicode-org/icu-data/tree/master/tzdata/icunew/<IANA tz version>/44/<platform directory>`.
`https://github.com/unicode-org/icu-data/tree/main/tzdata/icunew/<IANA tz version>/44/<platform directory>`.
* `<IANA tz version>` is a combination of year and letter, such as "2019c".
* *"44"* is the directory for updates to ICU version 4.4 and newer.
* `<platform directory>` is "le" for little endian processors, including
@ -228,7 +228,7 @@ the ICU data path.
1. Set up the environment necessary to rebuild your specific configuration of
ICU.
2. Download the .txt file sources for the updated resources from
`https://github.com/unicode-org/icu-data/tree/master/tzdata/icunew/<IANA tz version>/44`
`https://github.com/unicode-org/icu-data/tree/main/tzdata/icunew/<IANA tz version>/44`
3. Copy the downloaded .txt files into the ICU sources for your installation,
in the subdirectory source/data/misc/
4. Rebuid ICU.
@ -248,7 +248,7 @@ sources for general information on building ICU.
The [ICU4J Time Zone Update Update
Utility](http://site.icu-project.org/download/icutzu) automates the process of
updating ICU4J jar files with the latest time zone data. Instructions for use
are [here](https://htmlpreview.github.io/?https://github.com/unicode-org/icu-data/blob/master/tzdata/tzu/readme.html).
are [here](https://htmlpreview.github.io/?https://github.com/unicode-org/icu-data/blob/main/tzdata/tzu/readme.html).
The updater will work with ICU version 3.4.2 and newer.

2
docs/userguide/design.md
View file

@ -605,7 +605,7 @@ Here are some things to realize about the chart.
Starting with ICU 49, the dependencies of code files (.o files compiled from
.c/.cpp) are documented in
[source/test/depstest/dependencies.txt](https://github.com/unicode-org/icu/blob/master/icu4c/source/test/depstest/dependencies.txt).
[source/test/depstest/dependencies.txt](https://github.com/unicode-org/icu/blob/main/icu4c/source/test/depstest/dependencies.txt).
Adjacent Python code is used to parse this file and to
[verify](http://site.icu-project.org/processes/release/tasks/healthy-code#TOC-Check-library-dependencies)
that it matches the actual dependencies of the code files.

6
docs/userguide/dev/codingguidelines.md
View file

@ -1171,16 +1171,16 @@ pointers to owned memory must always be either NULL or point to owned objects.
Internally:
[cmemory.h](https://github.com/unicode-org/icu/blob/master/icu4c/source/common/cmemory.h)
[cmemory.h](https://github.com/unicode-org/icu/blob/main/icu4c/source/common/cmemory.h)
defines the `LocalMemory` class for chunks of memory of primitive types which
will be `uprv_free()`'ed.
[cmemory.h](https://github.com/unicode-org/icu/blob/master/icu4c/source/common/cmemory.h)
[cmemory.h](https://github.com/unicode-org/icu/blob/main/icu4c/source/common/cmemory.h)
also defines `MaybeStackArray` and `MaybeStackHeaderAndArray` which automate
management of arrays.
Use `CharString`
([charstr.h](https://github.com/unicode-org/icu/blob/master/icu4c/source/common/charstr.h))
([charstr.h](https://github.com/unicode-org/icu/blob/main/icu4c/source/common/charstr.h))
for `char *` strings that you build and modify.
#### Global Inline Functions

10
docs/userguide/dev/contributions.md
View file

@ -61,7 +61,7 @@ of the copyright assignment.
If you would like to make a contribution only once or infrequently, please use
the *Joint Copyright Assignment - One-time Contribution* form.
(<https://github.com/unicode-org/icu-docs/blob/master/legal/contributions/Copyright_Assignment.rtf>).
(<https://github.com/unicode-org/icu-docs/blob/main/legal/contributions/Copyright_Assignment.rtf>).
The contribution will be identified by a bug ID which is unique to the
contribution and entered into the form. Therefore, please make sure that there
is an appropriate bug (or Request For Enhancement) in the ICU bug database, or
@ -96,7 +96,7 @@ The process for ongoing contributors involves two types of forms: Initially, and
only once, an ongoing contributor submits a *Joint Copyright Assignment by
Ongoing Contributor* form, agreeing to essentially the same terms as in the
one-time contributor form, for all future contributions. (See the form at
<https://github.com/unicode-org/icu-docs/blob/master/legal/contributions/Copyright_Assignment_ongoing.rtf>).
<https://github.com/unicode-org/icu-docs/blob/main/legal/contributions/Copyright_Assignment_ongoing.rtf>).
The contributor must also send another form, *Addendum to Joint Copyright
Assignment by Ongoing Contributor: Authors*, for the initial set and each
@ -106,7 +106,7 @@ additional authors need to be listed on each such form.) The contributor agrees
to ensure that all of these authors agree to adhere to the terms of the
associated *Joint Copyright Assignment by Ongoing Contributor Agreement*. (See
the Authors Addendum form at
<https://github.com/unicode-org/icu-docs/blob/master/legal/contributions/Copyright_Assignment_authors.rtf>).
<https://github.com/unicode-org/icu-docs/blob/main/legal/contributions/Copyright_Assignment_authors.rtf>).
Some of an ongoing contributor's authors will have commit access to the ICU
source code repository. Their committer IDs need to be established before
@ -122,7 +122,7 @@ identified by their association with the contributor's committer IDs.
All previous "one-off" contributions from non-IBM sources to ICU are listed on
the code contributions page in ICU's source code repository. The page contains
links to the softcopies of the Joint Copyright Assignment forms. See
<https://htmlpreview.github.io/?https://github.com/unicode-org/icu-docs/blob/master/legal/contributions/code_contributions.html>
<https://htmlpreview.github.io/?https://github.com/unicode-org/icu-docs/blob/main/legal/contributions/code_contributions.html>
In addition, the following non-IBM companies are registered as Ongoing
Contributors:
@ -134,4 +134,4 @@ See the repository folder that contains the contributions page for the full set
of softcopies of contributor agreements including one-off contributions,
ongoing-contributor agreements and author-addendum documents to
ongoing-contributor agreements:
<https://github.com/unicode-org/icu-docs/tree/master/legal/contributions>
<https://github.com/unicode-org/icu-docs/tree/main/legal/contributions>

4
docs/userguide/dev/sync/custom.md
View file

@ -41,7 +41,7 @@ synchronization primitives.
**Low Level Atomics**, a set of platform or compiler dependent typedefs and
inlines. Provided in the internal header file
[`umutex.h`](https://github.com/unicode-org/icu/blob/master/icu4c/source/common/umutex.h).
[`umutex.h`](https://github.com/unicode-org/icu/blob/main/icu4c/source/common/umutex.h).
| Type/Function | Description |
|---------------------------------------------------------|-------------------------------------------------------------------------------|
@ -71,7 +71,7 @@ Provided in a .cpp file.
`UInitOnce` and `umtx_initOnce()` are used internally by ICU for thread-safe
one-time initialization. Their implementation is split into a
platform-independent part (contained in
[`umutex.h`](https://github.com/unicode-org/icu/blob/master/icu4c/source/common/umutex.h)),
[`umutex.h`](https://github.com/unicode-org/icu/blob/main/icu4c/source/common/umutex.h)),
and the pair of platform-dependent implementation functions listed above.
**Build Setup**

2
docs/userguide/dev/sync/index.md
View file

@ -50,7 +50,7 @@ implementations](custom.md) for other platforms.
The functions and types listed below are intended for use throughout the ICU
library code, where ever synchronization is required. They are defined in the
internal header
[umutex.h](https://github.com/unicode-org/icu/blob/master/icu4c/source/common/umutex.h).
[umutex.h](https://github.com/unicode-org/icu/blob/main/icu4c/source/common/umutex.h).
All synchronization within ICU4C implementation code must use these, and avoid
direct use of functions provided by a particular operating system or compiler.

4
docs/userguide/format_parse/numbers/legacy-numberformat.md
View file

@ -132,7 +132,7 @@ and display name, but also the correct number of fraction digits and the correct
the API references for more details.
There is ICU4C sample code at
[icu4c/source/samples/numfmt/main.cpp](https://github.com/unicode-org/icu/blob/master/icu4c/source/samples/numfmt/main.cpp)
[icu4c/source/samples/numfmt/main.cpp](https://github.com/unicode-org/icu/blob/main/icu4c/source/samples/numfmt/main.cpp)
which illustrates the use of `NumberFormat.setCurrency()`.
#### Displaying Numbers
@ -210,6 +210,6 @@ change any of these symbols, can get the `DecimalFormatSymbols` object from your
## Additional Sample Code
C/C++: See
[icu4c/source/samples/numfmt/](https://github.com/unicode-org/icu/blob/master/icu4c/source/samples/numfmt/)
[icu4c/source/samples/numfmt/](https://github.com/unicode-org/icu/blob/main/icu4c/source/samples/numfmt/)
in the ICU source distribution for code samples showing the use of ICU number
formatting.

2
docs/userguide/format_parse/numbers/rbnf-examples.md
View file

@ -106,4 +106,4 @@ syntax can be found in the [API
Documentation](https://unicode-org.github.io/icu-docs/apidoc/released/icu4c/classRuleBasedNumberFormat.html).
More rule examples can be found in the `RuleBasedNumberFormat` [demo
source](https://github.com/unicode-org/icu/blob/master/icu4j/demos/src/com/ibm/icu/dev/demo/rbnf/RbnfSampleRuleSets.java).
source](https://github.com/unicode-org/icu/blob/main/icu4j/demos/src/com/ibm/icu/dev/demo/rbnf/RbnfSampleRuleSets.java).

4
docs/userguide/format_parse/numbers/rounding-modes.md
View file

@ -148,6 +148,6 @@ error if the value cannot be represented exactly without rounding.
* Wikipedia article on Rounding:
<http://en.wikipedia.org/wiki/Rounding#Tie-breaking>
* Live rounding mode chart: [Rounding Mode
Chart](https://htmlpreview.github.io/?https://github.com/unicode-org/icu-demos/blob/master/roundmode/round.html)
Chart](https://htmlpreview.github.io/?https://github.com/unicode-org/icu-demos/blob/main/roundmode/round.html)
and [Source
Code](https://github.com/unicode-org/icu-demos/tree/master/roundmode)
Code](https://github.com/unicode-org/icu-demos/tree/main/roundmode)

14
docs/userguide/howtouseicu.md
View file

@ -24,19 +24,19 @@ License & terms of use: http://www.unicode.org/copyright.html
ICU builds and installs as relatively standard libraries. For details about
building, installing and porting see the [ICU4C
readme](https://htmlpreview.github.io/?https://github.com/unicode-org/icu/blob/master/icu4c/readme.html) and the
[ICU4J readme](https://htmlpreview.github.io/?https://github.com/unicode-org/icu/blob/master/icu4j/readme.html).
readme](https://htmlpreview.github.io/?https://github.com/unicode-org/icu/blob/main/icu4c/readme.html) and the
[ICU4J readme](https://htmlpreview.github.io/?https://github.com/unicode-org/icu/blob/main/icu4j/readme.html).
In addition, ICU4C installs several scripts and makefile fragments that help
build other code using ICU.
For C++, note that there are [Recommended Build
Options](https://htmlpreview.github.io/?https://github.com/unicode-org/icu/blob/master/icu4c/readme.html#RecBuild)
Options](https://htmlpreview.github.io/?https://github.com/unicode-org/icu/blob/main/icu4c/readme.html#RecBuild)
(both for normal use and for ICU as system-level libraries) which are not
default simply for compatibility with older ICU-using code.
Starting with ICU 49, the ICU4C readme has a short section about
[User-Configurable
Settings](https://htmlpreview.github.io/?https://github.com/unicode-org/icu/blob/master/icu4c/readme.html#UserConfig).
Settings](https://htmlpreview.github.io/?https://github.com/unicode-org/icu/blob/main/icu4c/readme.html#UserConfig).
## C++ Makefiles
@ -154,13 +154,13 @@ ICU C++ APIs are normally defined in a versioned namespace, for example
"icu_50". There is a stable "icu" alias which should be used instead. (Entry
point versioning is only to allow for multiple ICU versions linked into one
program. [It is optional and should be off for system
libraries.](https://htmlpreview.github.io/?https://github.com/unicode-org/icu/blob/master/icu4c/readme.html#RecBuild))
libraries.](https://htmlpreview.github.io/?https://github.com/unicode-org/icu/blob/main/icu4c/readme.html#RecBuild))
By default, and only for backward compatibility, the ICU headers contain a line
`using namespace icu_50;` which makes all ICU APIs visible in/with the global
namespace (and potentially collide with non-ICU APIs there). One of the
[Recommended Build
Options](https://htmlpreview.github.io/?https://github.com/unicode-org/icu/blob/master/icu4c/readme.html#RecBuild)
Options](https://htmlpreview.github.io/?https://github.com/unicode-org/icu/blob/main/icu4c/readme.html#RecBuild)
is to turn this off.
To write forward declarations, use
@ -200,7 +200,7 @@ need to modify this file directly to allow `static` and `dll` modes to function.
For building and running trivial (one-compilation-unit) programs with an
installed ICU4C, the shell script
[icurun](https://github.com/unicode-org/icu/blob/master/tools/scripts/icurun)
[icurun](https://github.com/unicode-org/icu/blob/main/tools/scripts/icurun)
may be used. For detailed help, see the top of that script.
As an example, if ICU is installed to the prefix **/opt/local** and the current
directory contains two sample programs "test1.cpp" and "test2.c", they may be

10
docs/userguide/icu4c-readme.md
View file

@ -63,7 +63,7 @@ See the [ICU download page](http://site.icu-project.org/download/) to find the s
The subpage for the current release will also include an API Change Report, both for ICU4C and ICU4J, for a complete list of APIs added, removed, or changed in this release.
The list of API changes since the previous ICU4C release is available [here](https://htmlpreview.github.io/?https://raw.githubusercontent.com/unicode-org/icu/master/icu4c/APIChangeReport.html).
The list of API changes since the previous ICU4C release is available [here](https://htmlpreview.github.io/?https://raw.githubusercontent.com/unicode-org/icu/main/icu4c/APIChangeReport.html).
Changes in previous releases can also be found on the main [ICU download page](http://site.icu-project.org/download) in its version-specific subpages.
@ -584,7 +584,7 @@ There are two ways you can build ICU with Cygwin. You can build with gcc or Micr
`C:\Program Files (x86)\Microsoft Visual Studio 14\VC\bin\x86_amd64\vcvarsx86_amd64.bat` can be used for 64-bit builds on Windows x64.
3. Unzip the icu-XXXX.zip file into any convenient location. Using command line zip, type "unzip -a icu-XXXX.zip -d drive:\directory", or just use WinZip.
4. Change directory to "icu/source", which is where you unzipped ICU.
5. Run `bash ./runConfigureICU Cygwin/MSVC` (See [Windows configuration note](#setting-active-configuration) and non-functional configure options below; see source for [./runConfigureICU](https://github.com/unicode-org/icu/blob/master/icu4c/source/runConfigureICU)).
5. Run `bash ./runConfigureICU Cygwin/MSVC` (See [Windows configuration note](#setting-active-configuration) and non-functional configure options below; see source for [./runConfigureICU](https://github.com/unicode-org/icu/blob/main/icu4c/source/runConfigureICU)).
6. Type `make` to compile the libraries and all the data files. This make command should be GNU make.
7. Optionally, type `make check` to run the test suite, which checks for ICU's functionality integrity (See [testing note](#running-the-tests-from-the-command-line) below).
8. Type `make install` to install ICU. If you used the `--prefix=` option on `configure` or `runConfigureICU`, ICU will be installed to the directory you specified. (See [installation note](#installing-icu) below).
@ -626,7 +626,7 @@ Here are the steps to build ICU:
```
chmod +x runConfigureICU configure install-sh
```
1. Run the [`runConfigureICU`](https://github.com/unicode-org/icu/blob/master/icu4c/source/runConfigureICU) script for your platform. (See [configuration note](#configuring-icu) below).
1. Run the [`runConfigureICU`](https://github.com/unicode-org/icu/blob/main/icu4c/source/runConfigureICU) script for your platform. (See [configuration note](#configuring-icu) below).
1. Now build:
```
gmake
@ -665,7 +665,7 @@ You can install ICU on z/OS or OS/390 (the previous name of z/OS), but IBM tests
* The makedep and GNU make tools are required for building ICU. If it is not already installed on your system, it is available at the [z/OS UNIX - Tools and Toys](http://www-03.ibm.com/servers/eserver/zseries/zos/unix/bpxa1toy.html) site. The PATH environment variable should be updated to contain the location of this executable prior to build. Failure to add these tools to your PATH will cause ICU build failures or cause pkgdata to fail to run.
* Since USS does not support using the mmap() function over NFS, it is recommended that you build ICU on a local filesystem. Once ICU has been built, you should not have this problem while using ICU when the data library has been built as a shared library, which is this is the default setting.
* Encoding considerations: The source code assumes that it is compiled with codepage ibm-1047 (to be exact, the UNIX System Services variant of it). The pax command converts all of the source code files from ASCII to codepage ibm-1047 (USS) EBCDIC. However, some files are binary files and must not be converted, or must be converted back to their original state. You can use the [unpax-icu.sh](https://github.com/unicode-org/icu/blob/master/icu4c/as_is/os390/unpax-icu.sh) script to do this for you automatically. It will unpackage the tar file and convert all the necessary files for you automatically.
* Encoding considerations: The source code assumes that it is compiled with codepage ibm-1047 (to be exact, the UNIX System Services variant of it). The pax command converts all of the source code files from ASCII to codepage ibm-1047 (USS) EBCDIC. However, some files are binary files and must not be converted, or must be converted back to their original state. You can use the [unpax-icu.sh](https://github.com/unicode-org/icu/blob/main/icu4c/as_is/os390/unpax-icu.sh) script to do this for you automatically. It will unpackage the tar file and convert all the necessary files for you automatically.
* z/OS supports both native S/390 hexadecimal floating point and (with OS/390 2.6 and later) IEEE 754 binary floating point. This is a compile time option. Applications built with IEEE should use ICU DLLs that are built with IEEE (and vice versa). The environment variable IEEE390=0 will cause the z/OS version of ICU to be built without IEEE floating point support and use the native hexadecimal floating point. By default ICU is built with IEEE 754 support. Native floating point support is sufficient for codepage conversion, resource bundle and UnicodeString operations, but the Format APIs require IEEE binary floating point.
* z/OS introduced the concept of Extra Performance Linkage (XPLINK) to bring performance improvement opportunities to call-intensive C and C++ applications such as ICU. XPLINK is enabled on a DLL-by-DLL basis, so if you are considering using XPLINK in your application that uses ICU, you should consider building the XPLINK-enabled version of ICU. You need to set ICU's environment variable `OS390_XPLINK=1` prior to invoking the make process to produce binaries that are enabled for XPLINK. The XPLINK option, which is available for z/OS 1.2 and later, requires the PTF PQ69418 to build XPLINK enabled binaries.
* ICU requires XPLINK for the icuio library. If you want to use the rest of ICU without XPLINK, then you must use the --disable-icuio configure option.
@ -755,7 +755,7 @@ Before you start building ICU, ICU requires the following:
The following describes how to setup and build ICU. For background information, you should look at the [UNIX build instructions](#how-to-build-and-install-on-unix).
1. Copy the ICU source .tgz to the IBM i environment, as binary. Also, copy the [unpax-icu.sh](https://github.com/unicode-org/icu/blob/master/icu4c/as_is/os400/unpax-icu.sh) script into the same directory, as a text file.
1. Copy the ICU source .tgz to the IBM i environment, as binary. Also, copy the [unpax-icu.sh](https://github.com/unicode-org/icu/blob/main/icu4c/as_is/os400/unpax-icu.sh) script into the same directory, as a text file.
2. Create target library. This library will be the target for the resulting modules, programs and service programs. You will specify this library on the OUTPUTDIR environment variable.
```
CRTLIB LIB(_libraryname_)

10
docs/userguide/icu4j-readme.md
View file

@ -59,13 +59,13 @@ See the [ICU download page](http://site.icu-project.org/download/) to find the s
The subpage for the current release will also include an API Change Report, both for ICU4C and ICU4J, for a complete list of APIs added, removed, or changed in this release.
The list of API changes since the previous ICU4J release is available [here](https://htmlpreview.github.io/?https://raw.githubusercontent.com/unicode-org/icu/master/icu4j/APIChangeReport.html).
The list of API changes since the previous ICU4J release is available [here](https://htmlpreview.github.io/?https://raw.githubusercontent.com/unicode-org/icu/main/icu4j/APIChangeReport.html).
Changes in previous releases can also be found the main [ICU download page](http://site.icu-project.org/download) in its version-specific subpages.
## License Information
The ICU projects (ICU4C and ICU4J) are hosted by the [Unicode Consortium](http://www.unicode.org/). The ICU binary and source files are distributed under the [UNICODE DATA FILES AND SOFTWARE LICENSE](http://www.unicode.org/copyright.html). The full copy of the license and third party software licenses are available in [LICENSE](https://github.com/unicode-org/icu/blob/master/icu4j/main/shared/licenses/LICENSE) file included in this package.
The ICU projects (ICU4C and ICU4J) are hosted by the [Unicode Consortium](http://www.unicode.org/). The ICU binary and source files are distributed under the [UNICODE DATA FILES AND SOFTWARE LICENSE](http://www.unicode.org/copyright.html). The full copy of the license and third party software licenses are available in [LICENSE](https://github.com/unicode-org/icu/blob/main/icu4j/main/shared/licenses/LICENSE) file included in this package.
## Platform Dependencies
@ -412,7 +412,7 @@ The files in `icudata.jar` get extracted to `com/ibm/icu/impl/data` in the build
### Building ICU4J Resources from ICU4C
ICU4J data is built by ICU4C tools. Please see [`icu4j-readme.txt`](https://github.com/unicode-org/icu/blob/master/icu4c/source/data/icu4j-readme.txt) in `icu4c/source/data` for the procedures.
ICU4J data is built by ICU4C tools. Please see [`icu4j-readme.txt`](https://github.com/unicode-org/icu/blob/main/icu4c/source/data/icu4j-readme.txt) in `icu4c/source/data` for the procedures.
#### Generating Data from CLDR
@ -423,10 +423,10 @@ ICU4J data is built by ICU4C tools. Please see [`icu4j-readme.txt`](https://gith
1. Checkout or download CLDR version `release-38`
2. Checkout ICU with tag `release-68-1`
3. cd to icu4c/source/data directory
4. Follow the instructions in [`icu4c/source/data/cldr-icu-readme.txt`](https://github.com/unicode-org/icu/blob/master/icu4c/source/data/cldr-icu-readme.txt)
4. Follow the instructions in [`icu4c/source/data/cldr-icu-readme.txt`](https://github.com/unicode-org/icu/blob/main/icu4c/source/data/cldr-icu-readme.txt)
5. Rebuild ICU4C with the newly generated data.
6. Run ICU4C tests to verify that the new data is good.
7. Build ICU4J data from ICU4C data by following the procedures in [`icu4j/source/data/icu4j-readme.txt`](https://github.com/unicode-org/icu/blob/master/icu4c/source/data/icu4j-readme.txt)
7. Build ICU4J data from ICU4C data by following the procedures in [`icu4j/source/data/icu4j-readme.txt`](https://github.com/unicode-org/icu/blob/main/icu4c/source/data/icu4j-readme.txt)
8. cd to `icu4j` dir
9. Build and test icu4j

6
docs/userguide/icu_data/buildtool.md
View file

@ -76,7 +76,7 @@ print messages when errors are found in your config file.
To build ICU4J with custom data, you must first build ICU4C with custom data
and then generate the JAR file. For more information, read
[icu4j-readme.txt](https://github.com/unicode-org/icu/blob/master/icu4c/source/data/icu4j-readme.txt).
[icu4j-readme.txt](https://github.com/unicode-org/icu/blob/main/icu4c/source/data/icu4j-readme.txt).
### Locale Slicing
@ -217,7 +217,7 @@ The data for many ICU features live in individual files. The ICU Data Build
Tool puts puts similar *types* of files into categories. The following table
summarizes the ICU data files and their corresponding features and categories:
| Feature | Category ID(s) | Data Files <br/> ([icu4c/source/data](https://github.com/unicode-org/icu/tree/master/icu4c/source/data)) | Resource Size <br/> (as of ICU 64) |
| Feature | Category ID(s) | Data Files <br/> ([icu4c/source/data](https://github.com/unicode-org/icu/tree/main/icu4c/source/data)) | Resource Size <br/> (as of ICU 64) |
|---|---|---|---|
| Break Iteration | `"brkitr_rules"` <br/> `"brkitr_dictionaries"` <br/> `"brkitr_tree"` | brkitr/rules/\*.txt <br/> brkitr/dictionaries/\*.txt <br/> brkitr/\*.txt | 522 KiB <br/> **2.8 MiB** <br/> 14 KiB |
| Charset Conversion | `"conversion_mappings"` | mappings/\*.ucm | **4.9 MiB** |
@ -416,7 +416,7 @@ You can apply resource filters to all locale tree categories as well as to
categories that include resource bundles, such as the `"misc"` category.
For example, consider measurement units. There is one unit file per locale (example:
[en.txt](https://github.com/unicode-org/icu/blob/master/icu4c/source/data/unit/en.txt)),
[en.txt](https://github.com/unicode-org/icu/blob/main/icu4c/source/data/unit/en.txt)),
and that file contains data for all measurement units in CLDR. However, if
you are only formatting distances, for example, you may need the data for only
a small set of units.

140
docs/userguide/icudata.md
View file

@ -61,7 +61,7 @@ Data which is NOT sourced from CLDR includes:
with the CLDR datasets)
For information on building ICU data from CLDR, see the
[cldr-icu-readme](https://github.com/unicode-org/icu/blob/master/icu4c/source/data/cldr-icu-readme.txt).
[cldr-icu-readme](https://github.com/unicode-org/icu/blob/main/icu4c/source/data/cldr-icu-readme.txt).
## ICU Data Directory
@ -474,7 +474,7 @@ goes into your ICU locale data file.
The first step is to obtain or create a .ucm (source) mapping data file for the
desired converter. A large archive of converter data is maintained by the ICU
team at <https://github.com/unicode-org/icu-data/tree/master/charset/data/ucm>
team at <https://github.com/unicode-org/icu-data/tree/main/charset/data/ucm>
We will use `solaris-eucJP-2.7.ucm`, available from the repository mentioned
above, as an example.
@ -582,7 +582,7 @@ If you have data for a locale that is not included in ICU's standard build, then
you can add it to the build in a very similar way as with conversion tables
above. The ICU project provides a large number of additional locales in its
[locale
repository](https://github.com/unicode-org/icu/blob/master/icu4c/source/data/locales/)
repository](https://github.com/unicode-org/icu/blob/main/icu4c/source/data/locales/)
on the web. Most of this locale data is derived from the CLDR ([Common Locale
Data Repository](http://www.unicode.org/cldr/)) project.
@ -769,130 +769,130 @@ loadable data objects.)
* Source format: (list of files provided as input to the icupkg tool, or
on the gencmn tool command line)
* Binary format: .dat:
[source/tools/toolutil/pkg_gencmn.cpp](https://github.com/unicode-org/icu/blob/master/icu4c/source/tools/toolutil/pkg_gencmn.cpp)
[source/tools/toolutil/pkg_gencmn.cpp](https://github.com/unicode-org/icu/blob/main/icu4c/source/tools/toolutil/pkg_gencmn.cpp)
* Generator tool:
[icupkg](https://github.com/unicode-org/icu/blob/master/icu4c/source/tools/icupkg)
[icupkg](https://github.com/unicode-org/icu/blob/main/icu4c/source/tools/icupkg)
or
[gencmn](https://github.com/unicode-org/icu/blob/master/icu4c/source/tools/gencmn)
[gencmn](https://github.com/unicode-org/icu/blob/main/icu4c/source/tools/gencmn)
#### Resource bundles
* Source format: .txt:
[icuhtml/design/bnf_rb.txt](https://github.com/unicode-org/icu-docs/blob/master/design/bnf_rb.txt)
[icuhtml/design/bnf_rb.txt](https://github.com/unicode-org/icu-docs/blob/main/design/bnf_rb.txt)
* Binary format: .res:
[source/common/uresdata.h](https://github.com/unicode-org/icu/blob/master/icu4c/source/common/uresdata.h)
[source/common/uresdata.h](https://github.com/unicode-org/icu/blob/main/icu4c/source/common/uresdata.h)
* Generator tool:
[genrb](https://github.com/unicode-org/icu/blob/master/icu4c/source/tools/genrb)
[genrb](https://github.com/unicode-org/icu/blob/main/icu4c/source/tools/genrb)
#### Unicode conversion mapping tables
* Source format: .ucm: [Conversion Data chapter](conversion/data.md)
* Binary format: .cnv:
[source/common/ucnvmbcs.h](https://github.com/unicode-org/icu/blob/master/icu4c/source/common/ucnvmbcs.h)
[source/common/ucnvmbcs.h](https://github.com/unicode-org/icu/blob/main/icu4c/source/common/ucnvmbcs.h)
* Generator tool:
[makeconv](https://github.com/unicode-org/icu/blob/master/icu4c/source/tools/makeconv)
[makeconv](https://github.com/unicode-org/icu/blob/main/icu4c/source/tools/makeconv)
#### Conversion (charset) aliases
* Source format:
[source/data/mappings/convrtrs.txt](https://github.com/unicode-org/icu/blob/master/icu4c/source/data/mappings/convrtrs.txt):
[source/data/mappings/convrtrs.txt](https://github.com/unicode-org/icu/blob/main/icu4c/source/data/mappings/convrtrs.txt):
contains format description. The command "uconv -l --canon" will also
generate the alias table from the currently used copy of ICU.
* Binary format: cnvalias.icu:
[source/common/ucnv_io.cpp](https://github.com/unicode-org/icu/blob/master/icu4c/source/common/ucnv_io.cpp)
[source/common/ucnv_io.cpp](https://github.com/unicode-org/icu/blob/main/icu4c/source/common/ucnv_io.cpp)
* Generator tool:
[gencnval](https://github.com/unicode-org/icu/blob/master/icu4c/source/tools/gencnval)
[gencnval](https://github.com/unicode-org/icu/blob/main/icu4c/source/tools/gencnval)
#### Unicode Character Data (Properties; for Java only: hardcoded in C common library)
* Source format:
[source/data/unidata/ppucd.txt](https://github.com/unicode-org/icu/blob/master/icu4c/source/data/unidata/ppucd.txt):
[source/data/unidata/ppucd.txt](https://github.com/unicode-org/icu/blob/main/icu4c/source/data/unidata/ppucd.txt):
[Preparsed UCD](http://site.icu-project.org/design/props/ppucd)
* Binary format: uprops.icu:
[tools/unicode/c/genprops/corepropsbuilder.cpp](https://github.com/unicode-org/icu/blob/master/tools/unicode/c/genprops/corepropsbuilder.cpp)
[tools/unicode/c/genprops/corepropsbuilder.cpp](https://github.com/unicode-org/icu/blob/main/tools/unicode/c/genprops/corepropsbuilder.cpp)
* Generator tool:
[genprops](https://github.com/unicode-org/icu/blob/master/tools/unicode/c/genprops)
[genprops](https://github.com/unicode-org/icu/blob/main/tools/unicode/c/genprops)
#### Unicode Character Data (Case mappings; for Java only: hardcoded in C common library)
* Source format:
[source/data/unidata/*.txt](https://github.com/unicode-org/icu/blob/master/icu4c/source/data/unidata):
[source/data/unidata/*.txt](https://github.com/unicode-org/icu/blob/main/icu4c/source/data/unidata):
[Unicode Character Database](http://www.unicode.org/onlinedat/online.html)
* Binary format: ucase.icu:
[tools/unicode/c/genprops/casepropsbuilder.cpp](https://github.com/unicode-org/icu/blob/master/tools/unicode/c/genprops/casepropsbuilder.cpp)
[tools/unicode/c/genprops/casepropsbuilder.cpp](https://github.com/unicode-org/icu/blob/main/tools/unicode/c/genprops/casepropsbuilder.cpp)
* Generator tool:
[genprops](https://github.com/unicode-org/icu/blob/master/tools/unicode/c/genprops)
[genprops](https://github.com/unicode-org/icu/blob/main/tools/unicode/c/genprops)
#### Unicode Character Data (BiDi, and Arabic shaping; for Java only: hardcoded in C common library)
* Source format:
[source/data/unidata/*.txt](https://github.com/unicode-org/icu/blob/master/icu4c/source/data/unidata):
[source/data/unidata/*.txt](https://github.com/unicode-org/icu/blob/main/icu4c/source/data/unidata):
[Unicode Character Database](http://www.unicode.org/onlinedat/online.html)
* Binary format: ubidi.icu:
[tools/unicode/c/genprops/bidipropsbuilder.cpp](https://github.com/unicode-org/icu/blob/master/tools/unicode/c/genprops/bidipropsbuilder.cpp)
[tools/unicode/c/genprops/bidipropsbuilder.cpp](https://github.com/unicode-org/icu/blob/main/tools/unicode/c/genprops/bidipropsbuilder.cpp)
* Generator tool:
[genprops](https://github.com/unicode-org/icu/blob/master/tools/unicode/c/genprops)
[genprops](https://github.com/unicode-org/icu/blob/main/tools/unicode/c/genprops)
#### Unicode Character Data (Normalization since ICU 4.4) & custom normalization data
* Source format:
[source/data/unidata/norm2/*.tx](https://github.com/unicode-org/icu/blob/master/icu4c/source/data/unidata/norm2):
[source/data/unidata/norm2/*.tx](https://github.com/unicode-org/icu/blob/main/icu4c/source/data/unidata/norm2):
Files derived from the [Unicode Character
Database](http://www.unicode.org/onlinedat/online.html), or custom data.
* Binary format: .nrm:
[source/common/normalizer2impl.h](https://github.com/unicode-org/icu/blob/master/icu4c/source/common/normalizer2impl.h)
[source/common/normalizer2impl.h](https://github.com/unicode-org/icu/blob/main/icu4c/source/common/normalizer2impl.h)
* Generator tool:
[gennorm2](https://github.com/unicode-org/icu/blob/master/icu4c/source/tools/gennorm2)
[gennorm2](https://github.com/unicode-org/icu/blob/main/icu4c/source/tools/gennorm2)
#### Unicode Character Data (Character names)
* Source format:
[source/data/unidata/UnicodeData.txt](https://github.com/unicode-org/icu/blob/master/icu4c/source/data/unidata/UnicodeData.txt):
[source/data/unidata/UnicodeData.txt](https://github.com/unicode-org/icu/blob/main/icu4c/source/data/unidata/UnicodeData.txt):
[Unicode Character Database](http://www.unicode.org/onlinedat/online.html)
* Binary format: unames.icu:
[tools/unicode/c/genprops/namespropsbuilder.cpp](https://github.com/unicode-org/icu/blob/master/tools/unicode/c/genprops/namespropsbuilder.cpp)
[tools/unicode/c/genprops/namespropsbuilder.cpp](https://github.com/unicode-org/icu/blob/main/tools/unicode/c/genprops/namespropsbuilder.cpp)
* Generator tool:
[genprops](https://github.com/unicode-org/icu/blob/master/tools/unicode/c/genprops)
[genprops](https://github.com/unicode-org/icu/blob/main/tools/unicode/c/genprops)
#### Unicode Character Data (Property [value] aliases since ICU 4.8; for Java only: hardcoded in C common library since ICU 4.8)
* Source format: [UCD Property*Aliases.txt](http://www.unicode.org/Public/UNIDATA/):
[Unicode Character Database](http://www.unicode.org/onlinedat/online.html)
* Binary format: pnames.icu:
[source/common/propname.h](https://github.com/unicode-org/icu/blob/master/icu4c/source/common/propname.h)
[source/common/propname.h](https://github.com/unicode-org/icu/blob/main/icu4c/source/common/propname.h)
* Generator tool:
[genprops](https://github.com/unicode-org/icu/blob/master/tools/unicode/c/genprops)
[genprops](https://github.com/unicode-org/icu/blob/main/tools/unicode/c/genprops)
#### Unicode Character Data (Text layout properties since ICU 64)
* Source format:
[source/data/unidata/ppucd.txt](https://github.com/unicode-org/icu/blob/master/icu4c/source/data/unidata/ppucd.txt):
[source/data/unidata/ppucd.txt](https://github.com/unicode-org/icu/blob/main/icu4c/source/data/unidata/ppucd.txt):
[Preparsed UCD](http://site.icu-project.org/design/props/ppucd)
* Binary format: ulayout.icu:
[tools/unicode/c/genprops/layoutpropsbuilder.cpp](https://github.com/unicode-org/icu/blob/master/tools/unicode/c/genprops/layoutpropsbuilder.cpp)
[tools/unicode/c/genprops/layoutpropsbuilder.cpp](https://github.com/unicode-org/icu/blob/main/tools/unicode/c/genprops/layoutpropsbuilder.cpp)
* Generator tool:
[genprops](https://github.com/unicode-org/icu/blob/master/tools/unicode/c/genprops)
[genprops](https://github.com/unicode-org/icu/blob/main/tools/unicode/c/genprops)
#### Collation data (root collation & tailorings; ICU 53 & later)
* Source format: Original data from allkeys_CLDR.txt in
[CLDR Root Collation Data Files](http://www.unicode.org/reports/tr35/tr35-collation.html#Root_Data_Files)
processed into
[source/data/unidata/FractionalUCA.txt](https://github.com/unicode-org/icu/blob/master/icu4c/source/data/unidata/FractionalUCA.txt)
[source/data/unidata/FractionalUCA.txt](https://github.com/unicode-org/icu/blob/main/icu4c/source/data/unidata/FractionalUCA.txt)
by
[tool at unicode.org maintained by Mark Davis](https://sites.google.com/site/unicodetools/#TOC-UCA)
(call the Main class with option writeFractionalUCA); source tailorings (text rules) in
[source/data/coll/*.txt](https://github.com/unicode-org/icu/blob/master/icu4c/source/data/coll)
[source/data/coll/*.txt](https://github.com/unicode-org/icu/blob/main/icu4c/source/data/coll)
resource bundles: [Collation Customization chapter](collation/customization/index.md).
* Binary format: ucadata.icu & binary tailorings in resource bundles:
[source/i18n/collationdatareader.h](https://github.com/unicode-org/icu/blob/master/icu4c/source/i18n/collationdatareader.h)
[source/i18n/collationdatareader.h](https://github.com/unicode-org/icu/blob/main/icu4c/source/i18n/collationdatareader.h)
* Generator tool:
[genuca](https://github.com/unicode-org/icu/blob/master/tools/unicode/c/genuca),
[genrb](https://github.com/unicode-org/icu/blob/master/icu4c/source/tools/genrb)
[genuca](https://github.com/unicode-org/icu/blob/main/tools/unicode/c/genuca),
[genrb](https://github.com/unicode-org/icu/blob/main/icu4c/source/tools/genrb)
#### Rule-based break iterator data
* Source format: .txt: [Boundary Analysis chapter](boundaryanalysis/index.md)
* Binary format: .brk:
[source/common/rbbidata.h](https://github.com/unicode-org/icu/blob/master/icu4c/source/common/rbbidata.h)
[source/common/rbbidata.h](https://github.com/unicode-org/icu/blob/main/icu4c/source/common/rbbidata.h)
* Generator tool:
[genbrk](https://github.com/unicode-org/icu/blob/master/icu4c/source/tools/genbrk)
[genbrk](https://github.com/unicode-org/icu/blob/main/icu4c/source/tools/genbrk)
#### Dictionary-based break iterator data (ICU 50 & later)
* Source format: txt: [gendict.cpp
comments](https://github.com/unicode-org/icu/blob/master/icu4c/source/tools/gendict/gendict.cpp)
comments](https://github.com/unicode-org/icu/blob/main/icu4c/source/tools/gendict/gendict.cpp)
* Binary format: .dict: see
[source/common/dictionarydata.h](https://github.com/unicode-org/icu/blob/master/icu4c/source/common/dictionarydata.h
[source/common/dictionarydata.h](https://github.com/unicode-org/icu/blob/main/icu4c/source/common/dictionarydata.h
* Generator tool:
[gendict](https://github.com/unicode-org/icu/blob/master/icu4c/source/tools/gendict)
[gendict](https://github.com/unicode-org/icu/blob/main/icu4c/source/tools/gendict)
#### Rule-based transform (transliterator) data
* Source format: .txt (in resource bundles): [Transform Rule Tutorial chapter](transforms/general/rules.md)
@ -901,36 +901,36 @@ loadable data objects.)
#### Time zone data (ICU 4.4 & later)
* Source format:
[source/data/misc/zoneinfo64.txt](https://github.com/unicode-org/icu/blob/master/icu4c/source/data/misc/zoneinfo64.txt):
[source/data/misc/zoneinfo64.txt](https://github.com/unicode-org/icu/blob/main/icu4c/source/data/misc/zoneinfo64.txt):
ftp://elsie.nci.nih.gov/pub/ tzdata<year><rev>.tar.gz
* Binary format: zoneinfo64.res (generated by genrb and
[tzcode tools](https://github.com/unicode-org/icu/blob/master/icu4c/source/tools/tzcode/readme.txt)).
[tzcode tools](https://github.com/unicode-org/icu/blob/main/icu4c/source/tools/tzcode/readme.txt)).
* Generator tool: Does not apply
#### StringPrep profile data
* Source format:
[source/data/sprep/rfc3491.txt](https://github.com/unicode-org/icu/blob/master/icu4c/source/data/sprep/rfc3491.txt):
[source/data/sprep/rfc3491.txt](https://github.com/unicode-org/icu/blob/main/icu4c/source/data/sprep/rfc3491.txt):
* Binary format: .spp:
[source/tools/gensprep/store.c](https://github.com/unicode-org/icu/blob/master/icu4c/source/tools/gensprep/store.c)
[source/tools/gensprep/store.c](https://github.com/unicode-org/icu/blob/main/icu4c/source/tools/gensprep/store.c)
* Generator tool:
[gensprep](https://github.com/unicode-org/icu/blob/master/icu4c/source/tools/gensprep)
[gensprep](https://github.com/unicode-org/icu/blob/main/icu4c/source/tools/gensprep)
#### Confusables data
* Source format:
[source/data/unidata/confusables.txt](https://github.com/unicode-org/icu/blob/master/icu4c/source/data/unidata/confusables.txt),
[source/data/unidata/confusablesWholeScript.txt](https://github.com/unicode-org/icu/blob/master/icu4c/source/data/unidata/confusablesWholeScript.txt)
[source/data/unidata/confusables.txt](https://github.com/unicode-org/icu/blob/main/icu4c/source/data/unidata/confusables.txt),
[source/data/unidata/confusablesWholeScript.txt](https://github.com/unicode-org/icu/blob/main/icu4c/source/data/unidata/confusablesWholeScript.txt)
* Binary format: .spp:
[confusables.cfu: source/i18n/uspoof_impl.h](https://github.com/unicode-org/icu/blob/master/icu4c/source/i18n/uspoof_impl.h)
* Generator tool: [gencfu](https://github.com/unicode-org/icu/blob/master/icu4c/source/tools/gencfu)
[confusables.cfu: source/i18n/uspoof_impl.h](https://github.com/unicode-org/icu/blob/main/icu4c/source/i18n/uspoof_impl.h)
* Generator tool: [gencfu](https://github.com/unicode-org/icu/blob/main/icu4c/source/tools/gencfu)
### Public Data Files (old versions)
#### Unicode Character Data (Normalization before ICU 4.4; for Java only: was hardcoded in C common library)
* Source format:
[source/data/unidata/*.txt]((https://github.com/unicode-org/icu/blob/master/icu4c/source/data/unidata):
[source/data/unidata/*.txt]((https://github.com/unicode-org/icu/blob/main/icu4c/source/data/unidata):
[Unicode Character Database](http://www.unicode.org/onlinedat/online.html)
* Binary format: unorm.icu:
[source/common/unormimp.h](https://github.com/unicode-org/icu/blob/master/icu4c/source/common/unormimp.h)
[source/common/unormimp.h](https://github.com/unicode-org/icu/blob/main/icu4c/source/common/unormimp.h)
* Generator tool: gennorm
#### Unicode Character Data (Property [value] aliases before ICU 4.8)
@ -942,14 +942,14 @@ loadable data objects.)
* Source format: Same as in ICU 53
* Binary format: ucadata.icu & binary tailorings in resource bundles: source/i18n/ucol_imp.h (ICU 52)
* Generator tool:
[genuca](https://github.com/unicode-org/icu/blob/master/tools/unicode/c/genuca),
[genrb](https://github.com/unicode-org/icu/blob/master/icu4c/source/tools/genrb)
[genuca](https://github.com/unicode-org/icu/blob/main/tools/unicode/c/genuca),
[genrb](https://github.com/unicode-org/icu/blob/main/icu4c/source/tools/genrb)
#### Collation data (Inverse UCA, weights->code points; ICU 52 & earlier)
* Source format: Processed from FractionalUCA.txt like ICU 52 ucadata.icu
* Binary format: invuca.icu: source/i18n/ucol_imp.h (ICU 52)
* Generator tool:
[genuca](https://github.com/unicode-org/icu/blob/master/tools/unicode/c/genuca)
[genuca](https://github.com/unicode-org/icu/blob/main/tools/unicode/c/genuca)
#### Dictionary-based break iterator data (ICU 49 & earlier)
* Source format: .txt: genctd.cpp comments
@ -959,7 +959,7 @@ loadable data objects.)
#### Time zone data (Before ICU 4.4)
* Source format: .source/data/misc/zoneinfo.txt (ICU 4.2): ftp://elsie.nci.nih.gov/pub/ tzdata<year><rev>.tar.gz
* Binary format: zoneinfo64.res (generated by genrb and
[tzcode tools](https://github.com/unicode-org/icu/blob/master/icu4c/source/tools/tzcode/readme.txt)).
[tzcode tools](https://github.com/unicode-org/icu/blob/main/icu4c/source/tools/tzcode/readme.txt)).
* Generator tool: Does not apply
### Non-File API Binary Data
@ -967,18 +967,18 @@ loadable data objects.)
#### Converter selector data
* Source format: none
* Binary format:
[source/common/ucnvsel.cpp](https://github.com/unicode-org/icu/blob/master/icu4c/source/common/ucnvsel.cpp)
[source/common/ucnvsel.cpp](https://github.com/unicode-org/icu/blob/main/icu4c/source/common/ucnvsel.cpp)
* Generator tool:
[ucnvsel_open()](https://github.com/unicode-org/icu/blob/master/icu4c/source/common/ucnvsel.cpp)
[ucnvsel_open()](https://github.com/unicode-org/icu/blob/main/icu4c/source/common/ucnvsel.cpp)
### Test-Only Data Files
#### test.icu (for udata API testing)
* Source format: none (fixed output from gentest when not using -r or -j options)
* Binary format: test.icu: see `createData()` in
[source/tools/gentest/gentest.c](https://github.com/unicode-org/icu/blob/master/icu4c/source/tools/gentest/gentest.c)
[source/tools/gentest/gentest.c](https://github.com/unicode-org/icu/blob/main/icu4c/source/tools/gentest/gentest.c)
* Generator tool:
[gentest](https://github.com/unicode-org/icu/blob/master/icu4c/source/tools/gentest/gentest.c)
[gentest](https://github.com/unicode-org/icu/blob/main/icu4c/source/tools/gentest/gentest.c)
### Other Data Structures
@ -986,28 +986,28 @@ loadable data objects.)
* Source format: (public builder API)
* Binary format:
[ICU Code Point Tries design doc](http://site.icu-project.org/design/struct/utrie),
[icu4c/source/common/ucptrie_impl.h](https://github.com/unicode-org/icu/blob/master/icu4c/source/common/ucptrie_impl.h)
[icu4c/source/common/ucptrie_impl.h](https://github.com/unicode-org/icu/blob/main/icu4c/source/common/ucptrie_impl.h)
* Generator tool: (builder class)
#### UTrie2 (C)/Trie2 (Java) (maps code points to integers)
* Source format: (internal builder API)
* Binary format:
[ICU Code Point Tries design doc](http://site.icu-project.org/design/struct/utrie),
[icu4c/source/common/utrie2_impl.h](https://github.com/unicode-org/icu/blob/master/icu4c/source/common/utrie2_impl.h)
[icu4c/source/common/utrie2_impl.h](https://github.com/unicode-org/icu/blob/main/icu4c/source/common/utrie2_impl.h)
* Generator tool: (builder class)
#### BytesTrie (maps byte sequences to 32-bit integers)
* Source format: (public builder API)
* Binary format:
[BytesTrie design doc](http://site.icu-project.org/design/struct/tries/bytestrie),
[icu4c/source/common/unicode/bytestrie.h](https://github.com/unicode-org/icu/blob/master/icu4c/source/common/unicode/bytestrie.h)
[icu4c/source/common/unicode/bytestrie.h](https://github.com/unicode-org/icu/blob/main/icu4c/source/common/unicode/bytestrie.h)
* Generator tool: (builder class)
#### UCharsTrie (C++)/CharsTrie (Java) (maps 16-bit-Unicode strings to 32-bit integers)
* Source format: (public builder API)
* Binary format:
[UCharsTrie design doc](http://site.icu-project.org/design/struct/tries/ucharstrie),
[icu4c/source/common/unicode/ucharstrie.h](https://github.com/unicode-org/icu/blob/master/icu4c/source/common/unicode/ucharstrie.h)
[icu4c/source/common/unicode/ucharstrie.h](https://github.com/unicode-org/icu/blob/main/icu4c/source/common/unicode/ucharstrie.h)
* Generator tool: (builder class)
## ICU4J Resource Information
@ -1127,15 +1127,15 @@ corresponding resource files already in that directory.
1. [ICU4C](http://icu-project.org/download/)
2. Compilers and tools required for [building ICU4C](https://htmlpreview.github.io/?https://github.com/unicode-org/icu/blob/master/icu4c/readme.html#HowToBuild).
2. Compilers and tools required for [building ICU4C](https://htmlpreview.github.io/?https://github.com/unicode-org/icu/blob/main/icu4c/readme.html#HowToBuild).
3. J2SE SDK version 5 or above
#### Procedure
1. Download and build ICU4C on a Windows or Linux machine. For instructions on downloading and building ICU4C, please click
[here](https://htmlpreview.github.io/?https://github.com/unicode-org/icu/blob/master/icu4c/readme.html#HowToBuild).
[here](https://htmlpreview.github.io/?https://github.com/unicode-org/icu/blob/main/icu4c/readme.html#HowToBuild).
2. Follow the remaining instructions in
[*$icu4c_root*/source/data/icu4j-readme.txt](https://github.com/unicode-org/icu/blob/master/icu4c/source/data/icu4j-readme.txt).
[*$icu4c_root*/source/data/icu4j-readme.txt](https://github.com/unicode-org/icu/blob/main/icu4c/source/data/icu4j-readme.txt).
*$icu4c_root* is the root directory of ICU4C source package.

6
docs/userguide/icufaq/icu4j-faq.md
View file

@ -84,7 +84,7 @@ with the pattern in a new version.
#### How can I see all API changes between two different ICU versions?
For every ICU4J release, we publish
[APIChangeReport.html](https://htmlpreview.github.io/?https://github.com/unicode-org/icu/blob/master/icu4j/APIChangeReport.html)
[APIChangeReport.html](https://htmlpreview.github.io/?https://github.com/unicode-org/icu/blob/main/icu4j/APIChangeReport.html)
which captures all API changes since previous reference release.
However, someone may want to see the changes between the
current release and much older ICU4J version. For example, you're currently
@ -95,10 +95,10 @@ generate a change report page by following steps.
archive](http://site.icu-project.org/download/64#TOC-ICU4J-Download)
from the ICU 64 download page and extract files to your local system.
2. Set up ICU4J build environment as explained in
[readme.html](https://htmlpreview.github.io/?https://github.com/unicode-org/icu/blob/master/icu4j/readme.html)
[readme.html](https://htmlpreview.github.io/?https://github.com/unicode-org/icu/blob/main/icu4j/readme.html)
included in the root directory of the ICU4J source package archive.
3. Edit
[build.properties](https://github.com/unicode-org/icu/blob/master/icu4j/build.properties)
[build.properties](https://github.com/unicode-org/icu/blob/main/icu4j/build.properties)
in the root directory and change the property value api.report.prev.version
from 63 to 60.
4. Invoke ant target "apireport".

12
docs/userguide/icufaq/index.md
View file

@ -249,7 +249,7 @@ closer to Java, which is important for porting between ICU4C and ICU4J. We use
functions and type-safe constants instead of #define, etc. However, we do not
use exceptions, and we do not use the Standard Template Library (STL), so
ICU4C's dependencies on the C++ library are minimal. See the new
[dependencies.txt](https://github.com/unicode-org/icu/blob/master/icu4c/source/test/depstest/dependencies.txt)
[dependencies.txt](https://github.com/unicode-org/icu/blob/main/icu4c/source/test/depstest/dependencies.txt)
and search for "group: cplusplus".
As ICU does not use exceptions, the GCC option `-fno-exceptions` will reduce or
@ -348,10 +348,10 @@ functions are provided for your convenience instead of using the `ucnv_\*` API.
You can also take a look at the `UTF_\*`, `UTF8_\*`, `UTF16_\*` and `UTF32_\*`
macros, which are defined in
[unicode/utf.h](https://github.com/unicode-org/icu/blob/master/icu4c/source/common/unicode/utf.h),
[unicode/utf8.h](https://github.com/unicode-org/icu/blob/master/icu4c/source/common/unicode/utf8.h),
[unicode/utf16.h](https://github.com/unicode-org/icu/blob/master/icu4c/source/common/unicode/utf16.h)
and [unicode/utf32.h](https://github.com/unicode-org/icu/blob/master/icu4c/source/common/unicode/utf32.h).
[unicode/utf.h](https://github.com/unicode-org/icu/blob/main/icu4c/source/common/unicode/utf.h),
[unicode/utf8.h](https://github.com/unicode-org/icu/blob/main/icu4c/source/common/unicode/utf8.h),
[unicode/utf16.h](https://github.com/unicode-org/icu/blob/main/icu4c/source/common/unicode/utf16.h)
and [unicode/utf32.h](https://github.com/unicode-org/icu/blob/main/icu4c/source/common/unicode/utf32.h).
These macros are helpful for programmers that need to manipulate and process
Unicode strings.
@ -431,7 +431,7 @@ to check for errors after calling a function by using the `U_SUCCESS` and
and `U_FAILURE` returns true when the function did NOT run properly. You may
handle specific errors from a function by checking the exact value of error. The
possible values of `UErrorCode` are located in
[utypes.h](https://github.com/unicode-org/icu/blob/master/icu4c/source/common/unicode/utypes.h)
[utypes.h](https://github.com/unicode-org/icu/blob/main/icu4c/source/common/unicode/utypes.h)
of the common project. Before any function is called with a `UErrorCode`, it
must be initialized to `U_ZERO_ERROR`.

2
docs/userguide/index.md
View file

@ -104,6 +104,6 @@ included, building, installing, etc.
## ICU License
Current license: <https://github.com/unicode-org/icu/blob/master/icu4c/LICENSE>
Current license: <https://github.com/unicode-org/icu/blob/main/icu4c/LICENSE>
See also FAQ section ["How is the ICU licensed"](icufaq/index#how-is-icu-licensed)

6
docs/userguide/layoutengine/index.md
View file

@ -91,7 +91,7 @@ points.
A concrete instance of this base class must be written for each target platform.
For a simple example which uses the standard C library to access a TrueType
font, look at the PortableFontInstance class in
[icu/source/test/letest](https://github.com/unicode-org/icu/tree/master/icu4c/source/test/letest)
[icu/source/test/letest](https://github.com/unicode-org/icu/tree/main/icu4c/source/test/letest)
.
The ICU LayoutEngine supports complex text in the following ways:
@ -126,7 +126,7 @@ font. It is written in a single direction (left-to-right or right-to-left), and
is written in a single script. Clients can use ICU's
[Bidi](../transforms/bidi.md) processing to determine the direction of the text
and use the ScriptRun class in
[icu/source/extra/scrptrun](https://github.com/unicode-org/icu/tree/master/icu4c/source/extra/scrptrun)
[icu/source/extra/scrptrun](https://github.com/unicode-org/icu/tree/main/icu4c/source/extra/scrptrun)
to find a run of text in the same script. Since the representation of font
information is application specific, ICU cannot help clients find these runs of
text.
@ -188,7 +188,7 @@ users must draw the bitmaps themselves.
> basic types.
For a more detailed example of how to call the LayoutEngine, look at
[icu/source/test/letest/letest.cpp](https://github.com/unicode-org/icu/tree/master/icu4c/source/test/letest/letest.cpp)
[icu/source/test/letest/letest.cpp](https://github.com/unicode-org/icu/tree/main/icu4c/source/test/letest/letest.cpp)
. This is a simple test used to verify that the LayoutEngine is working
properly. It does not do any complex text rendering.

2
docs/userguide/locale/localizing.md
View file

@ -124,7 +124,7 @@ Features:
7. Source files can be in any charset. Unicode signature byte sequences are recognized automatically (UTF-8/16, SCSU, ...), otherwise the tool takes a charset name on the command line.
Defined at: [icu-docs/master/design/bnf_rb.txt](https://raw.githubusercontent.com/unicode-org/icu-docs/master/design/bnf_rb.txt)
Defined at: [icu-docs/main/design/bnf_rb.txt](https://raw.githubusercontent.com/unicode-org/icu-docs/main/design/bnf_rb.txt)
To use with ICU4C, see the [Resource Bundle APIs](resources#resource-bundle-apis) section of this userguide.

22
docs/userguide/locale/resources.md
View file

@ -260,7 +260,7 @@ valid for the C++ APIs.
> :point_right: **Note**: All the data accessing examples in the following
> sections use ICU's
> [root](https://github.com/unicode-org/icu/blob/master/icu4c/source/data/locales/root.txt)
> [root](https://github.com/unicode-org/icu/blob/main/icu4c/source/data/locales/root.txt)
> resource bundle.
```c
@ -336,7 +336,7 @@ In order to be able to distinguish between resources, one needs to know the type
of the resource at hand. To find this out, use the
`UResType ures_getType(UResourceBundle* resourceBundle)` API, or the C++ analog
`UResType getType(void)`. The `UResType` is an enumeration defined in the
[unicode/ures.h](https://github.com/unicode-org/icu/blob/master/icu4c/source/common/unicode/ures.h)
[unicode/ures.h](https://github.com/unicode-org/icu/blob/main/icu4c/source/common/unicode/ures.h)
header file.
> :point_right: **Note**: Indexes of resources in tables do not necessarily
@ -550,7 +550,7 @@ Gets the number of items in a resource. Simple resources always return size 1.
| C++ | `UResType getType(void)` |
Gets the type of the resource. For a list of resource types, see:
[unicode/ures.h](https://github.com/unicode-org/icu/blob/master/icu4c/source/common/unicode/ures.h)
[unicode/ures.h](https://github.com/unicode-org/icu/blob/main/icu4c/source/common/unicode/ures.h)
| Language | API |
| -------- | ------------------------------------------------ |
@ -580,7 +580,7 @@ tuned.
Resource bundles are written in its source format. Before using them, they must
be compiled to the binary format using the `genrb` utility. Currently supported
source format is a text file. The format is defined in a [formal definition
file](https://github.com/unicode-org/icu-docs/blob/master/design/bnf_rb.txt).
file](https://github.com/unicode-org/icu-docs/blob/main/design/bnf_rb.txt).
This is an example of a resource bundle source file:
@ -667,7 +667,7 @@ root {
```
Binary format is described in the
[uresdata.h](https://github.com/unicode-org/icu/blob/master/icu4c/source/common/uresdata.h)
[uresdata.h](https://github.com/unicode-org/icu/blob/main/icu4c/source/common/uresdata.h)
header file.
### Resources Syntax
@ -745,11 +745,11 @@ aVeryLongString:string {
```
For more examples on syntax, take a look at our resource files for
[locales](https://github.com/unicode-org/icu/blob/master/icu4c/source/data/locales)
[locales](https://github.com/unicode-org/icu/blob/main/icu4c/source/data/locales)
and
[test data](https://github.com/unicode-org/icu/blob/master/icu4c/source/test/testdata),
[test data](https://github.com/unicode-org/icu/blob/main/icu4c/source/test/testdata),
especially at the
[testtypes resource bundle](https://github.com/unicode-org/icu/blob/master/icu4c/source/test/testdata/testtypes.txt).
[testtypes resource bundle](https://github.com/unicode-org/icu/blob/main/icu4c/source/test/testdata/testtypes.txt).
### Making Your Own Resource Bundles
@ -801,10 +801,10 @@ steps:
Rolling out your own data takes some practice, especially if you want to package
it all together. You might want to take a look at how we package data. Good
places to start (except of course ICU's own
[data](https://github.com/unicode-org/icu/blob/master/icu4c/source/data/)) are
[source/test/testdata/](https://github.com/unicode-org/icu/blob/master/icu4c/source/test/testdata/)
[data](https://github.com/unicode-org/icu/blob/main/icu4c/source/data/)) are
[source/test/testdata/](https://github.com/unicode-org/icu/blob/main/icu4c/source/test/testdata/)
and
[source/samples/ufortune/resources/](https://github.com/unicode-org/icu/blob/master/icu4c/source/samples/ufortune/resources/)
[source/samples/ufortune/resources/](https://github.com/unicode-org/icu/blob/main/icu4c/source/samples/ufortune/resources/)
directories.
Also, here is a sample Windows batch file that does compiling and packing of

2
docs/userguide/packaging/index.md
View file

@ -121,7 +121,7 @@ data to be installed and removed without rebuilding ICU. For details, see the
(This section assumes the reader is familiar with ICU version numbers (§) as
covered in the [Design](../design.md) chapter, and filename conventions for
libraries in the
[ReadMe](https://github.com/unicode-org/icu/blob/master/icu4c/readme.html#HowToPackage)
[ReadMe](https://github.com/unicode-org/icu/blob/main/icu4c/readme.html#HowToPackage)
.)
### POSIX Library Names

4
docs/userguide/packaging/plug-ins.md
View file

@ -55,7 +55,7 @@ uninstall themselves before they are removed from memory and unloaded.
The current plugin API is documented as
[icuplug.h](https://unicode-org.github.io/icu-docs/apidoc/released/icu4c/icuplug_8h.html)
Some sample plugins are available at:
[testplug.c](https://github.com/unicode-org/icu/blob/master/icu4c/source/tools/icuinfo/testplug.c)
[testplug.c](https://github.com/unicode-org/icu/blob/main/icu4c/source/tools/icuinfo/testplug.c)
Here is a simple, trivial plugin:
```c
@ -92,7 +92,7 @@ SHOULD call `uplug_setPlugName` to indicate a human readable plugin name.
## Configuration
You can see a sample configuration file here:
[icuplugins_windows_sample.txt](https://github.com/unicode-org/icu/blob/master/icu4c/source/tools/icuinfo/icuplugins_windows_sample.txt)
[icuplugins_windows_sample.txt](https://github.com/unicode-org/icu/blob/main/icu4c/source/tools/icuinfo/icuplugins_windows_sample.txt)
At ICU startup time, the environment variable "ICU_PLUGINS" will be
queried for a directory name. If it is not set, the #define
`DEFAULT_ICU_PLUGINS` will be checked for a default value.

6
docs/userguide/posix.md
View file

@ -107,14 +107,14 @@ naturally the case because the Java language and the JDK use UTF-16.
ICU uses and/or provides direct access to all of the [Unicode
properties](strings/properties.md) which provide a much finer-grained
classification of characters than [C/POSIX character
classes](https://htmlpreview.github.io/?https://github.com/unicode-org/icu-docs/blob/master/design/posix_classes.html).
classes](https://htmlpreview.github.io/?https://github.com/unicode-org/icu-docs/blob/main/design/posix_classes.html).
In C/C++ source code character and string literals, ICU uses only "invariant"
characters. They are the subset of graphic ASCII characters that are almost
always encoded with the same byte values on all systems. (One set of byte values
for ASCII-based systems, and another such set of byte values for EBCDIC
systems.) See
[`utypes.h`](https://github.com/unicode-org/icu/blob/master/icu4c/source/common/unicode/utypes.h)
[`utypes.h`](https://github.com/unicode-org/icu/blob/main/icu4c/source/common/unicode/utypes.h)
for the set of "invariant" characters.
With the use of Unicode, the implementation of many of the Unicode standard
@ -203,7 +203,7 @@ locale's respective character class.
Technical Standard #18: Unicode Regular Expressions](http://www.unicode.org/reports/tr18/#Compatibility_Properties)
and see the mailing list archives for the unicode list (on unicode.org). See
also the ICU design document about [C/POSIX character
classes](https://htmlpreview.github.io/?https://github.com/unicode-org/icu-docs/blob/master/design/posix_classes.html).
classes](https://htmlpreview.github.io/?https://github.com/unicode-org/icu-docs/blob/main/design/posix_classes.html).
#### ICU

2
docs/userguide/strings/characteriterator.md
View file

@ -171,5 +171,5 @@ text. The text and the iteration range are set in the implementing subclasses.
## Additional Sample Code
C/C++: See
[icu4c/source/samples/citer/](https://github.com/unicode-org/icu/blob/master/icu4c/source/samples/citer/)
[icu4c/source/samples/citer/](https://github.com/unicode-org/icu/blob/main/icu4c/source/samples/citer/)
in the ICU source distribution for code samples.

2
docs/userguide/strings/index.md
View file

@ -16,7 +16,7 @@ License & terms of use: http://www.unicode.org/copyright.html
This section explains how to handle Unicode strings with ICU in C and C++.
Sample code is available in the ICU source code library at
[icu/source/samples/ustring/ustring.cpp](https://github.com/unicode-org/icu/blob/master/icu4c/source/samples/ustring/ustring.cpp)
[icu/source/samples/ustring/ustring.cpp](https://github.com/unicode-org/icu/blob/main/icu4c/source/samples/ustring/ustring.cpp)
.
## Text Access Overview

8
docs/userguide/strings/properties.md
View file

@ -32,9 +32,9 @@ processing, and the data is publicly provided and kept up-to-date. See
https://www.unicode.org/ and https://www.unicode.org/main.html for more information.
Sample code is available in the ICU source code library at
[icu4c/source/samples/props/props.cpp](https://github.com/unicode-org/icu/blob/master/icu4c/source/samples/props/props.cpp).
[icu4c/source/samples/props/props.cpp](https://github.com/unicode-org/icu/blob/main/icu4c/source/samples/props/props.cpp).
See also the source code for the [Unicode
browser](https://github.com/unicode-org/icu-demos/tree/master/ubrowse) demo
browser](https://github.com/unicode-org/icu-demos/tree/main/ubrowse) demo
application, which can be used
[online](http://demo.icu-project.org/icu-bin/ubrowse) to browse Unicode
characters with their properties.
@ -226,7 +226,7 @@ change or add them at build-time. This is doable but not easy.
It is done by modifying the Character Database files copied into the ICU source
tree at
[icu4c/source/data/unidata](https://github.com/unicode-org/icu/tree/master/icu4c/source/data/unidata).
[icu4c/source/data/unidata](https://github.com/unicode-org/icu/tree/main/icu4c/source/data/unidata).
Since ICU 49, most of the properties have been combined into one file,
unidata/ppucd.txt (see the [Preparsed
UCD](http://site.icu-project.org/design/props/ppucd) design doc). Some of the
@ -238,7 +238,7 @@ site](http://www.unicode.org/reports/tr44/) for more information). After
modifying one or more of these files, the ICU data needs to be rebuilt, and the
resulting files need to be checked into the ICU source tree. The files are
processed by special ICU tools outside of the normal ICU build. The
[unidata/changes.txt](https://github.com/unicode-org/icu/blob/master/icu4c/source/data/unidata/changes.txt)
[unidata/changes.txt](https://github.com/unicode-org/icu/blob/main/icu4c/source/data/unidata/changes.txt)
file documents the process that has been used for the last several Unicode
version updates; skip the file preparation and API update steps.

2
docs/userguide/strings/stringprep.md
View file

@ -352,7 +352,7 @@ in binary form with data structures optimized for runtime use.
A web application at <http://demo.icu-project.org/icu-bin/idnbrowser>
illustrates the use of IDNA API. The source code for the application is
available at <https://github.com/unicode-org/icu-demos/tree/master/idnbrowser>.
available at <https://github.com/unicode-org/icu-demos/tree/main/idnbrowser>.
## Appendix

6
docs/userguide/strings/utext.md
View file

@ -129,7 +129,7 @@ int countWords(const char *utf8String) {
## UText API Functions
The UText API is declared in the ICU header file
[utext.h](https://github.com/unicode-org/icu/blob/master/icu4c/source/common/unicode/utext.h)
[utext.h](https://github.com/unicode-org/icu/blob/main/icu4c/source/common/unicode/utext.h)
### Opening and Closing.
@ -383,6 +383,6 @@ required.
To fully understand what is required to support a new string type with UText, it
will be necessary to study both the provider function declarations from
[utext.h](https://github.com/unicode-org/icu/blob/master/icu4c/source/common/unicode/utext.h)
[utext.h](https://github.com/unicode-org/icu/blob/main/icu4c/source/common/unicode/utext.h)
and the existing text provider implementations in
[utext.cpp](https://github.com/unicode-org/icu/blob/master/icu4c/source/common/utext.cpp).
[utext.cpp](https://github.com/unicode-org/icu/blob/main/icu4c/source/common/utext.cpp).

2
docs/userguide/transforms/casemappings.md
View file

@ -46,7 +46,7 @@ Shrew".
(uppercase) which form case pairs, but are not used in title case.*
Sample code is available in the ICU source code library at
[icu/source/samples/ustring/ustring.cpp](https://github.com/unicode-org/icu/blob/master/icu4c/source/samples/ustring/ustring.cpp)
[icu/source/samples/ustring/ustring.cpp](https://github.com/unicode-org/icu/blob/main/icu4c/source/samples/ustring/ustring.cpp)
.
Please refer to the following sections in the [The Unicode Standard](http://www.unicode.org/versions/latest/)

2
docs/userguide/transforms/normalization/index.md
View file

@ -108,7 +108,7 @@ invoke `gennorm2 --help`.
gennorm2 starts with no data. If you want to include standard Unicode
Normalization data, use the files in
[{ICU4C}/source/data/unidata/norm2/](https://github.com/unicode-org/icu/tree/master/icu4c/source/data/unidata/norm2)
[{ICU4C}/source/data/unidata/norm2/](https://github.com/unicode-org/icu/tree/main/icu4c/source/data/unidata/norm2)
. You can modify one of them, or provide it together with one or more additional
files that add or remove mappings.

2
docs/userguide/unicode.md
View file

@ -321,7 +321,7 @@ See also <https://www.unicode.org/reports/tr6/> .
Other Unicode encodings have been developed over time for various purposes. Most
of them are implemented in ICU, see
[source/data/mappings/convrtrs.txt](https://github.com/unicode-org/icu/blob/master/icu4c/source/data/mappings/convrtrs.txt)
[source/data/mappings/convrtrs.txt](https://github.com/unicode-org/icu/blob/main/icu4c/source/data/mappings/convrtrs.txt)
1. BOCU-1: Binary-Ordered Compression of Unicode
An encoding of Unicode that is about as compact as SCSU but has a much

2
icu4c/source/data/icu4j-readme.txt
View file

@ -30,7 +30,7 @@ In the following,
For more instructions on downloading and building ICU4C,
see the ICU4C readme at:
https://htmlpreview.github.io/?https://github.com/unicode-org/icu/blob/master/icu4c/readme.html#HowToBuild
https://htmlpreview.github.io/?https://github.com/unicode-org/icu/blob/main/icu4c/readme.html#HowToBuild
(Windows: build as 'x86, Release' otherwise you will have to set 'CFG' differently below.)
*NOTE* You should do a full rebuild after any data changes.

2
icu4c/source/i18n/unicode/numberformatter.h
View file

@ -2203,7 +2203,7 @@ class U_I18N_API NumberFormatterSettings {
* @param usage A `usage` parameter from the units resource. See the
* unitPreferenceData in *source/data/misc/units.txt*, generated from
* `unitPreferenceData` in [CLDR's
* supplemental/units.xml](https://github.com/unicode-org/cldr/blob/master/common/supplemental/units.xml).
* supplemental/units.xml](https://github.com/unicode-org/cldr/blob/main/common/supplemental/units.xml).
* @return The fluent chain.
* @draft ICU 68
*/

2
icu4j/maven/icu4j-charset/pom.xml
View file

@ -21,7 +21,7 @@
<licenses>
<license>
<name>Unicode/ICU License</name>
<url>https://raw.githubusercontent.com/unicode-org/icu/master/icu4c/LICENSE</url>
<url>https://raw.githubusercontent.com/unicode-org/icu/main/icu4c/LICENSE</url>
<distribution>repo</distribution>
</license>
</licenses>

2
icu4j/maven/icu4j-localespi/pom.xml
View file

@ -21,7 +21,7 @@
<licenses>
<license>
<name>Unicode/ICU License</name>
<url>https://raw.githubusercontent.com/unicode-org/icu/master/icu4c/LICENSE</url>
<url>https://raw.githubusercontent.com/unicode-org/icu/main/icu4c/LICENSE</url>
<distribution>repo</distribution>
</license>
</licenses>

2
icu4j/maven/icu4j/pom.xml
View file

@ -26,7 +26,7 @@
<licenses>
<license>
<name>Unicode/ICU License</name>
<url>https://raw.githubusercontent.com/unicode-org/icu/master/icu4c/LICENSE</url>
<url>https://raw.githubusercontent.com/unicode-org/icu/main/icu4c/LICENSE</url>
<distribution>repo</distribution>
</license>
</licenses>

2
tools/cldr/cldr-to-icu/README.txt
View file

@ -25,7 +25,7 @@ CLDR_DIR: This is the path to the to root of standard CLDR sources, below
CLDR_DATA_DIR: The top-level directory for the CLDR production data (typically
the "production" directory in the staging repository). Usually
generated locally or obtained from:
https://github.com/unicode-org/cldr-staging/tree/master/production
https://github.com/unicode-org/cldr-staging/tree/main/production
In Posix systems, it's best to set these as exported shell variables, and any
following instructions assume they have been set accordingly:

6
tools/commit-checker/README.md
View file

@ -41,9 +41,9 @@ Run the tool and save the result into REPORT.md; set fixVersion to the upcoming
--rev-range "release-63-1..upstream/maint/maint-64"
> REPORT.md
If the maintenance branch hasn't been cut yet, use upstream/master as the tip:
If the maintenance branch hasn't been cut yet, use upstream/main as the tip:
--rev-range "release-64-2..upstream/master"
--rev-range "release-64-2..upstream/main"
Note 1: These examples assume that your remote named "upstream" points to unicode-org/icu, the source of truth.
@ -68,4 +68,4 @@ It should be possible to clear the first two sections of the report simply by co
When ready, create a branch and push to your fork so others can view the report easily. Team members should close issues they own that are correctly fixed. Re-generate the report periodically until it comes back clean.
Note: REPORT.md is not intended to be merged back into master.
Note: REPORT.md is not intended to be merged back into main.

4
tools/commit-checker/check.py
View file

@ -92,7 +92,7 @@ def make_commit_wanted(jira_issue):
flag_parser = argparse.ArgumentParser(
description = "Generates a Markdown report for commits on master since the 'latest' tag.",
description = "Generates a Markdown report for commits on main since the 'latest' tag.",
formatter_class = argparse.ArgumentDefaultsHelpFormatter
)
flag_parser.add_argument(
@ -291,7 +291,7 @@ def print_sectionheader(section):
def main():
args = flag_parser.parse_args()
print("TIP: Have you pulled the latest master? This script only looks at local commits.", file=sys.stderr)
print("TIP: Have you pulled the latest main? This script only looks at local commits.", file=sys.stderr)
if not args.jira_username or not args.jira_password:
print("WARNING: Jira credentials not supplied. Sensitive tickets will not be found.", file=sys.stderr)
authenticated = False

2
tools/scripts/cpysearch/readme.txt
View file

@ -12,7 +12,7 @@ cpyscan.pl searches for all files that don't have any copyright
.cpyskip.txt is part of the ignore list. It resides as hidden file on
the top level of the repsoitory. Download the latest from
https://raw.githubusercontent.com/unicode-org/icu/master/.cpyskip.txt
https://raw.githubusercontent.com/unicode-org/icu/main/.cpyskip.txt
more docs on copyright scan at:
http://site.icu-project.org/processes/copyright-scan

2
vendor/double-conversion/pull-from-upstream.sh vendored
View file

@ -4,7 +4,7 @@
if [[ -z $1 ]]; then
echo "Pass the current version tag of double-conversion as the first argument to this script";
echo "To pull the latest changes, use 'master'"
echo "To pull the latest changes, use 'main'"
exit 1;
fi