DFUI curses frontend. Allows a DFUI backend (such as a system
installer) to communicate with the user with an addressable text
screen-oriented ('curses') user interface.
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.
This module make use of Algorithm::Accounting and SVK to do
simple accounting of any SVK repository. The installed
svn-accounting.pl script demonstrate a simple use to this module,
you may try:
svk-accounting.pl //
This will display all the contributions of developers under
repository '//'. You may also specify depotpath like '//trunk/svk'.
This module make use of Algorithm::Accounting and SVN::Log to do
simple accounting of any subversion repository (not necessarily
local, as long as you can do "svn log" to). The installed
svn-accounting.pl script demonstrate a simple use to this module,
you may try:
svn-accounting.pl http://svn.collab.net/repos/svn/
The Log::Agent::Logger class defines a generic interface for application
logging. It must not be confused with the interface provided by
Log::Agent, which is meant to be used by re-usable modules that do not
wish to commit on a particular logging method, so that they remain true
building blocks.
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.
Adapter to use callbacks with Log::Any.