libencode-locale-perl 1.05-ok1 source package in openKylin

Changelog

libencode-locale-perl (1.05-ok1) yangtze; urgency=low

  * Build for openKylin.

 -- openKylinBot <email address hidden>  Mon, 25 Apr 2022 22:03:04 +0800

Upload details

Uploaded by:
openKylinBot
Sponsored by:
luzp
Uploaded to:
Yangtze V1.0
Original maintainer:
Openkylin Developers
Architectures:
all
Section:
perl
Urgency:
Low Urgency

Publishing See full publishing history

Series Pocket Published Component Section

Downloads

File Size SHA-256 Checksum
libencode-locale-perl_1.05.orig.tar.gz 8.2 KiB 176fa02771f542a4efb1dbc2a4c928e8f4391bf4078473bd6040d8f11adb0ec1
libencode-locale-perl_1.05-ok1.debian.tar.xz 1.8 KiB 9daad6fe0b0b9b4428a0def6199185eacd5180195aea8369ed38451bb13e3c59
libencode-locale-perl_1.05-ok1.dsc 1.9 KiB 11b80399f55626aac449c3a91e872a42dca6e58dbdd53ccf8b81f50461d9347a

View changes file

Binary packages built by this source

libencode-locale-perl: utility to determine the locale encoding

 In many applications it's wise to let Perl use Unicode for the strings it
 processes. Most of the interfaces Perl has to the outside world are still byte
 based. Programs therefore need to decode byte strings that enter the program
 from the outside and encode them again on the way out.
 .
 The POSIX locale system is used to specify both the language conventions
 requested by the user and the preferred character set to consume and output.
 The Encode::Locale module looks up the charset and encoding (called a CODESET
 in the locale jargon) and arranges for the Encode module to know this encoding
 under the name "locale". It means bytes obtained from the environment can be
 converted to Unicode strings by calling Encode::encode(locale => $bytes) and
 converted back again with Encode::decode(locale => $string).