Result for 009A3C35615DC38F6EF9B2C3CD5FD35C14CEC3E4

Query result

Key Value
FileName./usr/lib/python3.6/site-packages/unidecode/__pycache__/x0b5.cpython-36.pyc
FileSize3778
MD50E333936CBC9615207680F4C0BDF8D46
SHA-1009A3C35615DC38F6EF9B2C3CD5FD35C14CEC3E4
SHA-256A7024DDB3103E8CE550B6731F47F901EBDE88A11FAA00B30549B3E09D8A2CF6A
SSDEEP96:EMBHEqBwc2DwdX9SbahHRScu0SsR9vd9KaHv6HKfv:1BEc2DwdX9/hfuiR9VdHS6v
TLSHT1EB7166FF7305118AF110F869C5C937C272DFA8A9E06A1B40A0726793AEC52D53D382E7
hashlookup:parent-total1
hashlookup:trust55

Network graph view

Parents (Total: 1)

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

Key Value
MD5B4FD6903982FF3F3473A12ABC79CA37A
PackageArchnoarch
PackageDescriptionIt 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>.
PackageMaintainerhttps://bugs.opensuse.org
PackageNamepython3-Unidecode
PackageReleaselp150.1.3
PackageVersion1.0.22
SHA-1014FE1F89DB9F0F3E4EF847223A59921E418029C
SHA-256E27E196B1F5D1ABF9D7431AED34F0F2617F1A5629458409CD17AB43848FF2BE0