Free unicode data browser 1.5 software for linux

The KDE CIM Browser is a KDE based frontend to management brokers using the CIM-XML protocol.
The tool will be useful to view and modify CIM class hierarchies as well as instance and association structures.
Enhancements:
- The latest release of kim-browser is mainly a maintenance release.
- One new feature is namespace browsing, which allows you to pick the namespace to navigate in once connected to a CIMOM.
- In addition to this, some bugfixes have been incorporated and the visual appearance has been improved a bit.

The Modular Manual Browser is a set scripts designed as a man/apropos work-alike. It indexes manual pages across different operating systems and displays them in a searchable database in a Web browser.
It is easy to set up and includes highlighting, linking support in man pages, browsing and searching of pages, categories, and manuals.
It can also optionally set up a database containing descriptions of pages from the page titles.
Enhancements:
- BUGS, COPYING, INSTALL, INSTALL.roff, Makefile, README, README.roff, TODO.sh, config.php, index.php, mandb.php, modfunc.php, modman.php, api/files.php, api/modfunc.php, api/pages.php, api/whatis.php, install/BUGS, install/COPYING, install/INSTALL, install/INSTALL.roff, install/Makefile, install/README, install/README.roff, install/TODO.sh, tmp/.local: api split up, install data moved, so that modman may be dropped directly into webspace. mandb.php can pick up multi-line descriptions now.
Apropos results can be filtered by Section or Manual, but not Page (obviously).
whatis pseudo-database implemented, enabled by default in config.
Sections include Subsections (3->3ucb, 3ucb->3ucblib). Local Apropos and description support added via apropos/whatis programs.
- Release 1.2 -- The Small-Box/WhatIS Release.

TV-Browser is a TV guide that is easily extensible using plugins. TVBrowser is designed to look like a paper based TV guide. Included are over 80 German language channels.
At the moment, it only loads data in its own binary format, but its possible to write a plugin that loads XMLTV data.
The tv data are retrieved from multiple sources and can be downloaded from our servers after having been automatically processed.
The whole project - both the client and the server part - is distributed under the GNU GPL.
Currently, we offer only channels in german language but we are highly motivated to extend TV-Browser for other countries.
Enhancements:
- Minor bugfixes.

Yukatan data model project is the schema definition of the Yukatan webmail database.
The PostgreSQL database structures defined in this file can be used as a backend store of an email message handling application. The database should be created with the "UNICODE" encoding to properly support messages in different languages.
New data types
The special data types commonly used in the Yukatan data model have been made explicit by the introduction of seven new domains. The domains and the related COMMENT statements make field semantics more clear than before.
See the SQL schema file for more detailed documentation on these domains.
Explicitly named constraints
All the table constraints in the database are now explicitly named and documented. This change makes the database implementation more orthogonal and cleans up the documentation.
Renamed fields and tables
All the *address field names have been truncated to *addr, to make it visually clearer that they are always paired with the corresponding *name fields. The change also makes parts of the documentation less repetitive.
The referencesfield table has been renamed to referencefield to avoid the plural form in the table name. Also all the contained references* field names have been renamed to reference*.
Semantic changes
Quite a few changes have been made to the semantics of various fields. The unnecessarily tight constraints on sequence numbers have been replaced with clearer documentation, the format and encoding of most fields has been explicitly documented, and the previously allowed dual use of the enttext and enddata fields has been prohibited.
Dropped envelope data
The envelope data added in version 0.5 of the data model has for now been removed. The reason for the removal is that the envelope data is not an integral part of an email message, and I wanted to make the version 1.0 as clear as possible. The database now stores "email messages" - nothing less, nothing more. Envelope data can and probably will be reintroduced in an incremental version 1.x along with other extensions.
Enhancements:
- cleans up and documents the data model that has developed since version 0.1
- removal of the envelope data added in version 0.5
- enaming and redefinition of some of the fields and tables
- database structure has also been extensively documented

Hermes JMS Browser is a console that helps you interact with JMS providers making it easy to browse or search queues and topics, copy messages around and delete them. The project fully integrates with JNDI letting you discover administered objects stored, create JMS sessions from the connection factories and use any destinations found.

Many providers include a plugin that uses the native API to do non-JMS things like getting queue depths (and other statistics) or finding queue and topic names.

Unicode::MapUTF8 is a Perl module with conversions to and from arbitrary character sets and UTF8.

SYNOPSIS

use Unicode::MapUTF8 qw(to_utf8 from_utf8 utf8_supported_charset);

# Convert a string in ISO-8859-1 to UTF8
my $output = to_utf8({ -string => An example, -charset => ISO-8859-1 });

# Convert a string in UTF8 encoding to encoding ISO-8859-1
my $other = from_utf8({ -string => Other text, -charset => ISO-8859-1 });

# List available character set encodings
my @character_sets = utf8_supported_charset;

# Add a character set alias
utf8_charset_alias({ ms-japanese => sjis });

# Convert between two arbitrary (but largely compatible) charset encodings
# (SJIS to EUC-JP)
my $utf8_string = to_utf8({ -string =>$sjis_string, -charset => sjis});
my $euc_jp_string = from_utf8({ -string => $utf8_string, -charset => euc-jp })

# Verify that a specific character set is supported
if (utf8_supported_charset(ISO-8859-1) {
# Yes
}

Provides an adapter layer between core routines for converting to and from UTF8 and other encodings. In essence, a way to give multiple existing Unicode modules a single common interface so you dont have to know the underlaying implementations to do simple UTF8 to-from other character set encoding conversions. As such, it wraps the Unicode::String, Unicode::Map8, Unicode::Map and Jcode modules in a standardized and simple API.

This also provides general character set conversion operation based on UTF8 - it is possible to convert between any two compatible and supported character sets via a simple two step chaining of conversions.

As with most things Perlish - if you give it a few big chunks of text to chew on instead of lots of small ones it will handle many more characters per second.

By design, it can be easily extended to encompass any new charset encoding conversion modules that arrive on the scene.
This module is intended to provide good Unicode support to versions of Perl prior to 5.8. If you are using Perl 5.8.0 or later, you probably want to be using the Encode module instead. This module does work with Perl 5.8, but Encode is the preferred method in that environment.

ustring is a C++ library to implement the complete Unicode 3.0 standard. It gives an easy access to the properties of each of the 10600 characters defined by the Unicode 3.0 standard, including the uppercase and lowercase mapping, category and subcategory, character name, and bidirectional category.

ustring C++ Unicode library provides a wide string class which fits with STL, implementing a full Unicode normalizer, uppercase and lowercase transformation, and diacritical mark removal. A Unicode level-1 regular expression class is also provided.