o à›h:ã@sjdZddlZddlmZddlmZe d¡Ze d¡Zde de fd d „Z e d ¡Z de de fd d „Z dS)zBPython implementation of ASCII85/ASCIIHex decoder (Adobe version).éN)Ú a85decode)Ú unhexlifys ^\s*?\s*$ÚdataÚreturncCs t d|¡}t d|¡}t|ƒS)aÚIn ASCII85 encoding, every four bytes are encoded with five ASCII letters, using 85 different types of characters (as 256**4 < 85**5). When the length of the original bytes is not a multiple of 4, a special rule is used for round up. Adobe's ASCII85 implementation expects the input to be terminated by `b"~>"`, and (though this is absent from the PDF spec) it can also begin with `b"<~"`. We can't reliably expect this to be the case, and there can be off-by-one errors in stream lengths which mean we only see `~` at the end. Worse yet, `<` and `>` are ASCII85 digits, so we can't strip them. We settle on a compromise where we strip leading `<~` or `~` and trailing `~` or `~>`. ó)Ústart_reÚsubÚend_rer)r©r úI/var/www/html/govbot/env/lib/python3.10/site-packages/pdfminer/ascii85.pyÚ ascii85decode s  r s\scCsFt d|¡}| d¡}|dkr|d|…}|ddkr|d7}t|ƒS)aáASCIIHexDecode filter: PDFReference v1.4 section 3.3.1 For each pair of ASCII hexadecimal digits (0-9 and A-F or a-f), the ASCIIHexDecode filter produces one byte of binary data. All white-space characters are ignored. A right angle bracket character (>) indicates EOD. Any other characters will cause an error. If the filter encounters the EOD marker after reading an odd number of hexadecimal digits, it will behave as if a 0 followed the last digit. ró>éÿÿÿÿNééó0)Úbws_rerÚfindr)rÚidxr r r Úasciihexdecode!s   r) Ú__doc__ÚreÚbase64rÚbinasciirÚcompilerr Úbytesr rrr r r r Ús