soj-_ddlZddlZddlZddlZddlZddlmZddlmZm Z m Z ddlm Z ddl mZddlmZddlmZmZmZmZmZmZmZmZmZmZddlZddlmZdd lm Z dd l!m"Z"dd l#m$Z$dd l%m&Z&m'Z'dd l(m)Z)ddl*m+Z+e j,dZ-dZ.ej/0ej1ddfej/0ej1ddfdZ2ej/0ej1dZ3ddddddddZ4de5d e5dzfd!Z6d"e5d e7e8e5e5dzffd#Z9d"e5d ejfd$Z:d%e5d e5dzfd&Z;de5d e5fd'Z< d7d(ed)e"d e5fd*Z=d)e"d+e5d,e5d-e5dzd.e5dzd/e5d0e5d e5fd1Z>d2e d e?fd3Z@d8d5eAd dfd6ZBdS)9N) confusables)Image ImageDraw ImageFont)features)Update) unidecode) WantedPosterVerticalAlignmentCaptureConditionEffectStampBOUNTY_POSTER_NAME_TEXTURE_PATHBOUNTY_POSTER_NAME_FONT_SIZEBOUNTY_POSTER_NAME_MAX_WBOUNTY_POSTER_NAME_HBOUNTY_POSTER_NAME_START_Y) Leaderboard)LeaderboardUser)User)BossType)LeaderboardRankget_rank_by_index)user_has_eaten_devil_fruit)generate_temp_file_pathraqmUnknownzNotoSansArabic-Bold.ttfrtlzNotoSansDevanagari-Bold.ttfltr)ARABIC DEVANAGARIzBlogger_Sans-Bold.otfRCLEHWM)uᖇuᑢuᒪuᘿuᎻuᏯuᎷnamereturnc|D]v}|s|s+ tj|}n#t$rYMwxYwt D]}||r|ccSwdS)a Detects whether a name is written in a script we can show as-is on the poster (see NATIVE_SCRIPT_FONT_MAP), by checking each character's Unicode name (e.g. a character named "ARABIC LETTER SEEN" belongs to the "ARABIC" script) :param name: The raw name, as it is on Telegram :return: The script name (a key of NATIVE_SCRIPT_FONT_MAP) if found, otherwise None N)isspaceisalpha unicodedatar) ValueErrorNATIVE_SCRIPT_FONT_MAP startswith)r)char char_namescripts )/app/src/service/bounty_poster_service.pyget_native_scriptr6Vs   <<>>    #(..II    H -  F##F++     4sA AAtextcg}d}d}|D]}d}tj|dr|}n_|rK tj|}n#t $rd}YnwxYwt D]}||r|}n||kr||z }|r|||f|}|}|r|||f|S)uT Segments text into contiguous runs of a single native script (see NATIVE_SCRIPT_FONT_MAP) or plain Latin/neutral characters (Latin letters, digits, punctuation, spaces), so a name that mixes scripts (e.g. "apple سیب FARZIN") can have each part rendered with a font that actually supports it, instead of forcing the whole string through a single script's font. :param text: The text to segment :return: A list of (segment_text, script) tuples in original order. script is a key of NATIVE_SCRIPT_FONT_MAP for a native-script run, or None for a Latin/neutral run Nr()r.categoryr1r-r)r/r0append)r7runs current_textcurrent_scriptr2 char_scriptr3r4s r5_segment_by_scriptr@os:*,DL!%N))   % % 0 0 5 5  )KK \\^^  ',T22      1  ''//"(KE . ( ( D LL < \>:;;;L(NN4 \>2333 Ks A!! A0/A0c t|}i|D]q\}}|vr |%tjttdf|<1t |\}}tj|ttjj|f|<rtj t}|j \}}tj d||f} tj| fd|D} t| } d} | t kr4t#| |zt z } tj d| |f}d} ntj d||f}tj|}|j d| z d z }t%|| D]@\\}}}|\}}|||d z zt(f||d d | ||z }A| r|||f}|||S) u Builds the name texture component for a name that mixes native-script text (see NATIVE_SCRIPT_FONT_MAP) with Latin/neutral text (e.g. "apple سیب FARZIN"), rendering each part with a font that actually supports it, positioned side by side in their original order. Without this, the whole string would be forced through a single native-script font (e.g. NotoSansArabic), which doesn't cover Latin characters -- those would show up as unsupported-glyph placeholder boxes instead of actual letters. Uses a texture + alpha mask, auto-scaling if the combined text is too wide, but draws each script run with its own font/direction instead of a single one for the whole string. :param text: The full name text, in its original (possibly mixed) script :return: The name component image, ready to paste over the poster at (0, BOUNTY_POSTER_NAME_START_Y) Nr) layout_enginer$cvg|]5\}}||d|d6S)r)font direction) textlength).0run_textr4fonts_and_directionsmeasuring_draws r5 z6_build_mixed_script_name_component..sa Hf !! %f-a0*6215 "  FTrwhitems)rEfillanchorrF)r@rtruetypeLATIN_NAME_FONT_PATHrr0LayoutRAQMropenrsizenewrDrawsumrintzipr7rresizeputalpha)r7r<_r4 font_pathrFtexture_backgroundtexture_background_wtexture_background_hmeasuring_alpha run_widthstotal_w should_scalenew_walphadraw current_xrIrun_wrErJrKs @@r5"_build_mixed_script_name_componentrnso d # #DQS 6 ) ) )  >"#79UVV,  ( ( $:&#A Iy";9K[K` ,  ( ($CDD1C1H..i&:% DA(A-I%(z%:%:  !6E.v6i  "$8 9      U K 24HIJJ&&& rMr2c$tj|d}|sdS|D]r}|dgD]Y}|dd}t|dkr.|r|r|ccSZsdS)aY General-purpose fallback for FANCY_FONT_LOOKALIKE_CHAR_MAP, for "fancy font" look-alike characters that haven't been reported/added there yet. Looks up Unicode's own official "confusables" data (the same dataset used for anti-phishing/anti-spoofing detection, listing characters from any script that are visually confusable with one another) for a plain ASCII letter/digit that this character could be mistaken for. Only called for non-ASCII characters, since otherwise this would find characters that look like an existing ASCII letter and "correct" the letter into a different one (e.g. it considers "l" a look-alike of "1", which would wrongly replace a legitimate "1" with "l") :param char: A single non-ASCII character :return: A single ASCII letter/digit if a confident look-alike is found, otherwise None T)greedyN homoglyphscr9rD)r is_confusablegetlenisasciiisalnum)r2matchesmatch homoglyph candidates r5_get_homoglyph_latin_letterr|s'T:::G t!!<44 ! !I! c2..I9~~""y'8'8':':"y?P?P?R?R"       ! 4rMc>|sdSg}|D]}|r|d-|tvr!|t|Wt|}t |dkr*|r|||s't|}||||r)|r||tj ddd |}tj dd|}tj dd|S)u3 Sanitizes a name for use on a wanted poster, for scripts that aren't shown as-is (see NATIVE_SCRIPT_FONT_MAP / get_native_script). The poster font only supports latin characters, so names are normally transliterated with unidecode. The problem is that unidecode doesn't just transliterate, it also *describes* characters it has no real letter equivalent for (e.g. the chess piece "♚" becomes the phrase "black king", an emoji becomes a description, etc.). Those descriptions would otherwise be added to the name, making it longer than it should be and, in the worst case, pushing it past the point where it gets discarded entirely, resulting in a blank name on the poster. To support as many characters as possible while avoiding that, every character is transliterated individually and only kept if the result is a clean word with no spaces in it (e.g. "Ⓐ" -> "A", "Ω" -> "O", "你" -> "Ni", "Ⅷ" -> "VIII" are all kept). Characters whose transliteration is a description made up of multiple words (e.g. "♚" -> "black king") or that have no latin equivalent at all (most emoji) are discarded instead of being spelled out. Known "fancy font" look-alike characters (see FANCY_FONT_LOOKALIKE_CHAR_MAP) are mapped to their intended Latin letter directly, bypassing unidecode, since unidecode would otherwise transliterate them based on their unrelated real meaning instead of their intended visual appearance. Any other non-ASCII look-alike not in that map is checked against Unicode's official confusables data (see _get_homoglyph_latin_letter) as a general safety net, before finally falling back to unidecode :param name: The raw name to sanitize, as it is on Telegram :return: The sanitized name, safe to pass to the poster generator r9 rDNz\s+z[^A-Za-z0-9 '\-.]) r,r;FANCY_FONT_LOOKALIKE_CHAR_MAPr striprurwrvr|resubjoin)r) kept_charsr2transliteratedrzcleaneds r5get_bounty_poster_namers< rJ&.&. <<>>    c " " "  0 0 0   ;DA B B B "4..00 ~  ! # #(>(>(@(@ #   n - - - ||~~ 3D99I$!!),,,  .n4466 .   n - - -fVS"''*"5"566<<>>Gf)2w77G 6&#w ' ' - - / //rMupdateuserc Kddlm}|jpd}|jpd}d}t rt |pt |}|r|d|nd}|rd}d} n)t|}t|} |s | st}|||d{V} tj t|| || |||| d{VS)z Gets the bounty poster of a user :param update: Telegram update :param user: The user to get the poster of :param telegram_user: Optional Telegram user to fetch the portrait for :return: The path to the poster r)get_user_profile_photor9Nr~) src.service.user_servicer tg_first_namer tg_last_nameRAQM_AVAILABLEr6rBOUNTY_POSTER_FALLBACK_NAMEasyncio to_thread_generate_poster_sync) rr telegram_userrraw_first_name raw_last_name native_scriptnative_script_textposter_first_nameposter_last_nameportraits r5get_bounty_posterrbsb@?????(.B5577N&,"3355M M^).99]=N}=]=] HU_N<<]<<BBDDD[_ <3>BB1-@@! <)9 < ; ++FMBBBBBBBBH"          rMrrrrrrc ddlm}t||||j} tj} g} d} t |r tj} ||} | dtj fvr tj } | xtj kr-| tj tj } n}xtjkrn$xtjkrnxtjkrnnH| tj| tjur tj} n tj} | t-t.jt2j| | | d}|r t7|}t9j|d}||dt@f||!|n#tD$r}tGj$d|tK|}tK|}|s |stL}t| j'|||j}||t2j| | | d}Yd}~nd}~wwxYw|S)a Does the actual CPU-bound poster generation (font loading/shaping, image compositing, resizing, disk I/O) synchronously. Only ever called through asyncio.to_thread from get_bounty_poster, so this blocking work runs on a separate thread instead of stalling the single-threaded event loop (and with it, every other scheduled task in the Bot - e.g. a game's start countdown - for however long generation takes) while it runs :return: The path to the generated poster r) get_boss_type)r first_name last_namebountyN)output_poster_pathportrait_vertical_aligncapture_conditioneffectsstampfull_name_max_lengthRGBz