from small one page howto to huge articles all in one place
 

search text in:





Poll
Which filesystem do you use?






poll results

Last additions:
using iotop to find disk usage hogs

using iotop to find disk usage hogs

words:

887

views:

186360

userrating:

average rating: 1.7 (102 votes) (1=very good 6=terrible)


May 25th. 2007:
Words

486

Views

250360

why adblockers are bad


Workaround and fixes for the current Core Dump Handling vulnerability affected kernels

Workaround and fixes for the current Core Dump Handling vulnerability affected kernels

words:

161

views:

137537

userrating:

average rating: 1.4 (42 votes) (1=very good 6=terrible)


April, 26th. 2006:

Druckversion
You are here: manpages





GENBRK

Section: ICU 58.2 Manual (1)
Updated: 2 December 2005
Index Return to Main Contents
 

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 example, 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 configurations 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 recommended 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/58.2/. 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 others  

SEE ALSO

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


 

Index

NAME
SYNOPSIS
DESCRIPTION
OPTIONS
CAVEATS
ENVIRONMENT
AUTHORS
VERSION
COPYRIGHT
SEE ALSO





Support us on Content Nation
rdf newsfeed | rss newsfeed | Atom newsfeed
- Powered by LeopardCMS - Running on Gentoo -
Copyright 2004-2020 Sascha Nitsch Unternehmensberatung GmbH
Valid XHTML1.1 : Valid CSS : buttonmaker
- Level Triple-A Conformance to Web Content Accessibility Guidelines 1.0 -
- Copyright and legal notices -
Time to create this page: 18.1 ms