4 ms·

Ah so that's how we're supposed to Google for tweets now. "𝕏 something something".

voxadam 3y ago
𝕏 (U+1D54F) decomposes[0] to X (U+0058) meaning that if you search for 𝕏 your search string will likely be automatically converted to the equivalent X. Of course, while a search engine could conceivably index and search the entire Unicode codespace internet wide, such a task would likely be somewhat unrealistic and provide only limited upside. [0] https://en.wikipedia.org/wiki/Unicode_equivalence https://en.wikipedia.org/wiki/Unicode_equivalence
- calderknight 3y ago
  i presume x.com or site:x.com will get the trick done
- PaulHoule 3y ago
  It’s already got to search 1000s of Chinese characters, a few more doesn’t make a big difference.
  - voxadam 3y ago
    How do you decide which characters to index? The current Unicode release (15.0) includes 149,186 individual characters. I suppose you can probably ignore U+237C (Right Angle with Downwards Zigzag Arrow) seeing as nobody seems to know what it denotes.[0][1] [0] https://news.ycombinator.com/item?id=31012865 https://news.ycombinator.com/item?id=31012865 [1] https://ionathan.ch/2022/04/09/angzarr.html https://ionathan.ch/2022/04/09/angzarr.html
    - NoGravitas 3y ago
      That is Ellis.
    - PaulHoule 3y ago
      Most search engines for languages like English are indexing words as opposed to characters so choices as to what characters are indexed are made as part of deciding which words to index. Search engines for CJK languages do tend to work at the character level so a search for “Sona” on a certain site run by (I think) Chinese people will turn up result for “Persona”. I was involved with an A.I. startup where we had lots of meetings about what to do about all the strange Unicode characters and right now in Mastodon there is a lot of concern that screen readers will choke on 𝐮𝐧𝐢𝐜𝐨𝐝𝐞 𝐛𝐨𝐥𝐝 𝐜𝐡𝐚𝐫𝐚𝐜𝐭𝐞𝐫𝐬 while it doesn’t seem that difficult to squash them down to ordinary characters or treat them exactly as <b>unicode bold characters</b>
- layer8 3y ago
  The essential operation here is not decomposition, but compatibility normalization. Both NFKC and NFKD result in a regular “X”.
deleted 3y ago
[deleted]
b800h 3y ago
No, you're supposed to go to X and search on there. And consume ads.

𝕏 (U+1D54F) decomposes[0] to X (U+0058) meaning that if you search for 𝕏 your search string will likely be automatically converted to the equivalent X. Of course, while a search engine could conceivably index and search the entire Unicode codespace internet wide, such a task would likely be somewhat unrealistic and provide only limited upside. [0] https://en.wikipedia.org/wiki/Unicode_equivalence https://en.wikipedia.org/wiki/Unicode_equivalence

calderknight 3y ago
i presume x.com or site:x.com will get the trick done
PaulHoule 3y ago
It’s already got to search 1000s of Chinese characters, a few more doesn’t make a big difference.
- voxadam 3y ago
  How do you decide which characters to index? The current Unicode release (15.0) includes 149,186 individual characters. I suppose you can probably ignore U+237C (Right Angle with Downwards Zigzag Arrow) seeing as nobody seems to know what it denotes.[0][1] [0] https://news.ycombinator.com/item?id=31012865 https://news.ycombinator.com/item?id=31012865 [1] https://ionathan.ch/2022/04/09/angzarr.html https://ionathan.ch/2022/04/09/angzarr.html
  - NoGravitas 3y ago
    That is Ellis.
  - PaulHoule 3y ago
    Most search engines for languages like English are indexing words as opposed to characters so choices as to what characters are indexed are made as part of deciding which words to index. Search engines for CJK languages do tend to work at the character level so a search for “Sona” on a certain site run by (I think) Chinese people will turn up result for “Persona”. I was involved with an A.I. startup where we had lots of meetings about what to do about all the strange Unicode characters and right now in Mastodon there is a lot of concern that screen readers will choke on 𝐮𝐧𝐢𝐜𝐨𝐝𝐞 𝐛𝐨𝐥𝐝 𝐜𝐡𝐚𝐫𝐚𝐜𝐭𝐞𝐫𝐬 while it doesn’t seem that difficult to squash them down to ordinary characters or treat them exactly as <b>unicode bold characters</b>
layer8 3y ago
The essential operation here is not decomposition, but compatibility normalization. Both NFKC and NFKD result in a regular “X”.

deleted 3y ago

[deleted]

b800h 3y ago

No, you're supposed to go to X and search on there. And consume ads.