Dj4FUdZddlmZddlmZmZdedefdZdZ ee d<e e Z e e e d <e d Ze e e d <ee Dcic]\}}|| c}}Zee e fe d <d edefdZdede defdZdede fdZde defdZdedefdZdededzfdZycc}}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. )decodes_without_error)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 U/root/workspace/ytshorts/venv/lib/python3.12/site-packages/chardet/pipeline/escape.py z(_has_valid_hz_regions..%s6!DA%%%6s)findlenall)rstartbeginendregions r_has_valid_hz_regionsrs E  %' B;iiuqy) "9eai#& K1 F a1$6v66a s@ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789+/ _B64_CHARS _UTF7_BASE64sABCDEFGHIJKLMNOPQRSTUVWXYZ_B64_UPPERCASE _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_b64r:6sL 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)rr; b64_with_padcountr8rs r_is_embedded_in_base64rDss$0)D/#AL E aA q& G  FA   QJE FA  A: q& A:rb64_datac`t|ddzt|ddzzt|dzdz S)z@Decode the first (only) UTF-16 code unit of a single-unit block.r r'r%r )r")rEs r _single_unitrHsK Xa[ !R ' x{ #q ( * hqk " #   runitcd|cxkxrdkncxsjd|cxkxrdkncxsXd|cxkxrdkncxsFd|cxkxrdkncxs4d |cxkxrd kncxs"d |cxkxrd kncxsd |cxkxrdkScS)z>Script ranges where a lone shifted character plausibly occurs.iiii i+i0i0iNiiiiir)rIs r_plausible_lone_unitrLs $ &  $ T #V # $ T #V # $ T #V # $ T #V #  $ T #V #  $ T #V # $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\rt d |Ds|} |dk\r1t |r&|d zd zdk(rt|}t|s|}Uyt||}c) 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'-c3,K|] }|tvyw)N)r!rs rrz,_has_valid_utf7_sequences..s#JAA$7#Jsr%r&) rordrrDr anyr:rHrLmax)rr shift_posr;r8b64_lenrErIs r_has_valid_utf7_sequencesrWs E IIc#h. ?!m T?tCyCH4!GE  T?tCyCH4D /d3i3s8&;qD /d3i3s8&;E  "$ 2E  #d)mQ< 7 FA#d)mQ< 7c'A; a<#J#J JE  a<.x8! "a'#H-+D1EC G rNcd|v}d|v}d|v}|s|s|sy|rd|vsd|vsd|vrtdtd Sd |vrtd td Sd |vs d|vsd|vsd|vr,d|vrd|vrtd td Stdtd Sd|vrtdtd S|r%d|vr!d|vrt|rtdtd S|r7t|dkr)t |drt |rtdtd Sy)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_krkor r hzzhrKzutf-7)rrrrTrrW)rhas_esc has_tildehas_pluss rdetect_escape_encodingrlsd oG It|H 9X  t!3zT7I"*3   ")3   D D T!$7d?&-7!#'3   "%3 Ud]u}9Nt9T/    I  !$ 0 %d +/  r)__doc__chardet._utilsrchardet.pipelinerrbytesboolrr__annotations__rAr intr! enumerater"dictr:rDrHrLrWrl)r8r6s00rrvs 1F$6X EW(4 in4"++H!I #I1:*0EF1q!tF T#s(^F:%:D:zST0 5 S  s t LELdL^YY?T+AY{Gs B