޺ia*%SrSSKJrJr S\S\4SjrSr\\S'\ "\5r \ \ \S'\ "\5VVs0sHupX_M snnr \\ \ 4\S 'S \S\4S jrS\S \ S\4S jrS\S\4SjrS\S\S-4Sjrgs snnf)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_CONFIDENCEDetectionResultdatareturncSnURSU5nUS:XagURSUS-5nUS:XagXS-Un[U5S:a*[U5S-S:Xa[SU55(agUS-nM|) zCheck 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~}c3L# UHnSUs=:*=(a S:*Os v M g7f)!~N).0bs V/var/www/piano.thomer.com/venv/lib/python3.13/site-packages/chardet/pipeline/escape.py (_has_valid_hz_regions..$s 6v!DA%%%%vs"$)findlenall)rstartbeginendregions r_has_valid_hz_regionsrs E  %' B;iiuqy) "9ai#& K1 F a1$6v666a s@ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789+/ _B64_CHARS _UTF7_BASE64 _B64_DECODE b64_bytesc[U5nUS-nUS-nUS:a[USnSU-S- nXE-(agUS-n[U5nSnSn Sn UH2n US-[U -nU S- n U S:dMU S-n X- S-Xz'U S- n M4 Sn [SUS- S 5HWn X}S-X}S--nS Us=::aS ::aO O U (a gS n M/S Us=::aS::aO O U (d gSn MLU (a gSn MY U (+$)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_b64r82s8 IAQJ?Lay}-\!Q& ? aI I CGIG a<;q>1Q > NI#0D8CL qLG I 1i!mQ 'Vq[CAJ. Y (& (I y *F *II(=rposc[[S5-nSnUS- nUS:a/XnUS;aUS-nMXR;a US- nUS-nOUS:$US:aM/US:$)aQReturn 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)rr9 b64_with_padcountr6rs r_is_embedded_in_base64rBos|$0)D/#AL E aA q& G  FA   QJE FA  A: q& A:rcSnUR[S5U5nUS:XagUS-nU[U5:aX[S5:XaUS-nMOU[U5:a\X[S5:XaKU[U5:a8X[S5:Xa'US- nU[U5:aX[S5:XaM'UnM[X5(aUnMUnU[U5:a.X[;a"US- nU[U5:aX[;aM"XC- nXUnUS:aUR 5(aUnGM5US:a[ U5(ag[X45nGMY) a_Check 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%-)rordrrBrislowerr8max)rr shift_posr9r6b64_lenb64_datas r_has_valid_utf7_sequencesrMsV E IIc#h. ?!m T?tyCH4!GE  T?tyCH4D /di3s8&;qD /di3s8&;E  "$ 2 2E  #d)m< 7 FA#d)m< 7'A; arls G$6X EW(4 in41:*0EF0Eqt0EF T#s(^F:%:D:zST09E9d9xOO?T+AOiGsA=