Parents (Total: 179)

The searched file hash is included in 179 parent files which include package known and seen by metalookup. A sample is included below:

Key	Value
MD5	B4FD6903982FF3F3473A12ABC79CA37A
PackageArch	noarch
PackageDescription	It often happens that you have text data in Unicode, but you need to represent it in ASCII. For example when integrating with legacy code that doesn't support Unicode, or for ease of entry of non-Roman names on a US keyboard, or when constructing ASCII machine identifiers from human-readable Unicode strings that should still be somewhat intelligible (a popular example of this is when making an URL slug from an article title). In most of these examples you could represent Unicode characters as "???" or "\\15BA\\15A0\\1610", to mention two extreme cases. But that's nearly useless to someone who actually wants to read what the text says. What Unidecode provides is a middle road: function unidecode() takes Unicode data and tries to represent it in ASCII characters (i.e., the universally displayable characters between 0x00 and 0x7F), where the compromises taken when mapping between two character sets are chosen to be near what a human with a US keyboard would choose. The quality of resulting ASCII representation varies. For languages of western origin it should be between perfect and good. On the other hand transliteration (i.e., conveying, in Roman letters, the pronunciation expressed by the text in some other writing system) of languages like Chinese, Japanese or Korean is a very complex issue and this library does not even attempt to address it. It draws the line at context-free character-by-character mapping. So a good rule of thumb is that the further the script you are transliterating is from Latin alphabet, the worse the transliteration will be. Note that this module generally produces better results than simply stripping accents from characters (which can be done in Python with built-in functions). It is based on hand-tuned character mappings that for example also contain ASCII approximations for symbols and non-Latin alphabets. This is a Python port of Text::Unidecode Perl module by Sean M. Burke <sburke@cpan.org>.
PackageMaintainer	https://bugs.opensuse.org
PackageName	python3-Unidecode
PackageRelease	lp150.1.3
PackageVersion	1.0.22
SHA-1	014FE1F89DB9F0F3E4EF847223A59921E418029C
SHA-256	E27E196B1F5D1ABF9D7431AED34F0F2617F1A5629458409CD17AB43848FF2BE0

Key	Value
FileName	https://ftp.lysator.liu.se/pub/OpenBSD/6.8/packages//amd64//py-unidecode-1.1.1p0.tgz
MD5	163983A760643F5E35ED1E4949919DB4
SHA-1	055C21EF564092C19F12D1EDAA9150883B94B4A8
SHA-256	CA42D3890AF5CDABD38E71F80547AEFEFE063E50BF6B5749DAAE64218A416606
SSDEEP	6144:8mngD6v2mKJxSi2Cg8C1djcTYTs4I6fOiEIORal0AlEHEzVfCnz9eQazQQS7oM6:LBv21xjCzxcTLsOiEbRapEEsnzANSkF
TLSH	T186642205DC16E7FD926138734A9EAD339935CA3C63331E5E3A0D30F496E988376A6D06

Key	Value
MD5	66107BFD0ADD2BFBB1D5BC89142B1219
PackageArch	noarch
PackageDescription	It often happens that you have text data in Unicode, but you need to represent it in ASCII. For example when integrating with legacy code that doesn't support Unicode, or for ease of entry of non-Roman names on a US keyboard, or when constructing ASCII machine identifiers from human-readable Unicode strings that should still be somewhat intelligible (a popular example of this is when making an URL slug from an article title). In most of these examples you could represent Unicode characters as "???" or "\\15BA\\15A0\\1610", to mention two extreme cases. But that's nearly useless to someone who actually wants to read what the text says. What Unidecode provides is a middle road: function unidecode() takes Unicode data and tries to represent it in ASCII characters (i.e., the universally displayable characters between 0x00 and 0x7F), where the compromises taken when mapping between two character sets are chosen to be near what a human with a US keyboard would choose. The quality of resulting ASCII representation varies. For languages of western origin it should be between perfect and good. On the other hand transliteration (i.e., conveying, in Roman letters, the pronunciation expressed by the text in some other writing system) of languages like Chinese, Japanese or Korean is a very complex issue and this library does not even attempt to address it. It draws the line at context-free character-by-character mapping. So a good rule of thumb is that the further the script you are transliterating is from Latin alphabet, the worse the transliteration will be. Note that this module generally produces better results than simply stripping accents from characters (which can be done in Python with built-in functions). It is based on hand-tuned character mappings that for example also contain ASCII approximations for symbols and non-Latin alphabets. This is a Python port of Text::Unidecode Perl module by Sean M. Burke <sburke@cpan.org>.
PackageMaintainer	https://bugs.opensuse.org
PackageName	python3-Unidecode
PackageRelease	bp154.1.68
PackageVersion	1.1.1
SHA-1	060FC5EB5F092C399740382F2358B1955DF7241D
SHA-256	4F816BB93C7CA3B95D760DD8435A8E21351F44FFD1454BF6B96163D4737614AB

Key	Value
FileName	https://ftp.lysator.liu.se/pub/OpenBSD/6.7/packages//sparc64//py3-unidecode-1.1.1.tgz
MD5	C3009A382C0CFD92E4573816C72D011D
SHA-1	0920D8F87C99CE80E5D83059E8A83629A18BCB95
SHA-256	2DEFAA95BADAF43D9920D3F16BC563E5A8E4884F0B3F1D44053926FF2EDFD14C
SSDEEP	6144:2KeJSti0BzCZl3GdYIVyXAVj3HYsk5TlxtkBGGTswFI:2zJC9BeZl2dYIEX83413t/yI
TLSH	T19A54224EF7E366A5568B613F1F85528E868532788450B1AE8CC37C5B82215F3C9F8E1F

Key	Value
FileName	https://ftp.lysator.liu.se/pub/OpenBSD/6.5/packages//mips64el//py3-unidecode-1.0.23.tgz
MD5	07CD7238981BA3C4CA9EA7FF8E9BE86B
SHA-1	09418E9C758E702C19F07B3F0DBB50F1C012DBFC
SHA-256	8DC5E4F4D1BBC3FCC7ECE5D8E553E358693FC3614B718BA6ED736C0E550950EF
SSDEEP	6144:EInoIhH7iq1BxArYixRy2G9fiM78uHCmn:EtIB7iuUl0fJIuHL
TLSH	T1E164239D2D33E5AC8149279E4FA60FF126CC52C950B56CE510E880E5A6BFF6F3A13361

Key	Value
FileName	https://ftp.lysator.liu.se/pub/OpenBSD/6.8/packages//arm//py3-unidecode-1.1.1p0.tgz
MD5	A9B1744357A47F5D97FCCCCBCE3B6A14
SHA-1	09CC2630BBE3BC2627799F9940ACD4533B4F8C9A
SHA-256	9015F0B6D8B06DD009581DEE7DB7101A1876C00EBCA9772BF8BF6A784A38C8FF
SSDEEP	6144:1xNn6fY5eUBPc5peBPLEpNOmdidOl+GyX2tQRfdqVzcUkiJD:17qY3BPc5ERLI8MidOLyX26IVzcU9
TLSH	T1B56423972EB09FDA77A158F6CBB375C4C7C30AF86A7A4941DA0C0D86A7A02D63341593

Key	Value
FileName	https://ftp.lysator.liu.se/pub/OpenBSD/6.7/packages//sparc64//py-unidecode-1.1.1.tgz
MD5	80977E1D79EDE95976589457F568AEA4
SHA-1	09CCA54A00317BAAB998F8895633EF16CC51A3B3
SHA-256	E3190B4C873194D855C806DD61CD951CB1CD70B310F6EA82277ECC4F0C1B89DD
SSDEEP	6144:Lqx/etE9mKJxSi2Cg8C1djcTYTSJtfu8BHig2RSje0u8ekcCJOb/:LDE91xjCzxcTtJtfustdje0u8ob
TLSH	T12A6423074C237BFC42B335B34A9C29E73E7D466DA06219FE0A2C66B94291CD71C92D67

Key	Value
FileName	https://ftp.lysator.liu.se/pub/OpenBSD/6.9/packages//arm//py-unidecode-1.1.1p1.tgz
MD5	A21C22416E264E2259793A6D36B108EF
SHA-1	09FBFD656749B0EA976E355B29A617460756F8AB
SHA-256	9B40728CB2025CDAE72D076B713A3AB96DB5B19657896BDF0B9DA8B264162503
SSDEEP	6144:lImimKJxSi2Cg8C1djcTYTSJtfu8BHig2RSje0u8ekcCJOb/:Fi1xjCzxcTtJtfustdje0u8ob
TLSH	T1A66423074C27B7BC92623573495D3AE73F7D11ACA0B21CEE0A2C69BB52D1C962C52C97

Key	Value
SHA-1	0E30486CA56E3C544B896C850BCA53905AFEA633
snap-authority	canonical
snap-filename	QntDb1wZjJJ5lizFjPIj3thQsvSpakI5_1253.snap
snap-id	QntDb1wZjJJ5lizFjPIj3thQsvSpakI5_1253
snap-name	sickgear
snap-publisher-id	TVuZoFqNQjS3wXXJygU544vtBswXL4G8
snap-signkey	BWDEoaqyr25nF5SNCvEv2v7QnM9QsfCc0PBMYD_i2NGSQ32EF2d4D0hqUel3m8ul
snap-timestamp	2018-10-23T20:02:32.692392Z
source-url	https://api.snapcraft.io/api/v1/snaps/download/QntDb1wZjJJ5lizFjPIj3thQsvSpakI5_1253.snap

Key	Value
MD5	8063F9D4F68A648D0E0E74333B0C9EAE
PackageArch	noarch
PackageDescription	It often happens that you have text data in Unicode, but you need to represent it in ASCII. For example when integrating with legacy code that doesn't support Unicode, or for ease of entry of non-Roman names on a US keyboard, or when constructing ASCII machine identifiers from human-readable Unicode strings that should still be somewhat intelligible (a popular example of this is when making an URL slug from an article title). In most of these examples you could represent Unicode characters as "???" or "\\15BA\\15A0\\1610", to mention two extreme cases. But that's nearly useless to someone who actually wants to read what the text says. What Unidecode provides is a middle road: function unidecode() takes Unicode data and tries to represent it in ASCII characters (i.e., the universally displayable characters between 0x00 and 0x7F), where the compromises taken when mapping between two character sets are chosen to be near what a human with a US keyboard would choose. The quality of resulting ASCII representation varies. For languages of western origin it should be between perfect and good. On the other hand transliteration (i.e., conveying, in Roman letters, the pronunciation expressed by the text in some other writing system) of languages like Chinese, Japanese or Korean is a very complex issue and this library does not even attempt to address it. It draws the line at context-free character-by-character mapping. So a good rule of thumb is that the further the script you are transliterating is from Latin alphabet, the worse the transliteration will be. Note that this module generally produces better results than simply stripping accents from characters (which can be done in Python with built-in functions). It is based on hand-tuned character mappings that for example also contain ASCII approximations for symbols and non-Latin alphabets. This is a Python port of Text::Unidecode Perl module by Sean M. Burke <sburke@cpan.org>.
PackageName	python3-Unidecode
PackageRelease	2.1
PackageVersion	1.3.2
SHA-1	110E9F2067C942D7B7EA0E9F292754B58C70B2A9
SHA-256	A3FF76DDB5AAB7D5F3B28679671BF58337598545C8BFA7EFE29E1850543B93ED