openKylin libtext-unidecode-perl package

libtext-unidecode-perl 1.30-ok1 source package in openKylin

Changelog

libtext-unidecode-perl (1.30-ok1) yangtze; urgency=medium

  * Build for openkylin.

 -- sufang <email address hidden>  Wed, 24 Aug 2022 16:22:02 +0800

Upload details

Uploaded by:
sufang
Sponsored by:
Cibot
Uploaded to:
Yangtze V1.0
Original maintainer:
Openkylin Developers
Architectures:
all
Section:
perl
Urgency:
Medium Urgency

Publishing See full publishing history

Series Pocket Published Component Section

Downloads

File Size SHA-256 Checksum
libtext-unidecode-perl_1.30.orig.tar.gz 128.8 KiB 39ff4a8379c493f5fa296cf3af38c0a93a85b1cac1626a70a85a9f8376cb5a78
libtext-unidecode-perl_1.30-ok1.debian.tar.xz 2.5 KiB 1f70853e963d73a8c044667a550835efa144cd4b4595a0b0ba20646e58208f3a
libtext-unidecode-perl_1.30-ok1.dsc 1.9 KiB 7ce4aee9f6d33d99db56f807e48b8a6b5e7c6356bc95ded869e5911724cb1c73

View changes file

Binary packages built by this source

libtext-unidecode-perl: US-ASCII transliterations of Unicode text

 It often happens that you have non-Roman text data in Unicode, but you can't
 display it -- usually because you're trying to show it to a user via an
 application that doesn't support Unicode, or because the fonts you need
 aren't accessible. You could represent the Unicode characters as "???????" or
 "\15BA\15A0\1610...", but that's nearly useless to the user who actually
 wants to read what the text says.
 .
 What Text::Unidecode provides is a function, unidecode(...) that takes
 Unicode data and tries to represent it in US-ASCII characters (i.e., the
 universally displayable characters between 0x00 and 0x7F). The representation
 is almost always an attempt at transliteration -- i.e., conveying, in Roman
 letters, the pronunciation expressed by the text in some other writing
 system.