Man page or keyword search:   man All Sections 1 - General Commands 2 - System Calls 3 - Subroutines, Functions 4 - Special Files 5 - File Formats 6 - Games and Screensavers 7 - Macros and Conventions 8 - Maintenence Commands 9 - Kernel Interface New Commands Server 4.4BSD AIX Alpinelinux Archlinux Aros BSDOS BSDi Bifrost CentOS Cygwin Darwin Debian DigitalUNIX DragonFly ElementaryOS Fedora FreeBSD Gentoo GhostBSD HP-UX Haiku Hurd IRIX Inferno JazzOS Kali Knoppix LinuxMint MacOSX Mageia Mandriva Manjaro Minix MirBSD NeXTSTEP NetBSD OPENSTEP OSF1 OpenBSD OpenDarwin OpenIndiana OpenMandriva OpenServer OpenSuSE OpenVMS Oracle PC-BSD Peanut Pidora Plan9 QNX Raspbian RedHat Scientific Slackware SmartOS Solaris SuSE SunOS Syllable Tru64 UNIXv7 Ubuntu Ultrix UnixWare Xenix YellowDog aLinux   18016 pages apropos Keyword Search (all sections) Output format html ascii pdf view pdf save postscript

GENBRK(1)			ICU 53.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/53.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

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

ICU MANPAGE			2 December 2005			     GENBRK(1)

Vote for polarhome