Ports Search

This package contains the data files for the m17n library. m17n-lib currently supports input of more than 60 languages with more than 150 language specific input methods. m17n-db now incorporates a set of user-contributed input methods, formerly known as m17n-contrib. The package also provides the tbl2mim.awk script for conversion of keyboard files used by table based IMEngines of SCIM/IBus into m17n-lib's .mim format. The documentation is available through devel/m17n-docs.

This package contains the documentation files for the m17n library.

The m17n library provides following facilities to handle multilingual text. * M-text: A data structure for a multilingual text. It is basically a string but with attributes called text property, and is designed to substitute for the C string. It is the most important object of the m17n library. * Functions for creating and processing M-texts. * Functions for converting M-texts from/to strings encoded in various existing formats. * A huge character space, which contains all the Unicode characters and more non-Unicode characters. * Chartable: A data structure that contains per-character information efficiently. * Functions for inputting and displaying M-text on a window system. The documentation is available through devel/m17n-docs.

The program mph tries to generate an order preserving minimal perfect hashing (MPH) function for the set of keys, one per line, on stdin. Each key can be at most 4095 characters long (see keys.h to increase this limit), and the keys must be unique. If mph terminates, it emits a language independent binary or text representation of the MPH function on stdout. To generate a usable hash function, this output should be fed to a language dependent filter, like emitc.

Perl algorithm to iterate through subsets of a list. "Subsets" in this context refers to lists with elements taken from the original list, and in the same order as the elements in the original list. After creating the object, subsequent calls to next() will return the next such list in lexicographic order (where the alphabet is the original list).

A system for choosing a value for something. Takes a string composed of various tests, arguements, and etc and returns a value based on it.

This module is designed to provide an extremely lightweight way to parse moderately complex configuration files. As such, it exports a single function - fastconfig() - and does not provide any OO access methods. Still, it is fairly full-featured. Here's how it works: %cf = fastconfig($file, $delim); Basically, the fastconfig() function returns a hash of keys and values based on the directives in your configuration file. By default, directives and values are separated by whitespace in the config file, but this can be easily changed with the delimiter argument (see below). When the configuration file is read, its modification time is first checked and the results cached. On each call to fastconfig(), if the config file has been changed, then the file is reread. Otherwise, the cached results are returned automatically. This makes this module great for mod_perl modules and scripts, one of the primary reasons I wrote it. Simply include this at the top of your script or inside of your constructor function: my %cf = fastconfig('/path/to/config/file.conf'); If the file argument is omitted, then fastconfig() looks for a file named $0.conf in the ../etc directory relative to the executable. For example, if you ran: /usr/local/bin/myapp Then fastconfig() will automatically look for: /usr/local/etc/myapp.conf This is great if you're really lazy and always in a hurry, like I am. If this doesn't work for you, simply supply a filename manually. Note that filename generation does not work in mod_perl, so you'll need to supply a filename manually.

Checks for dir/file addition/removals in the current directory.

Devel::TraceUse - Show the modules your program loads, recursively. An apparently simple program may load a lot of modules. That's useful, but sometimes you may wonder exactly which part of your program loads which module. Devel::TraceUse can analyze a program to see which part used which module.

File::DirSync will make two directories exactly the same. The goal is to perform this synchronization process as quickly as possible with as few stats and reads and writes as possible. It usually can perform the synchronization process within a few milliseconds - even for gigabytes or more of information.