Esther Payne :bisexual_flag:
boosted
@ShaulaEvans
Posted about this a while ago — #UNICODE is pondering the directionality issue and has been testing solutions
There I mention how it’d be easier for them to reverse a train 🚂 than all the pedestrian variants 🚶♂️➡️🚶🏻♂️➡️🚶🏼♂️➡️🚶🏽♂️➡️🚶🏾♂️➡️🚶🏿♂️➡️🚶🏿🚶🏼🚶🏽🚶🏻🚶🚶🏾🚶🏻🚶🏾
But they started with the people 🤷🏻♂️
https://mastodon.social/@AccordionBruce/111823648382625123
#emoji
@ShaulaEvans
Posted about this a while ago — #UNICODE is pondering the directionality issue and has been testing solutions
There I mention how it’d be easier for them to reverse a train 🚂 than all the pedestrian variants 🚶♂️➡️🚶🏻♂️➡️🚶🏼♂️➡️🚶🏽♂️➡️🚶🏾♂️➡️🚶🏿♂️➡️🚶🏿🚶🏼🚶🏽🚶🏻🚶🚶🏾🚶🏻🚶🏾
But they started with the people 🤷🏻♂️
https://mastodon.social/@AccordionBruce/111823648382625123
#emoji
A free tool that stuns LLMs with thousands of invisible Unicode characters
#HackerNews #A #free #tool #that #stuns #LLMs #with #thousands #of #invisible #Unicode #characters #gibberifier.com #LLMs #Unicode #characters #AI #tools #tech #news
Unicode Binary Input Terminal
https://hackaday.io/project/192644-unicode-binary-input-terminal
#HackerNews #Unicode #Binary #Input #Terminal #Hackaday #Project #Technology #Innovation #Coding
Aw bummer! My #emoji "circuit board" proposal was denied. Oh well, at least I tried :)
(previously: https://icosahedron.website/@greg/114763923868354196)
Pretty messed up that umlaut doesn't have an umlaut.
Ţ̴̨᷿̰͈͎͓̩̿͢H̵̲̙̘̭̺̺̰̹̞̤̓᷄̈́͊̃̋͘Â̶̢̢̡̛̼̖͕̰̞̪T̸̨̡̧̢̧͈̗̻̖̱ͭͥͣ͆̄ͪ̋͌̓’̵̛͚͕͔᷊͓̼̉̋̿ͫ͊͒̔͊͛s̴̻̜̲̹̖̝᷅̉᷄᷄̄͞ W̶̦̗̏︣᷅H̶̨̝̙̺͓͌̅̋͘͟À̴̺̤͉̦̖̝̿͌ͦ́᷆̽͜Ţ̶᷿͕̝̬̣̪̰̆᷅́͆́᷉̐ͬ͒͢͢ S̴̘̭̞᷂̜̤͑͌̀ͪ︡ͧ̓̃᷅ͦ͢H̵͕̱̬̭̠͑ͪ͆̀᷉̈́︣͢E̴̻̖̬̠ͯ̈́͐ S̷̨̩̖̠̘᷿̝᷀̔᷅̇́̃͢͞A̶̭̪̭̟̦̞̘̼ͩ͢I̶̳͑᷁̂︣̆̂̍̀̕D̵̺̤̅ͯ̑͆᷾
vruz
boosted
the most important part of #Unicode history is when a mouse fell out of a light fixture and got added to the count of members present at a Technical Committee meeting (9 Nov 2016)
RE: https://hachyderm.io/@SnoopJ/109921008429679600
Happy #Unicode Mouse day to those who celebrate
the most important part of #Unicode history is when a mouse fell out of a light fixture and got added to the count of members present at a Technical Committee meeting (9 Nov 2016)
RE: https://hachyderm.io/@SnoopJ/109921008429679600
Happy #Unicode Mouse day to those who celebrate
A new Hebrew-related Unicode proposal... I hate being a gatekeeper, and I know nothing about the Babylonian Messorah, but a private proposal without any significant affiliation looks like a safe bet to have even more Unicode mess, like the one we are already having with the combining classes of Tiberian cantillation marks. Just saying... 🙃
https://www.unicode.org/L2/L2025/25268-babylonian-proposal.pdf
![Mike [SEC=OFFICIAL]](https://static.chinwag.net.au/accounts/avatars/000/000/001/original/b02e2e0cd4f0ffe5.jpg "Mike [SEC=OFFICIAL]")
It should be illegal to give codenames to subsequent OS versions that begin with the same letter as the previous one.
I'm looking directly at you, Debian and Apple.
Jail.
RE: https://mastodon.social/@reiver/115352274818575263
This probably means that someone should modernize HTTP by creating HTTP/1.4.
alcinnz
boosted
Google more-or-less created 2 new versions of the HTTP protocol — HTTP/2 and HTTP/3 —
But didn't bother make either of them (officially) support UTF-8 in the HTTP request.
Google more-or-less created 2 new versions of the HTTP protocol — HTTP/2 and HTTP/3 —
But didn't bother make either of them (officially) support UTF-8 in the HTTP request.
#DNS
Regardez le nom de domaine affiché sur https://monlycee.net/
Ensuite, testez ce nom dans le DNS.
Enfin, écrivez à Valérie Pécresse pour lui signaler.
monlycée.net est désormais réparé. https://www.bortzmeyer.org/monlycee.html
Dans le coffre aux trésors d’Unicode 17 : des chameaux et un trombone : https://linuxfr.org/news/dans-le-coffre-aux-tresors-d-unicode-17-des-chameaux-et-un-trombone
d@nny disc@ mc²
boosted
IMO the reason most people don't know that there are official guidelines on what #Unicode codepoint sequences constitute a valid identifier is because languages largely don't bother to even discover that the standard exists, let alone implement it.
#Python is an exception to the rule, it has had UAX#31 support since Python 3.0¹²
C++ has switched over to this standard as of C++23 although I do not know all of the details. Fun fact: gcc and Clang are both perfectly happy to let you use a zero-width space in an identifier in earlier versions of C++.
¹ https://docs.python.org/3.0/reference/lexical_analysis.html#identifiers-and-keywords
² see PEP 3131 for historical details: https://peps.python.org/pep-3131/
IMO the reason most people don't know that there are official guidelines on what #Unicode codepoint sequences constitute a valid identifier is because languages largely don't bother to even discover that the standard exists, let alone implement it.
#Python is an exception to the rule, it has had UAX#31 support since Python 3.0¹²
C++ has switched over to this standard as of C++23 although I do not know all of the details. Fun fact: gcc and Clang are both perfectly happy to let you use a zero-width space in an identifier in earlier versions of C++.
¹ https://docs.python.org/3.0/reference/lexical_analysis.html#identifiers-and-keywords
² see PEP 3131 for historical details: https://peps.python.org/pep-3131/
Most people don't really know that the #Unicode Consortium publishes extremely well-defined guidelines on identifiers.
https://www.unicode.org/reports/tr31
The most familiar example is the sort who has a whole soapbox rant about how emoji are bad.
If that Hypothetical Guy makes reference to how some languages allow emoji in identifiers, they may not realize how much of their ass they are baring to the world, because in fact, the default guidelines don't allow them! The languages they are bitching about as a rule are not following the Unicode Consortium's guidance on identifiers, but some ad-hoc rules which are usually missing large swaths of conventional wisdom.
One of the cool things about UAX#31 though is that it allows you to create custom "profiles", changing up the rules a bit about what is or is not valid in an identifier to your own liking without entirely discarding the valuable wisdom of people who spend their professional lives thinking about these Hard Problems.
Anyway, the distinction between Recommended Scripts and Limited Use Scripts is along similar lines:
Recommended Scripts are the sort that UAX#31 thinks you probably should implement because they are "in widespread modern customary use".
Limited Use Scripts are ones that are less "encouraged" and which you might want to disallow as an implementer of the standard. It's not that they're disallowed, but they're not being encouraged.
For the sake of completeness, there are also Excluded Scripts which as the name suggests are recommended against because they are archaic/etc.