This website does readability filtering of other pages. All styles, scripts, forms and ads are stripped. If you want your website excluded or have other feedback, use this form.

Man page of mkbedic

Content-type: text/html

mkbedic

Section: User Commands (1)
Index Return to Main Contents Install NVidia Drivers Ubuntu
 

NAME

mkbedic - Create a dictionary file for bedic dictionary readers from a simplified dictionary format file  

SYNOPSIS

mkbedic [--no-header] [--header-file <file>] [--id <id_field>] [--verbose] [--help] <infile> <outfile>

 

DESCRIPTION

mkbedic sorts, generates index and adds missing header properties to bedic dictionary file. Unlike xerox command, mkbedic expects <infile> to be a dictionary file in a simplified bedic format (see the next section). <outfile> is a resulting dictionary in full zbedic format (readable by zbedic). See bedic-format.txt for more information on the format of bedic dictionaries. If <file> (--header-file option) or <outfile> argument is a dash '-', the data is read or written to the Standard Input or Output.

 

SIMPLIFIED BEDIC FORMAT

Simplified bedic format has been introduced to overcome two shortcomings of the original full bedic format: to get rid of binary characters (such as 0 bytes), which are difficult to generate in scripts, and to make editing dictionaries in a text editor as easy as possible. The drawback of the new format is that the dictionaries in the simplified bedic format are not readable by the bedic library or any bedic dictionary reader, and must be first processed with mkbedic command.

The following is an example dictionary in the simplified bedic format:

nid=Example dictionary

Keyword 1
{s}{ss}This is a description of the {hw/},
which can span several lines{/ss}{s}

Keyword 2
{s}{ss}A single keyword can contain multiple
senses and subsenses{/ss}
{ss}This is the second subsense of the first sense{/ss}{/s}
{s}{ss}And this is the second sense{/ss}{/s}

The first part of the file is a header with multiple properties followed by an empty line. Then follow dictionary entries, each separated by a single empty line. Each entry can span several lines, but the first line is always a keyword. Format of entries (meanings of keywords) is the same as in the case of the full bedic format (see bedic-format.txt for the full description).  

OPTIONS

--header-file <file>, -h <file>

bedic header with the properties can be stored in a separate file, which can be specified with this option. If <infile> already contains some properties, they will be overwriten (if names match) with those in the <file>.

--no-header, -n

Specify this option if the <infile> does not contain a header (starts with dictionary entries).

--id <id_field>, -i <id_field>

id property in the header will be set to the argument of this option. This option overwrites both properties from the <infile> and the <file> specified with --header-file option.

 

WARNING AND ERROR MESSAGES

Duplicate entry

mkbedic will print out the entries that are not discernable using current character precedence settings and therefore they are not accessible by bedic (bedic requires that all key-words are unique). Do not use search-ignore-chars and set the proper char-precedence property to avoid duplicate entries.

Maximum dictionary length exceeded

Currectly bedic can handle dictionaries up to about 2,147,483,647 bytes.

 

BUGS

mkbedic may not handle very large files, since it uses libc IO functions.

--generate-char-precedence option is not supported. Run xerox on the <outfile> to find to generate a char precedence line.  

AUTHOR

Rafal Mantiuk <[email protected]>  

SEE ALSO

xerox(1)


 

Index

NAME
SYNOPSIS
DESCRIPTION
SIMPLIFIED BEDIC FORMAT
OPTIONS
WARNING AND ERROR MESSAGES
BUGS
AUTHOR
SEE ALSO

This document was created by man2html, using the manual pages.
Time: 08:47:35 GMT, June 27, 2005