fjs+UdZddlmZmZdedefdZdZeed<e eZ e e ed<d e eDZ ee e fed <d edefd Zded e defdZdedefdZdededzfdZdS)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_CONFIDENCEDetectionResultdatareturnc4d} |d|}|dkrdS|d|dz}|dkrdS||dz|}t|dkr1t|dzdkrtd|DrdS|dz}) 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~}c36K|]}d|cxkodkncVdS)!~N).0bs kC:\Users\Terasoftware\OneDrive\Desktop\faahhh\fyndo\fyndo\venv\Lib\site-packages\chardet/pipeline/escape.py z(_has_valid_hz_regions..$s>66!DA%%%%%%%%666666)findlenall)rstartbeginendregions r_has_valid_hz_regionsrs E %'' B; 5iiuqy)) "9 5eai#o& KK1  F a1$ 66v66666  4ars@ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789+/ _B64_CHARS _UTF7_BASE64ci|]\}}|| Srr)rics r r"/sFFF1q!FFFr _B64_DECODE b64_bytesct|}|dz}|dz}|dkr"t|d}d|zdz }||zrdS|dz}t|}d}d} d} |D]5} |dzt| z}| dz } | dkr| dz} || z dz|| <| dz } 6d} td|dz d D]P} || dz|| dzz}d |cxkrd kr nn| rdSd } 1d |cxkrdkr nn| sdSd} I| rdSd} Q| 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_idxr! prev_highr code_units r_is_valid_utf7_b64r92s IAQJ?Lay}-\!Q& d? 5 aI I  CGIG a<;q>1Q >  NI#y0D8CL qLGI 1i!mQ ' '  Vq[CAJ. Y    &      uuII y    F      uuII uuII=rposcttdz}d}|dz }|dkr(||}|dvr|dz}||vr |dz }|dz}nn|dk(|dkS)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)rr: b64_with_padcountr rs r_is_embedded_in_base64rCos$0)D//#AL E aA q&  G   FA    QJE FAA  q&  A:rcNd} |td|}|dkrdS|dz}|t|kr||tdkr|dz}c|t|kry||tdkr`|t|krJ||tdkr1|dz }|t|kr||tdk1|}t||r|}|}|t|kr6||tvr'|dz }|t|kr||tv'||z }|||}|dkr|r|}{|dkrt |rdSt||}) 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(-)rordrrCrislowerr9max)rr shift_posr:r b64_lenb64_datas r_has_valid_utf7_sequencesrNs E0IIc#hh.. ? 5!m T? tCyCHH4 !GE  T? tCyCHH4 D / d3i3s88&; qD / d3i3s88&; E  "$ 2 2 E  #d))m Q< 7  FA#d))m Q< 7 c'A; a< H,,.. E  a< .x88 4C a0rNcFd|v}d|v}d|v}|s|s|sdS|rd|vsd|vsd|vrtdtd Sd |vrtd td Sd |vs d|vsd|vsd|vr6d|vrd|vrtd td Stdtd Sd|vrtdtd S|r.d|vr*d|vr&t|rtdtd S|r9t|dkr&t |rtdtd SdS)zDetect ISO-2022, HZ-GB-2312, and UTF-7 from escape/tilde/plus sequences. :param data: The raw byte data to examine. :returns: A :class:`DetectionResult` if an escape encoding is found, or ``None``. ~+Ns$(Os$(Ps$(Qiso2022_jp_2004ja)encoding confidencelanguages(Iiso2022_jp_exts$Bs$@s(Js$(D iso2022_jp_2s$)C iso2022_krkorr hzzhzutf-7)rrrrJrN)rhas_esc has_tildehas_pluss rdetect_escape_encodingrds oG It|H 9Xt-   t!3 zT7I "*3    ")3    D  D  T!  $ 7d? &-7!#'3    "%3  Ud] u} 9Nt9T9T /     CII$ )B4)H)H /    4r)__doc__chardet.pipelinerrbytesboolrr__annotations__r@rint enumerater#dictr9rCrNrdrrrrms]   GFFFFFFF$6X EWWW(y44 in444GF *0E0EFFF T#s(^FFF:%:D::::zST09E9d9999xOO?T+AOOOOOOr