Go to main content

マニュアルページ セクション 1: ユーザーコマンド

印刷ビューの終了

更新: 2018年8月8日
 
 

genbrk (1)

名前

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

形式

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

説明

GENBRK(1)                       ICU 59.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
                 ${prefix}/share/icu/59.1/.  Some tools in ICU depend  on  the
                 presence  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


ATTRIBUTES
       See attributes(7) for descriptions of the following attributes:


       +---------------+-----------------------+
       |ATTRIBUTE TYPE |   ATTRIBUTE VALUE     |
       +---------------+-----------------------+
       |Availability   | developer/icu         |
       +---------------+-----------------------+
       |Stability      | Pass-through volatile |
       +---------------+-----------------------+
SEE ALSO
       http://www.icu-project.org/userguide/boundaryAnalysis.html




NOTES
       This     software     was    built    from    source    available    at
       https://github.com/oracle/solaris-userland.   The  original   community
       source       was       downloaded       from       http://download.icu-
       project.org/files/icu4c/59.1/icu4c-59_1-src.tgz

       Further information about this software can be found on the open source
       community website at http://site.icu-project.org/.



ICU MANPAGE                     2 December 2005                      GENBRK(1)