Пакет: icu

PKGDATA(1)			ICU 77.1 Manual			    PKGDATA(1)



NAME
       pkgdata - package data for use by ICU

SYNOPSIS
       pkgdata	[  -h,	-?, --help ] [ -v, --verbose ] [ -c, --copyright | -C,
       --comment comment ] [ -m, --mode mode ] -p, --name  name	 -O,  --bldopt
       options	[  -e,	--entrypoint  name  ] [ -r, --revision version ] [ -F,
       --rebuild ] [ -I, --install ] [ -s, --sourcedir source ] [ -d,  --dest‐
       dir destination ] [ -T, --tempdir directory ] [ file ...	 ]

DESCRIPTION
       pkgdata	takes  a set of data files and packages them for use by ICU or
       applications that use ICU. The typical reason to	 package  files	 using
       pkgdata	is  to make their distribution easier and their loading by ICU
       faster and less consuming of limited system resources such as file  de‐
       scriptors.   Packaged  data  also  allow applications to be distributed
       with fewer resource files, or even  with	 none  at  all	if  they  link
       against the packaged data directly.

       pkgdata	supports  a few different methods of packaging data that serve
       different purposes.

       The default packaging mode is common, or archive.  In  this  mode,  the
       different  data files are bundled together as an architecture-dependent
       file that can later be memory mapped for use by ICU. Data packaged  us‐
       ing  this  mode	will  be  looked up under the ICU data directory. Such
       packaging is easy to use for applications resource bundles,  for	 exam‐
       ple,  as	 long  as the application can install the packaged file in the
       ICU data directory.

       Another packaging mode is the dll, or library,  mode,  where  the  data
       files are compiled into a shared library. ICU used to be able to dynam‐
       ically load these shared libraries, but as of ICU 2.0, such support has
       been removed. This mode is still useful for two main purposes: to build
       ICU itself, as the ICU data is packaged as a shared library by default;
       and  to	build resource bundles that are linked to the application that
       uses them. Such resource bundles can then be placed anywhere where  the
       system's	 dynamic  linker will be looking for shared libraries, instead
       of being forced to live inside the ICU data directory.

       The static packaging mode is similar to the shared library  one	except
       that it produces a static library.

       Finally,	 pkgdata  supports  a  files mode which simply copies the data
       files instead of packaging them as a single file or library. This  mode
       is  mainly  intended  to	 provide support for building ICU before it is
       packaged as separate small packages  for	 distribution  with  operating
       systems such as Debian GNU/Linux for example. Please refer to the pack‐
       aging documentation in the ICU source distribution for further informa‐
       tion on the use of this mode.

       pkgdata	builds,	 packages,  installs,  or  cleans the appropriate data
       based on the options given without the need to call GNU make anymore.

OPTIONS
       -h, -?, --help
	      Print help about usage and exit.

       -v, --verbose
	      Display extra informative messages during execution.

       -c, --copyright
	      Include a copyright notice in the binary data.

       -C, --comment comment
	      Includes the specified comment in the resulting data instead  of
	      the ICU copyright notice.

       -m, --mode mode
	      Set  the	packaging  mode	 to be used by pkgdata.	 The different
	      modes and their meaning are explained in the DESCRIPTION section
	      above. The valid mode names are common (or archive), dll (or li‐
	      brary), and files.

       -O, --bldopt options
	      Specify options for the builder. The builder is used  internally
	      by  pkgdata  to generate the correct packaged file. Such options
	      include, but are not  limited  to,  setting  variables  used  by
	      make(1) during the build of the packaged file. Note: If icu-con‐
	      fig is available, then this option is not needed.

       -p, --name name
	      Set the packaged file name to name.  This name is also  used  as
	      the  default  entry  point  name after having been turned into a
	      valid C identifier.

       -e, --entrypoint name
	      Set the data entry point (used for linking against the data in a
	      shared  library  form) to name.  The default entry point name is
	      the name set by the -n, --name option.

       -r, --revision version
	      Enable versioning of the shared library produced in dll, or  li‐
	      brary,  mode.  The  version  number  has	the  format  major.mi‐
	      nor.patchlevel and all parts except for major are	 optional.  If
	      only major is supplied then the version is assumed to be major.0
	      for versioning purposes.

       -F, --rebuild
	      Force the rebuilding of all data and their repackaging.

       -I, --install
	      Install the packaged file (or all the files in the files	mode).
	      If the variable DESTDIR is set it will be used for installation.

       -s, --sourcedir source
	      Set  the	source directory to source.  The default source direc‐
	      tory is the current directory.

       -d, --destdir destination
	      Set the destination directory to destination.  The default  des‐
	      tination directory is the current directory.

       -T, --tempdir directory
	      Set the directory used to generate temporary files to directory.
	      The default temporary directory is the same as  the  destination
	      directory as set by the -d, --destdir option.

AUTHORS
       Steven Loomis
       Yves Arrouye

VERSION
       77.1

COPYRIGHT
       Copyright (C) 2000-2009 IBM, Inc. and others.




ICU MANPAGE			6 February 2009			    PKGDATA(1)

GENCFU(1)			ICU 77.1 Manual			     GENCFU(1)



NAME
       gencfu - Generates Unicode Confusable data files

SYNOPSIS
       gencfu  [  -h, -?, --help ] [ -V, --version ] [ -c, --copyright ] [ -v,
       --verbose ] [ -d, --destdir destination ] [ -i, --icudatadir  directory
       ]  -r, --rules rule-file -w, --wsrules whole-script-rule-file -o, --out
       output-file

DESCRIPTION
       gencfu reads confusable character definitions in the input file,	 which
       are plain text files containing confusable character definitions in the
       input format defined by Unicode UAX39 for the files confusables.txt and
       confusablesWholeScript.txt.  This source (.txt) format is also accepted
       by ICU spoof detectors.	The files must be  encoded  in	utf-8  format,
       with  or without a BOM.	Normally the output data file has the .cfu ex‐
       tension.

OPTIONS
       -h, -?, --help
	      Print help about usage and exit.

       -V, --version
	      Print the version of gencfu and exit.

       -c, --copyright
	      Embeds the standard ICU copyright into the output-file.

       -v, --verbose
	      Display extra informative messages during execution.

       -d, --destdir destination
	      Set the destination directory of the output-file to destination.

       -i, --icudatadir directory
	      Look for any necessary ICU data files in directory.   For	 exam‐
	      ple,  the file pnames.icu must be located when ICU's data is not
	      built as a shared library.  The default ICU  data	 directory  is
	      specified by the environment variable ICU_DATA.  Most configura‐
	      tions of ICU do not require this argument.

       -r, --rules rule-file
	      The source file to read.

       -w, --wsrules whole-script-rule-file
	      The whole script source file to read.

       -o, --out output-file
	      The output data file to write.

VERSION
       1.0

COPYRIGHT
       Copyright (C) 2009 International Business Machines Corporation and oth‐
       ers



ICU MANPAGE			  24 May 2009			     GENCFU(1)

GENCNVAL(1)			ICU 77.1 Manual			   GENCNVAL(1)



NAME
       gencnval - compile the converters aliases file

SYNOPSIS
       gencnval [ -h, -?, --help ] [ -v, --verbose ] [ -c, --copyright ] [ -s,
       --sourcedir source ] [ -d, --destdir destination ] [ converterfile ]

DESCRIPTION
       gencnval converts the ICU aliases file converterfile  into  the	binary
       file  cnvalias.icu.  This binary file can then be read directly by ICU,
       or used by pkgdata(1) for incorporation into a larger  archive  or  li‐
       brary.

       If  converterfile is not provided, the default ICU convrtrs.txt file is
       used.

OPTIONS
       -h, -?, --help
	      Print help about usage and exit.

       -v, --verbose
	      Display verbose output. This information can include information
	      about conflicting aliases and the converters the aliases resolve
	      to.

       -c, --copyright
	      Include a copyright notice in the binary data.

       -s, --sourcedir source
	      Set the source directory to source.  The default	source	direc‐
	      tory is specified by the environment variable ICU_DATA.

       -d, --destdir destination
	      Set  the destination directory to destination.  The default des‐
	      tination directory is  specified	by  the	 environment  variable
	      ICU_DATA.

ENVIRONMENT
       ICU_DATA	 Specifies  the	 directory  containing	ICU  data. Defaults to
		 /usr/share/icu/77.1/.	Some tools in ICU depend on the	 pres‐
		 ence of the trailing slash. It is thus important to make sure
		 that it is present if ICU_DATA is set.

FILES
       icu/source/data/mappings/convrtrs.txt   Description of ICU's converters
					       and  their  aliases.  This data
					       file is not normally installed,
					       and  it	is available as a part
					       of ICU source code.

VERSION
       77.1

COPYRIGHT
       Copyright (C) 2000-2004 IBM, Inc. and others.

SEE ALSO
       pkgdata(1)



ICU MANPAGE			 11 March 2004			   GENCNVAL(1)

GENRB(1)			ICU 77.1 Manual			      GENRB(1)



NAME
       genrb - compile a resource bundle

SYNOPSIS
       genrb  [	 -h,  -?,  --help  ] [ -V, --version ] [ -v, --verbose ] [ -e,
       --encoding encoding  ]  [  -j,  --write-java  [	encoding  ]  ]	[  -s,
       --sourcedir  source  ] [ -d, --destdir destination ] [ -i, --icudatadir
       directory ] bundle ...

DESCRIPTION
       genrb converts the resource bundle source files passed on  the  command
       line  to their binary form or to a Java source file for use with ICU4J.
       The resulting binary files have a .res extension while resource	bundle
       source  files typically have a .txt extension. Java source files have a
       java extension and follow the ICU4J naming conventions.

       It is customary to name the resource bundles by their locale name, i.e.
       to  use a local identifier for the bundle filename, e.g.	 ja_JP.txt for
       Japanese (Japan) data, or root.txt for the root bundle.	In  any	 case,
       genrb  will  produce  a	file whose base name is the name of the locale
       found in the resource file, not the base name of the resource file  it‐
       self.

       The binary files can be read directly by ICU, or used by pkgdata(1) for
       incorporation into a larger archive or library.

OPTIONS
       -h, -?, --help
	      Print help about usage and exit.

       -V, --version
	      Print the version of genrb and exit.

       -v, --verbose
	      Display extra informative messages during execution.

       -e, --encoding encoding
	      Set the encoding used to read input files to encoding.  The  de‐
	      fault  encoding  is  the	invariant  (subset of ASCII or EBCDIC)
	      codepage for the system (see section INVARIANT CHARACTERS).  The
	      encodings	 UTF-8,	 UTF-16BE,  and UTF-16LE are automatically de‐
	      tected if a byte order mark (BOM) is present.

       -j, --write-java [ encoding ]
	      Generate a Java source code for use with ICU4J. An optional  en‐
	      coding for the Java file can be given.

       -s, --sourcedir source
	      Set  the	source directory to source.  The default source direc‐
	      tory is specified by the environment variable ICU_DATA,  or  the
	      location set when ICU was built if ICU_DATA is not set.

       -d, --destdir destination
	      Set  the destination directory to destination.  The default des‐
	      tination directory is  specified	by  the	 environment  variable
	      ICU_DATA	or  is the location set when ICU was built if ICU_DATA
	      is not set.

       -i, --icudatadir directory
	      Look for any necessary ICU data files in directory.   For	 exam‐
	      ple,  when  processing collation overrides, the file ucadata.dat
	      must be located.	The default ICU data directory is specified by
	      the environment variable ICU_DATA.

INVARIANT CHARACTERS
       The  invariant  character  set consists of the following set of charac‐
       ters, expressed as  a  standard	POSIX  regular	expression:  [a-z]|[A-
       Z]|[0-9]|_| |+|-|*|/.  This is the set which is guaranteed to be avail‐
       able regardless of code page.

ENVIRONMENT
       ICU_DATA	 Specifies the directory  containing  ICU  data.  Defaults  to
		 /usr/share/icu/77.1/.	 Some tools in ICU depend on the pres‐
		 ence of the trailing slash. It is thus important to make sure
		 that it is present if ICU_DATA is set.

VERSION
       77.1

COPYRIGHT
       Copyright (C) 2000-2002 IBM, Inc. and others.

SEE ALSO
       derb(1)
       pkgdata(1)



ICU MANPAGE			 16 April 2002			      GENRB(1)

MAKECONV(1)			ICU 77.1 Manual			   MAKECONV(1)



NAME
       icuexportdata  -	 Writes	 text  files with Unicode properties data from
       ICU.



ICU MANPAGE			 12 June 2021			   MAKECONV(1)

DERB(1)				ICU 77.1 Manual			       DERB(1)



NAME
       derb - disassemble a resource bundle

SYNOPSIS
       derb [ -h, -?, --help ] [ -V, --version ] [ -v, --verbose ] [ -e, --en‐
       coding encoding ] [ --bom  ]  [	-t,  --truncate	 [  size  ]  ]	[  -s,
       --sourcedir  source  ] [ -d, --destdir destination ] [ -i, --icudatadir
       directory ] [ -c, --to-stdout ] bundle ...

DESCRIPTION
       derb reads the compiled resource bundle files  passed  on  the  command
       line and write them back in text form.  The resulting text files have a
       .txt extension while compiled resource bundle  source  files  typically
       have a .res extension.

       It is customary to name the resource bundles by their locale name, i.e.
       to use a local identifier for the bundle filename, e.g.	ja_JP.res  for
       Japanese	 (Japan) data, or root.res for the root bundle.	 This is espe‐
       cially important for derb since the locale name is not  accessible  di‐
       rectly  from  the compiled resource bundle, and to know which locale to
       ask for when opening the bundle.	 derb will produce a file  whose  base
       name  is	 the  base  name of the compiled resource file itself.	If the
       --to-stdout, -c option is used, however, the text will  be  written  on
       the standard output.

OPTIONS
       -h, -?, --help
	      Print help about usage and exit.

       -V, --version
	      Print the version of derb and exit.

       -v, --verbose
	      Display extra informative messages during execution.

       -A, --suppressAliases
	      Don't follow aliases when producing output.

       -e, --encoding encoding
	      Set  the	encoding  used to write output files to encoding.  The
	      default encoding is the invariant (subset of  ASCII  or  EBCDIC)
	      codepage for the system (see section INVARIANT CHARACTERS).  The
	      choice of the encoding does not affect the data, just their rep‐
	      resentation. Characters that cannot be represented in the encod‐
	      ing will be represented using \uhhhh escape sequences.

       --bom  Write a byte order mark (BOM) at the beginning of the file.

       -l, --locale locale
	      Set the locale for the resource bundle, which is	used  both  in
	      the generated text and as the base name of the output file.

       -t, --truncate [ size ]
	      Truncate	individual  resources (strings or binary data) to size
	      bytes. The default if size is not specified is 80 bytes.

       -s, --sourcedir source
	      Set the source directory to source.  The default	source	direc‐
	      tory  is the current directory.  If - is passed for source, then
	      the bundle will be looked for in its default location, specified
	      by the ICU_DATA environment variable (or defaulting to the loca‐
	      tion set when ICU was built if ICU_DATA is not set).

       -d, --destdir destination
	      Set the destination directory to destination.  The default  des‐
	      tination	directory  is  specified  by  the environment variable
	      ICU_DATA or is the location set when ICU was built  if  ICU_DATA
	      is not set.

       -i, --icudatadir directory
	      Look  for	 any necessary ICU data files in directory.  For exam‐
	      ple, when processing collation overrides, the  file  ucadata.dat
	      must be located.	The default ICU data directory is specified by
	      the environment variable ICU_DATA.

       -c, --to-stdout
	      Write the disassembled bundle on standard output instead of into
	      a file.

CAVEATS
       When  the  option --bom is used, the character U+FEFF is written in the
       destination encoding regardless of whether it is a Unicode  transforma‐
       tion  format (UTF) or not.  This option should only be used with an UTF
       encoding, as byte order marks are not meaningful for other encodings.

INVARIANT CHARACTERS
       The invariant character set consists of the following  set  of  charac‐
       ters,  expressed	 as  a	standard  POSIX	 regular expression: [a-z]|[A-
       Z]|[0-9]|_| |+|-|*|/.  This is the set which is guaranteed to be avail‐
       able regardless of code page.

ENVIRONMENT
       ICU_DATA	 Specifies  the	 directory  containing	ICU  data. Defaults to
		 /usr/share/icu/77.1/.	Some tools in ICU depend on the	 pres‐
		 ence of the trailing slash. It is thus important to make sure
		 that it is present if ICU_DATA is set.

AUTHORS
       Vladimir Weinstein
       Yves Arrouye

VERSION
       1.0

COPYRIGHT
       Copyright (C) 2002 IBM, Inc. and others.

SEE ALSO
       genrb(1)




ICU MANPAGE			  7 Mar 2014			       DERB(1)

MAKECONV(1)			ICU 77.1 Manual			   MAKECONV(1)



NAME
       makeconv - compile a converter table

SYNOPSIS
       makeconv [ -h, -?, --help ] [ -c, --copyright ] [ -v, --verbose ] [ -d,
       --destdir destination ] convertertable ...

DESCRIPTION
       makeconv converts the ICU converter table convertertable into a	binary
       file.  The binary file has the same base name as convertertable but has
       a .cnv extension (instead of the typical .ucm extension of the convert‐
       ertable	file).	 This binary file can then be read directly by ICU, or
       used by pkgdata(1) for incorporation into a larger archive or library.

       The convertertable must be in the ICU ucm  (Unicode  Codepage  Mapping)
       format  in  order  to be understood by makeconv.	 The ICU ucm format is
       similar to the IBM NLTC upmap/tpmap/rpmap files.	 Comments in the  con‐
       vertertable  are	 handled as follows. If a comment (starting with a `#'
       sign) that is after some text does contain the fallback	indicator  `|'
       then  only  the	text starting with the `#' sign, and ending before the
       `|' sign, is ignored.  Otherwise, or if the comment is the first	 thing
       on  the	line, the comment runs up to the end of the line. This special
       handling of comments is to accommodate the practice of putting fallback
       information in comments in the strict IBM NLTC ucmap format.

       Note that new converters will be automatically found by ICU after their
       installation in ICU's data directory. They do not need to be listed  in
       the convrtrs.txt(5) converters aliases file in order to be available to
       applications using ICU.	They do need to be listed there if  one	 wants
       to give them aliases, or tags, though.

OPTIONS
       -h, -?, --help
	      Print help about usage and exit.

       -c, --copyright
	      Include a copyright notice in the binary data.

       -v, --verbose
	      Display extra informative messages during execution.

       -d, --destdir destination
	      Set  the destination directory to destination.  The default des‐
	      tination directory is  specified	by  the	 environment  variable
	      ICU_DATA.

CAVEATS
       If  an  existing	 converter table is changed and recompiled using make‐
       conv, the resulting binary file must be packaged in the same  way  that
       it  was packaged initially. For example, if converters were grouped to‐
       gether in an archive or a library with pkgdata(1), then the archive  or
       library	must be rebuilt with the new binary file.  A standalone binary
       converter file will not take precedence over a packaged one.

ENVIRONMENT
       ICU_DATA	 Specifies the directory  containing  ICU  data.  Defaults  to
		 /usr/share/icu/77.1/.	 Some tools in ICU depend on the pres‐
		 ence of the trailing slash. It is thus important to make sure
		 that it is present if ICU_DATA is set.

VERSION
       77.1

COPYRIGHT
       Copyright (C) 2000 IBM, Inc. and others.

SEE ALSO
       convrtrs.txt(5)
       pkgdata(1)




ICU MANPAGE			 16 April 2002			   MAKECONV(1)

UCONV(1)			ICU 77.1 Manual			      UCONV(1)



NAME
       uconv - convert data from one encoding to another

SYNOPSIS
       uconv  [	 -h,  -?,  --help  ]  [ -V, --version ] [ -s, --silent ] [ -v,
       --verbose ] [ -l, --list | -l, --list-code code | --default-code |  -L,
       --list-transliterators	]  [  --canon  ]  [  -x	 transliteration  ]  [
       --to-callback callback | -c ] [	--from-callback	 callback  |  -i  ]  [
       --callback callback ] [ --fallback | --no-fallback ] [ -b, --block-size
       size ] [ -f, --from-code encoding  ]  [	-t,  --to-code	encoding  ]  [
       --add-signature	]  [  --remove-signature  ]  [	-o,  --output file ] [
       file...	]

DESCRIPTION
       uconv converts, or transcodes, each given file (or its  standard	 input
       if no file is specified) from one encoding to another.  The transcoding
       is done using Unicode as a pivot encoding  (i.e.	 the  data  are	 first
       transcoded  from their original encoding to Unicode, and then from Uni‐
       code to the destination encoding).

       If an encoding is not specified or is -, the default encoding is	 used.
       Thus,  calling  uconv with no encoding provides an easy way to validate
       and sanitize data files for further consumption by tools requiring data
       in the default encoding.

       When  calling  uconv, it is possible to specify callbacks that are used
       to handle invalid characters in the input, or characters that cannot be
       transcoded  to  the  destination encoding. Some encodings, for example,
       offer a default substitution character that can be  used	 to  represent
       the occurrence of such characters in the input. Other callbacks offer a
       useful visual representation of the invalid data.

       uconv can also run the  specified  transliteration  on  the  transcoded
       data,  in  which	 case  transliteration	will happen as an intermediate
       step, after the data have been transcoded to Unicode.  The translitera‐
       tion  can be either a list of semicolon-separated transliterator names,
       or an arbitrarily complex set of rules in the ICU transliteration rules
       format.

       For  transcoding	 purposes,  uconv options are compatible with those of
       iconv(1), making it easy to replace it in scripts. It is not  necessar‐
       ily  the	 case,	however, that the encoding names used by uconv and ICU
       are the same as the ones used by iconv(1).  Also, options that  provide
       informational data, such as the -l, --list one offered by some iconv(1)
       variants such as GNU's, produce data in a slightly different and easier
       to parse format.

OPTIONS
       -h, -?, --help
	      Print help about usage and exit.

       -V, --version
	      Print the version of uconv and exit.

       -s, --silent
	      Suppress messages during execution.

       -v, --verbose
	      Display extra informative messages during execution.

       -l, --list
	      List all the available encodings and exit.

       -l, --list-code code
	      List  only  the  code encoding and exit. If code is not a proper
	      encoding, exit with an error.

       --default-code
	      List only the name of the default encoding and exit.

       -L, --list-transliterators
	      List all the available transliterators and exit.

       --canon
	      If used with -l, --list or --default-code, the list of encodings
	      is  produced  in	a  format compatible with convrtrs.txt(5).  If
	      used with -L, --list-transliterators, print only one transliter‐
	      ator name per line.

       -x transliteration
	      Run  the	given  transliteration on the transcoded Unicode data,
	      and use the transliterated data as input for the transcoding  to
	      the destination encoding.

       --to-callback callback
	      Use  callback  to handle characters that cannot be transcoded to
	      the destination encoding. See section CALLBACKS for  details  on
	      valid callbacks.

       -c     Omit  invalid characters from the output.	 Same as --to-callback
	      skip.

       --from-callback callback
	      Use callback to handle characters that cannot be transcoded from
	      the  original  encoding.	See  section  CALLBACKS for details on
	      valid callbacks.

       -i     Ignore invalid sequences in the input.  Same as  --from-callback
	      skip.

       --callback callback
	      Use callback to handle both characters that cannot be transcoded
	      from  the	 original  encoding  and  characters  that  cannot  be
	      transcoded  to  the  destination encoding. See section CALLBACKS
	      for details on valid callbacks.

       --fallback
	      Use the fallback mapping when transcoding from  Unicode  to  the
	      destination encoding.

       --no-fallback
	      Do not use the fallback mapping when transcoding from Unicode to
	      the destination encoding.	 This is the default.

       -b, --block-size size
	      Read input in blocks of size bytes at a time. The default	 block
	      size is 4096.

       -f, --from-code encoding
	      Set the original encoding of the data to encoding.

       -t, --to-code encoding
	      Transcode the data to encoding.

       --add-signature
	      Add  a  U+FEFF  Unicode  signature character (BOM) if the output
	      charset supports it and does not add one anyway.

       --remove-signature
	      Remove a U+FEFF Unicode signature character (BOM).

       -o, --output file
	      Write the transcoded data to file.

CALLBACKS
       uconv supports specifying callbacks to handle invalid  data.  Callbacks
       can be set for both directions of transcoding: from the original encod‐
       ing to Unicode, with the --from-callback option, and  from  Unicode  to
       the destination encoding, with the --to-callback option.

       The  following is a list of valid callback names, along with a descrip‐
       tion of their behavior. The list of  callbacks  actually	 supported  by
       uconv is displayed when it is called with -h, --help.

       substitute	Write  the encoding's substitute sequence, or the Uni‐
			code replacement character U+FFFD when transcoding  to
			Unicode.

       skip		Ignore the invalid data.

       stop		Stop  with  an	error  when encountering invalid data.
			This is the default callback.

       escape		Same as escape-icu.

       escape-icu	Replace the missing characters with a  string  of  the
			format %Uhhhh for plane 0 characters, and %Uhhhh%Uhhhh
			for planes 1 and above characters, where hhhh  is  the
			hexadecimal value of one of the UTF-16 code units rep‐
			resenting the character. Characters from planes 1  and
			above  are  written as a pair of UTF-16 surrogate code
			units.

       escape-java	Replace the missing characters with a  string  of  the
			format \uhhhh for plane 0 characters, and \uhhhh\uhhhh
			for planes 1 and above characters, where hhhh  is  the
			hexadecimal value of one of the UTF-16 code units rep‐
			resenting the character. Characters from planes 1  and
			above  are  written as a pair of UTF-16 surrogate code
			units.

       escape-c		Replace the missing characters with a  string  of  the
			format	\uhhhh	for plane 0 characters, and \Uhhhhhhhh
			for planes 1 and above characters, where hhhh and hhh‐
			hhhhh  are the hexadecimal values of the Unicode code‐
			point.

       escape-xml	Same as escape-xml-hex.

       escape-xml-hex	Replace the missing characters with a  string  of  the
			format	&#xhhhh;,  where hhhh is the hexadecimal value
			of the Unicode codepoint.

       escape-xml-dec	Replace the missing characters with a  string  of  the
			format &#nnnn;, where nnnn is the decimal value of the
			Unicode codepoint.

       escape-unicode	Replace the missing characters with a  string  of  the
			format	{U+hhhh},  where hhhh is the hexadecimal value
			of the Unicode codepoint.  That hexadecimal string  is
			of  variable  length  and  can use from 4 to 6 digits.
			This is the format universally used to denote  a  Uni‐
			code  codepoint	 in the literature, delimited by curly
			braces for easy recognition of those substitutions  in
			the output.

EXAMPLES
       Convert data from a given encoding to the platform encoding:

	   $ uconv -f encoding

       Check if a file contains valid data for a given encoding:

	   $ uconv -f encoding -c file >/dev/null

       Convert	a UTF-8 file to a given encoding and ensure that the resulting
       text is good for any version of HTML:

	   $ uconv -f utf-8 -t encoding \
	       --callback escape-xml-dec file

       Display the names of the Unicode code points in a UTF-file:

	   $ uconv -f utf-8 -x any-name file

       Print the name of a Unicode code point whose value is known (U+30AB  in
       this example):

	   $ echo '\u30ab' | uconv -x 'hex-any; any-name'; echo
	   {KATAKANA LETTER KA}{LINE FEED}
	   $

       (The  names  are delimited by curly braces.  Also, the name of the line
       terminator is also displayed.)

       Normalize UTF-8 data using Unicode NFKC, remove all control characters,
       and map Katakana to Hiragana:

	   $ uconv -f utf-8 -t utf-8 \
		 -x '::nfkc; [:Cc:] >; ::katakana-hiragana;'

CAVEATS AND BUGS
       uconv does report errors as occurring at the first invalid byte encoun‐
       tered. This may be confusing to users of GNU  iconv(1),	which  reports
       errors  as  occurring  at  the  first  byte of an invalid sequence. For
       multi-byte character sets or encodings, this means that uconv error po‐
       sitions	may be at a later offset in the input stream than would be the
       case with GNU iconv(1).

       The reporting of error positions when a transliterator is used  may  be
       inaccurate  or  unavailable, in which case uconv will report the offset
       in the output stream at which the error occurred.

AUTHORS
       Jonas Utterstroem
       Yves Arrouye

VERSION
       77.1

COPYRIGHT
       Copyright (C) 2000-2005 IBM, Inc. and others.

SEE ALSO
       iconv(1)



ICU MANPAGE			  2005-jul-1			      UCONV(1)

GENDICT(1)			ICU 77.1 Manual			    GENDICT(1)



NAME
       gendict - Compiles word list into ICU string trie dictionary

SYNOPSIS
       gendict [ --uchars | --bytes --transform transform ] [ -h, -?, --help ]
       [ -V, --version ] [ -c, --copyright ] [ -v, --verbose ] [  -i,  --icud‐
       atadir directory ]  input-file  output-file

DESCRIPTION
       gendict	reads  the word list from dictionary-file and creates a string
       trie dictionary file. Normally this data file has the .dict extension.

       Words begin at the beginning of a line and are terminated by the	 first
       whitespace.  Lines that begin with whitespace are ignored.

OPTIONS
       -h, -?, --help
	      Print help about usage and exit.

       -V, --version
	      Print the version of gendict and exit.

       -c, --copyright
	      Embeds the standard ICU copyright into the output-file.

       -v, --verbose
	      Display extra informative messages during execution.

       -i, --icudatadir directory
	      Look  for	 any necessary ICU data files in directory.  For exam‐
	      ple, the file pnames.icu must be located when ICU's data is  not
	      built  as	 a  shared library.  The default ICU data directory is
	      specified by the environment variable ICU_DATA.  Most configura‐
	      tions of ICU do not require this argument.

       --uchars
	      Set  the	output	trie  type  to	UChar. Mutually exclusive with
	      --bytes.

       --bytes
	      Set the output trie  type	 to  Bytes.  Mutually  exclusive  with
	      --uchars.

       --transform
	      Set  the	transform type. Should only be specified with --bytes.
	      Currently supported transforms are:  offset-<hex-number>,	 which
	      specifies	 an  offset to subtract from all input characters.  It
	      should be noted that the offset transform also  maps  U+200D  to
	      0xFF and U+200C to 0xFE, in order to offer compatibility to lan‐
	      guages that require these characters.  A transform must be spec‐
	      ified  for a bytes trie, and when applied to the non-value char‐
	      acters in the input-file must produce output  between  0x00  and
	      0xFF.

	input-file
	      The source file to read.

	output-file
	      The file to write the output dictionary to.

CAVEATS
       The  input-file is assumed to be encoded in UTF-8.  The integers in the
       input-file that are used as values must be made	up  of	ASCII  digits.
       They  may be specified either in hex, by using a 0x prefix, or in deci‐
       mal.  Either --bytes or --uchars must be specified.

ENVIRONMENT
       ICU_DATA	 Specifies the directory  containing  ICU  data.  Defaults  to
		 /usr/share/icu/77.1/.	 Some tools in ICU depend on the pres‐
		 ence of the trailing slash. It is thus important to make sure
		 that it is present if ICU_DATA is set.

AUTHORS
       Maxime Serrano

VERSION
       1.0

COPYRIGHT
       Copyright (C) 2012 International Business Machines Corporation and oth‐
       ers

SEE ALSO
       http://www.icu-project.org/userguide/boundaryAnalysis.html




ICU MANPAGE			  1 June 2012			    GENDICT(1)

ICU-CONFIG(1)			ICU 77.1 Manual			 ICU-CONFIG(1)



NAME
       icu-config - output ICU build options

SYNOPSIS
       icu-config  [  --bindir	]  [  --cc  ]  [  --cflags  ] [ --cppflags ] [
       --cppflags-searchpath ] [ --cxx ] [ --cxxflags ] [ --detect-prefix ]  [
       --exec-prefix  ]	 [  --exists ] [ --help, -?, --usage ] [ --icudata ] [
       --icudata-install-dir ] [ --icudata-mode ] [ --icudatadir ] [  --invoke
       ]  [  --invoke=prog  ]  [  --ldflags  ]	[ --ldflags-libsonly ] [ --ld‐
       flags-searchpath ] [ --ldflags-system ] [ --ldflags-icuio ] [  --mandir
       ] [ --prefix ] [ --prefix=prefix ] [ --sbindir ] [ --shared-datadir ] [
       --sysconfdir ] [ --unicode-version ] [ --version ] [ --incfile ]




DESCRIPTION
       icu-config simplifies the task of building and linking against  ICU  as
       compared to manually configuring user makefiles or equivalent.  Because
       icu-config is an executable script, it also solves the problem  of  lo‐
       cating  the  ICU	 libraries and headers, by allowing the system PATH to
       locate it.

EXAMPLES
       icu-config can be used without a makefile. The command  line  below  is
       sufficient for building a single-file c++ program against ICU. (For ex‐
       ample, icu/source/samples/props/props.cpp)

	      `icu-config --cxx	 --cxxflags  --cppflags	 --ldflags`  -o	 props
	      props.cpp

       More  commonly,	icu-config  will be called from within a makefile, and
       used to set up variables. The following example also builds  the	 props
       example.

	      CC=$(shell icu-config --cc)

	      CXX=$(shell icu-config --cxx)

	      CPPFLAGS=$(shell icu-config --cppflags)

	      CXXFLAGS=$(shell icu-config --cxxflags)

	      LDFLAGS =$(shell icu-config --ldflags)

	      all: props

	      props.o: props.cpp

       make(1) will automatically use the above variables.

OPTIONS
       --bindir
	      Prints  the binary (executable) directory path. Normally equiva‐
	      lent to 'bin'.  ICU user-executable applications and scripts are
	      found here.

       --cc   Print  the  C  compiler  used.  Equivalent to the $(CC) Makefile
	      variable.

       --cflags
	      Print the C compiler flags. Equivalent to the $(CFLAGS) Makefile
	      variable.	  Does NOT include preprocessor directives such as in‐
	      clude path or defined symbols. Examples include  debugging  (-g)
	      and optimization flags

       --cppflags
	      Print  the  C  preprocessor flags. Equivalent to the $(CPPFLAGS)
	      Makefile variable. Examples are -I include paths	and -D	define
	      directives.

       --cppflags-searchpath
	      Print  the  C  preprocessor  flags,  as above but only -I search
	      paths.

       --cxx  Print the C++ compiler. Equivalent to the $(CXX) Makefile	 vari‐
	      able.

       --cxxflags
	      Print  the  C++  compiler	 flags.	 Equivalent to the $(CXXFLAGS)
	      Makefile variable.

       --detect-prefix
	      If ICU has been moved from its  installed	 location,  prepending
	      this  flag  to other icu-config calls will attempt to locate ICU
	      relative to where the icu-config script has been located. Can be
	      used  as	a  last-chance effort if the ICU install has been dam‐
	      aged.

       --exec-prefix
	      Print the prefix used for executable program  directories	 (such
	      as bin, sbin, etc). Normally the same as the prefix.

       --exists
	      Script  will return with a successful (0) status if ICU seems to
	      be installed and located correctly, otherwise an	error  message
	      and nonzero status will be displayed.

       --help, -?,--usage
	      Print a help and usage message.

       --icudata
	      Print  the shortname of the ICU data file. This does not include
	      any suffix such as .dat, .dll, .so, .lib, .a, etc	 nor  does  it
	      include prefixes such as 'lib'.  It may be in the form icudt21b

       --icudata-install-dir
	      Print the directory where ICU packaged data should be installed.
	      Can use as pkgdata(1)'s --install option.

       --icudata-mode
	      Print the default ICU pkgdata mode, such as dll or common.   Can
	      use as pkgdata(1)'s --mode option.

       --icudatadir
	      Print  the  path	to  packaged  archive  data.  (should be where
	      $ICU_DATA or equivalent default path points.)  Will NOT point to
	      the libdir.

       --invoke
	      If ICU is not installed in a location where the operating system
	      will locate its shared libraries, this  option  will  print  out
	      commands	so  as to set the appropriate environment variables to
	      load ICU's shared libraries. For	example,  on  many  systems  a
	      variable named LD_LIBRARY_PATH or equivalent must be set.

       --invoke=prog
	      Same  as the --invoke option, except includes options for invok‐
	      ing a program named prog.	 If prog is the name of an  ICU	 tool,
	      such  as	genrb(1),  then	 icu-config will also include the full
	      path to that tool.

       --ldflags
	      Print any flags which should be passed to the linker. These  may
	      include  -L  for	library search paths, and -l for including ICU
	      libraries. By default, this option will attempt to link  in  the
	      "common"	(libicuuc)  and "i18n" (libicui18n) libraries, as well
	      as the data library. If additional libraries are	required,  any
	      of the following two flags may be added in conjunction with this
	      one, for example "--ldflags --ldflags-icuio" if  the  icuio  li‐
	      brary  is	 required  in  addition to the standard ICU libraries.
	      Equivalent to the $(LDFLAGS) Makefile variable.

       --ldflags-layout
	      Prints the link option for the ICU layout library.

       --ldflags-icuio
	      Prints the link option to add the ICU I/O package

       --ldflags-libsonly
	      Similar to --ldflags but only includes the -l options.

       --ldflags-searchpath
	      Similar to --ldflags but only includes the -L  search  path  op‐
	      tions.

       --ldflags-system
	      Similar to --ldflags but only includes system libraries (such as
	      pthreads) --mandir Prints the location of the installed ICU  man
	      pages. Normally (man)

       --prefix
	      Prints the prefix (base directory) under which the installed ICU
	      resides.

       --prefix=prefix
	      Sets the ICU prefix to prefix for the remainder of this  command
	      line.  Does test whether the new prefix is valid.

       --sbindir
	      Prints the location of ICU system binaries, normally (sbin)

       --shared-datadir
	      Prints the location of ICU shared data, normally (share)

       --sysconfdir
	      Prints  the  location of ICU system configuration data, normally
	      (etc)

       --unicode-version
	      Prints the Version of the Unicode Standard which the current ICU
	      uses.

       --version
	      Prints the current version of ICU.

       --incfile
	      Prints  the  'Makefile.inc'  path,  suitable  for	 use with pkg‐
	      data(1)'s -O option.

AUTHORS
       Steven Loomis

VERSION
       77.1

COPYRIGHT
       Copyright (C) 2002-2004 IBM, Inc. and others.




ICU MANPAGE			  17 May 2004			 ICU-CONFIG(1)

GENBRK(1)			ICU 77.1 Manual			     GENBRK(1)



NAME
       genbrk  -  Compiles  ICU break iteration rules source files into binary
       data files

SYNOPSIS
       genbrk [ -h, -?, --help ] [ -V, --version ] [ -c, --copyright ]	[  -v,
       --verbose  ] [ -d, --destdir destination ] [ -i, --icudatadir directory
       ] -r, --rules rule-file -o, --out output-file

DESCRIPTION
       genbrk reads the break (boundary) rule source code from	rule-file  and
       creates	a  break  iteration data file. Normally this data file has the
       .brk extension.

       The details of the rule syntax can be found in ICU's User Guide.

OPTIONS
       -h, -?, --help
	      Print help about usage and exit.

       -V, --version
	      Print the version of genbrk and exit.

       -c, --copyright
	      Embeds the standard ICU copyright into the output-file.

       -v, --verbose
	      Display extra informative messages during execution.

       -d, --destdir destination
	      Set the destination directory of the output-file to destination.

       -i, --icudatadir directory
	      Look for any necessary ICU data files in directory.   For	 exam‐
	      ple,  the file pnames.icu must be located when ICU's data is not
	      built as a shared library.  The default ICU  data	 directory  is
	      specified by the environment variable ICU_DATA.  Most configura‐
	      tions of ICU do not require this argument.

       -r, --rules rule-file
	      The source file to read.

       -o, --out output-file
	      The output data file to write.

CAVEATS
       When the rule-file contains a byte order mark (BOM) at the beginning of
       the  file, which is the Unicode character U+FEFF, then the rule-file is
       interpreted as Unicode. Without the BOM, the file is interpreted in the
       current	operating  system default codepage.  In order to eliminate any
       ambiguity of the encoding for how the rule-file was written, it is rec‐
       ommended that you write this file in UTF-8 with the BOM.

ENVIRONMENT
       ICU_DATA	 Specifies  the	 directory  containing	ICU  data. Defaults to
		 /usr/share/icu/77.1/.	Some tools in ICU depend on the	 pres‐
		 ence of the trailing slash. It is thus important to make sure
		 that it is present if ICU_DATA is set.

AUTHORS
       George Rhoten
       Andy Heninger

VERSION
       1.0

COPYRIGHT
       Copyright (C) 2005 International Business Machines Corporation and oth‐
       ers

SEE ALSO
       http://www.icu-project.org/userguide/boundaryAnalysis.html




ICU MANPAGE			2 December 2005			     GENBRK(1)