3ja*UdZddlmZmZdedefdZdZeed<e eZ e e ed<e eDcic]\}}|| c}}Z ee e fed <d edefd Zded e defd ZdedefdZdededzfdZycc}}w)aEarly detection of escape-sequence-based encodings (ISO-2022, HZ-GB-2312, UTF-7). These encodings use ESC (0x1B), tilde (~), or plus (+) sequences to switch character sets. They must be detected before binary detection (ESC is a control byte) and before ASCII detection (HZ-GB-2312 and UTF-7 use only printable ASCII bytes plus their respective shift markers). Note: ``from __future__ import annotations`` is intentionally omitted because this module is compiled with mypyc, which does not support PEP 563 string annotations. )DETERMINISTIC_CONFIDENCEDetectionResultdatareturncd} |jd|}|dk(ry|jd|dz}|dk(ry||dz|}t|dk\r$t|dzdk(rtd|Dry|dz}s) aCheck that at least one ~{...~} region contains valid GB2312 byte pairs. In HZ-GB-2312 GB mode, characters are encoded as pairs of bytes in the 0x21-0x7E range. We require at least one region with a non-empty, even- length run of such bytes. rT~{F~}c3<K|]}d|cxkxrdkncyw)!~N).0bs D/DATA/.local/lib/python3.12/site-packages/chardet/pipeline/escape.py z(_has_valid_hz_regions..$s6v!DA%%%vs)findlenall)rstartbeginendregions r_has_valid_hz_regionsrs E  %' B;iiuqy) "9eai#& K1 F a1$6v66a s@ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789+/ _B64_CHARS _UTF7_BASE64 _B64_DECODE b64_bytesct|}|dz}|dz}|dkDrt|d}d|zdz }||zry|dz}t|}d}d} d} |D]1} |dzt| z}| dz } | dk\s| dz} || z dz|| <| dz } 3d} td|dz d D]C} || dz|| dzz}d |cxkrd kr nn| ryd } )d |cxkrdkr nn| syd} >| ryd} E| S)uCheck if base64 bytes decode to valid UTF-16BE with correct padding. A valid UTF-7 shifted sequence must: 1. Contain at least 3 Base64 characters (18 bits, enough for one 16-bit UTF-16 code unit). 2. Have zero-valued trailing padding bits (the unused low bits of the last Base64 sextet after the last complete 16-bit code unit). 3. Decode to valid UTF-16BE — no lone surrogates. This rejects accidental ``+-`` patterns found in URLs, MIME boundaries, hex-encoded hashes (e.g. SHA-1 git refs), and other ASCII data. The caller (``_has_valid_utf7_sequences``) already checks ``b64_len >= 3`` before calling this function, so *b64_bytes* is always at least 3 bytes. rr Fr iiTii)rr bytearrayrange)r n total_bits padding_bitslast_valmask num_bytesrawbit_buf bit_countout_idxc prev_highi code_units r_is_valid_utf7_b64r72sB IAQJ?Lay}-\!Q& d? aI I CGIG a<;q>1Q > NI#y0D8CL qLG I 1i!mQ 'Vq[CAJ. Y (& (I y *F *II(=rposcttdz}d}|dz }|dk\r*||}|dvr|dz}||vr |dz }|dz}n |dk\S|dk\r*|dk\S)aeReturn True if the ``+`` at *pos* is embedded in a base64 stream. Walks backward from *pos*, skipping CR/LF, and counts consecutive base64 characters (including ``=`` for padding). If 4 or more are found, the ``+`` is likely part of a PEM certificate, email attachment, or similar base64 blob rather than a real UTF-7 shift character. =rr$> )r frozenset)rr8 b64_with_padcountr5rs r_is_embedded_in_base64rAos$0)D/#AL E aA q& G  FA   QJE FA  A: q& A:rcd} |jtd|}|dk(ry|dz}|t|kr||tdk(r|dz}L|t|krX||tdk(rG|t|kr6||tdk(r%|dz }|t|kr||tdk(r%|}t||r|}|}|t|kr*||tvr|dz }|t|kr ||tvr||z }|||}|dk\r|j r|}|dk\r t |ryt||}<) asCheck that *data* contains at least one valid UTF-7 shifted sequence. A valid shifted sequence is ``+`` terminated by either an explicit ``-`` or any non-Base64 character (per RFC 2152). The base64 portion must decode to valid UTF-16BE with correct zero-padding bits. The sequence ``+-`` is a literal plus sign and is **not** counted. rT+r Fr$-)rordrrArislowerr7max)rr shift_posr8r5b64_lenb64_datas r_has_valid_utf7_sequencesrLsa E IIc#h. ?!m T?tCyCH4!GE  T?tCyCH4D /d3i3s8&;qD /d3i3s8&;E  "$ 2E  #d)mQ< 7 FA#d)mQ< 7c'A; arint enumeraterdictr7rArLrb)r5r3s00rrks G$6X EW(4 in41:*0EF0E1q!t0EF T#s(^F:%:D:zST09E9d9xOO?T+AOiGs A7