Here is a quick lesson in UTF-8.
UTF-8 encodes the entirety of Unicode in chunks of 1 to 4 bytes.
If you are given a random index within a string encoded in UTF-8, you can find the beginnings of the characters before and after that index.
If the current byte is an ASCII character, then it is an ASCII character.
Hei #DigitalScholarlyEditions #TEIXML crowd!
I have a question for you: have you ever used the #Unicode symbol for insertion of a character or word into a text, U+2380 ⎀?
Or how would you encode the insertion mark in a text?
In the #OscarMamen pocket diaries, the insertion mark is used frequently and I would like to encode it somehow.
Suggestions? Examples?
I feels that I cannot get any good results googling anymore: #Enshittification of the search engine, I guess...
Newly covered #Unicode code points in #iOS 26.
I have to admit I have not updated anything to 26 yet. At least on Mac I usually wait for #MacPorts issues to be cleared up, but this one might take me a while...
㇀㇁㇂㇃㇄㇅㇆㇇㇈㇉㇊㇋㇌㇍㇎㇏㇐㇑㇒㇓㇔㇕㇖㇗㇘㇙㇚㇛㇜㇝㇞㇟㇠㇡㇢㇣𞓐𞓑𞓒𞓓𞓔𞓕𞓖𞓗𞓘𞓙𞓚𞓛𞓜𞓝𞓞𞓟𞓠𞓡𞓢𞓣𞓤𞓥𞓦𞓧𞓨𞓩𞓪𞓫𞓮𞓯𞓬𞓭𞓰𞓱𞓲𞓳𞓴𞓵𞓶𞓷𞓸𞓹𠁣𠃛𠊎𠖄𠖫𠗻𠘆𠜖𠞩𠞭𠠃𠠝𠠫𠢕𠴭𠺅𠺣𠻞𡌴𡟓𡨞𡳞𡽜𢄧𢎙𢒉𢓜𢛟𢜳𢬳𢯭𢯾𢱤𢲴𢳪𢶀𢺴𢻷𢼌𢼛𢿞𣁳𣍐𣗺𣦼𣩈𣮈𣲩𣸤𣼎𤁢𤊶𤍒𤐙𤐰𤖯𤘅𤞚𤡯𤲍𤶃𤸁𤺅𤺪𤿎𥉔𥌚𥍉𥏘𥐵𥯟𥯥𥰔𥴊𥽕𦃓𦉎𦊓𦒨𦘅𦜆𧉅𧉟𧌄𧜞𧩣𧮙𧰵𧺤𧻴𧿳𨂿𨅔𨒇𨢑𩏠𩑾𩔵𩚨𩛩𩜄𩜇𩜰𩟗𩣳𩨑𩵱𩸙𩼧𪀋𪐞𪖐𪖶𪘒𪜶𪢼𪳕𪹚𫓩𫝏𫝘𫝙𫝞𫝺𫝻𫞭𫞼𫟂𫟊𫟧𫠄𫠛𫣆𫰡𬈜𬏛𬠖𬤐𬦰𬬺𬮤𮀎𮣳𮭦𮯴𰣻𰵝𰵞𰵧𰹬𰾫𱂐𱮒𱱿𱳪𲂎
we are all \u1FAEA
Any guesses why macos Characterviewer lists guillemetleft and guillemetright under “Parentheses”? The guillemets share their Unicode category Pi / Pf with quotedblleft and quotedblright. The guillemets are missing from “Punctuation” and even “Punctuation - All”. Are these really used as parens? Seems like a personal selection. #macos #unicode #categories
«»“”()[]
guillemetleft Pi
guillemetright Pf
quotedblleft Pi
quotedblright Pf
parenleft Ps
parenright Pe
bracketleft Ps
bracketright Pe
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
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.
#Unicode 17.0.0 includes a bunch of script updates, some fun new symbols — including astronomical symbols for asteroids!
My favorite change is a fairly obscure tweak to Unicode Standard Annex #31, which defines guidelines and requirements for which codepoint sequences form valid identifiers (e.g. for programming languages)
The Bopomofo script (Zhùyīn fúhào) for phonetically representing Chinese was previously considered a "Recommended script" but has been recategorized as a "Limited use script" because it is generally used in educational contexts.
Mistodon: @mc.fresher drew the Hell out of this #Unicode #textmode art tribute to #MamoruOshii's surreal post-apocalyptic 1985 OVA #AngelsEgg. We nearly shared it in our May SF artpack, but kept it as seed stock for last month's new MIST0825 #anime - themed artpack.
Android will *not* be getting most of the Unicode 17 updates.
Some of its fonts are over a decade out of date - and Google refuses to re-use its own Noto font stack.
I've raised the issue at:
https://issuetracker.google.com/issues/366415133
If you're a Googler please ask someone to prioritise this issue. Can everyone else please hit the +1 button.
Today’s fun Unicode character: Multiocular O, aka biblically accurate angel: ꙮ
h/t benji
La version 17 d'#Unicode vient de sortir. Une description officielle des principaux changements est disponible mais voici ceux qui m'ont intéressé particulièrement. (Il n'y a pas de changement radical.) https://www.bortzmeyer.org/unicode-17-0.html
#Development #Techniques
Text lengths with ‘Intl.Segmenter’ API · Human-friendly character counting in JavaScript https://ilo.im/166lco
_____
#Characters IntlSegmenter #API #JavaScript #Unicode #UTF8 #UTF16 #Browser #WebDev #Frontend
Avec @MoritzBrouhaha découvrez l'histoire du standard informatique Unicode, utilisé par tout le monde à travers le globe dans nos communications quotidiennes.
https://www.paris-web.fr/2025/conference/a-la-decouverte-du-monde-au-travers-de-lunicode
Je viens de passer une excellente après-midi au parc à discuter avec un inconnu des Béri (ceux dont le système d'écriture est "l'écriture des chameaux", de l'Unicode, des langues sahariennes, de l'hobyot et de ce genre de choses.
Maintenant il faut que je lui précise comment ajouter un système d'écriture à l'Unicode ou des caractères.
string.length() is lying to you.
Unicode in Java is more complex than many realize. In this hands-on tutorial, I show how to handle code points, normalization, and emoji correctly with a Quarkus REST API.
https://www.the-main-thread.com/p/java-unicode-rest-api-quarkus
I just learned how to type unicode letters and dingbats in Linux!
Ctrl + Shift + U press all 3 keys at once then let all three letters go.
then type in the unicode and press enter.
https://en.wikipedia.org/wiki/List_of_Unicode_characters
IE.
Ctrl + Shift + U 2713 is a tick or check mark
✓
Similarly, I can write ñ (n tilde) with:
ctrl + shift + U 00f1
See dingbats block for more check mark choices.
https://en.wikipedia.org/wiki/Dingbats_(Unicode_block)
All of unicode here:
https://home.unicode.org/
