m17n-db bug fix and enhancement update

Updated m17n-db packages that fix several bugs and add an enhancement are
now available.

The m17n-db packages contain multilingualization (m17n) datafiles for
m17n-lib, which describe input maps, encoding maps, and OpenType font data
for many languages.

These updated packages fix the followings bugs:

* the ta-typewriter.mim table in the Tamil (ta_IN) ta-typewriter keymap
incorrectly mapped ("n" ""), resulting in no output when pressing the
"n" key. The correct mapping, ("n" "ே"), is included in these updated
packages.

* during the transliteration of foreign words into Kannada (kn_IN), if
there were any consonants after a halant, and if there were any consonants
before the halant, without any spaces, both consonants merged to create a
composed character. In these updated packages, keymapping for the
ZeroWidthNonJoiner (ZWNJ) character has been added to the kn_IN keymaps,
which resolves this issue.

* in previous m17n-db packages, pressing the "a" key when using the Slovak
language resulted in three "t" characters being printed. In these updated
packages, the correct "a" to "a" key mapping is included.

* in previous m17n-db packages, there were no keymaps for number pad keys.
For example, using an Indic language resulted in the number pad keys
producing en_US characters. In these updated packages, the number pad keys
produce output in the correct language.

* in previous m17n-db packages, there were no key summaries for the kn-*
keymaps. Selecting a kn-* keymap in Smart Common Input Method (SCIM)
resulted in no key summary being displayed.

* the te_IN inscript keymap did not contain a key stroke for the
ZeroWidthNonJoiner (ZWNJ) character.

* the te-inscript.mim table did not contain a mapping for the 0c03
(ః) character.

These updated packages also add the following enhancement:

* additional key mappings for the Tamil (ta_IN) language.

Users of m17n-db are advised to upgrade to these updated packages, which
resolve these issues and add this enhancement.

Before applying this update, make sure that all previously-released
errata relevant to your system have been applied.

This update is available via Red Hat Network. Details on how to use
the Red Hat Network to apply this update are available at
http://kbase.redhat.com/faq/FAQ_58_10188