converts the ICU converter table
into a binary file. The binary file has the same base name as
but has a
extension (instead of the typical
extension of the
This binary file can then be read directly by ICU, or used by
for incorporation into a larger archive or library.
must be in the ICU ucm (Unicode Codepage Mapping) format in order to
be understood by
The ICU ucm format is similar to the IBM NLTC upmap/tpmap/rpmap files.
Comments in the
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,
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 accomodate 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
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
-h, -?, --help
Print help about usage and exit.
Include a copyright notice in the binary data.
Display extra informative messages during execution.
-d, --destdir destination
Set the destination directory to
The default destination directory is specified by the environment variable
If an existing converter table is changed and recompiled using
the resulting binary file must be packaged in the same way that it was
packaged initially. For example, if converters were grouped together in
an archive or a library with
then the archive or library must be rebuilt with the new binary file.
A standalone binary converter file will not take precedence over a
Specifies the directory containing ICU data. Defaults to
Some tools in ICU depend on the presence of the trailing slash. It is thus
important to make sure that it is present if