Lingua::Translit can be used to convert text from one writing system to
another, based on national or international transliteration tables. Where
possible a reverse transliteration is supported.
Are you sick of trying to remember whether a particular helper is defined in
List::Util or List::MoreUtils? I sure am. Now you don't have to remember. This
module will export all of the functions that either of those two modules
defines.
The List::PowerSet module is simple module that currently allows you to
generate the power set of a list
Log::Dump is a simple logger mix-in mainly for debugging. This
installs six methods into a caller (the class that used Log::Dump) via
Sub::Install. The point is you don't need to load extra dumper modules
or you don't need to concatenate messages. Just log things and they
will be dumped (and concatenated if necessary) to stderr, and to a
file if you prefer. Also, you can use these logging methods as class
methods or object methods (though usually you don't want to mix them,
especially when you're doing something special).
List::SomeUtils provides some trivial but commonly needed functionality on lists
which is not going to go into List::Util.
All of the below functions are implementable in only a couple of lines of Perl
code. Using the functions from this module however should give slightly better
performance as everything is implemented in C. The pure-Perl implementation of
these functions only serves as a fallback in case the C portions of this module
couldn't be compiled on this machine.
pure perl implementation of GNU gettext
This module provides methods for manipulating objects that represent
entries in a gettext po-file (untranslated and translated strings, with
associated comments). It can load and save complete po-files.
This module permits from perl to the gettext() family of functions
for retrieving message strings from databases constructed to
internationalize software.
The package libintl-perl is an internationalization library for Perl
that aims to be compatible with the Uniforum message translations
system as implemented for example in GNU gettext.
The Log::Agent module provides an abstract layer for logging and tracing, which
is independent from the actual method used to physically perform those
activities. It acts as an agent (hence the name) that collects the requests and
delegates processing to a sublayer: the logging driver.
The Log::Agent module is meant to be used in all reusable components, since
they cannot know in advance how the application which ends up using them will
perform its logging activities: either by emitting messages on stdout and
errors on stderr, or by directing messages to log files, or by using syslog(3).
The logging interface is common for all the logging drivers, and is therefore
the result of a compromise between many logging schemes: any information given
at this level must be either handled by all drivers, or may be ignored
depending on the application's final choice.
WARNING: THIS INTERFACE IS STILL SOMEWHAT ALPHA AND COULD STILL CHANGE
DEPENDING ON THE FEEDBACK THE AUTHOR RECEIVES, WITHOUT ANY BACKWARD
COMPATIBILITY ASSURANCE.