locale.5: Document character transliteration

See e.g. da_DK for reference.

(Not sure should we actually provide an example here?)

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Marko Myllynen 2015-05-12 16:58:58 +03:00 committed by Michael Kerrisk
parent f863ce4f60
commit 4e3b0c16e1
1 changed files with 28 additions and 3 deletions

View File

@ -249,9 +249,6 @@ The definition starts with the string
in the first column.
The following keywords are allowed:
.\" FIXME The following LC_CTYPE keywords are not documented:
.\" translit_start + translit_end
.\" include
.TP
.I upper
followed by a list of uppercase letters.
@ -460,6 +457,34 @@ for input digits for the locale.
followed by a list of mapping pairs of
alternate separators
for output for the locale.
.TP
.I translit_start
marks the start of the transliteration rules section.
The section can contain the
.I include
keyword in the beginning followed by
locale specific rules and overrides.
Any rule specified in the locale file
will override any rule
copied or included from other files.
In case of duplicate rule definitions in the locale file,
only the first rule is used.
A transliteration rule consist of a character to be transliterated
followed by a list of transliteration targets separated by semicolons.
The first target which can be presented in the target character set
is used, if none of them can be used the
.I default_missing
character will be used instead.
.TP
.I include
in the transliteration rules section includes
a transliteration rule file
(and optionally a repertoire map file)
.
.TP
.I translit_end
marks the end of the transliteration rules.
.PP
The
.B LC_CTYPE