monlycée.net est désormais réparé. https://www.bortzmeyer.org/monlycee.html

#IDN #Unicode #DNS

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

#Unicode

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.

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.

anyway, #Unicode 17.0.0 is out

https://blog.unicode.org/2025/09/unicode-170-release-announcement.html

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

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

#unicode #standards #typographie #internationalisation

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

#unicode #standards #typographie #internationalisation

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.

@bortzmeyer

#unicode

Je viens de me rendre compte que l'emoji « Trognon de pomme », qui avait été pré-approuvé pour la version 17 d'#Unicode (publication bientôt), a finalement été retiré et sera peut-être dans la version 18.

@Ysabeau

Each time i use https://shapecatcher.com
I'm gratefull to #BenjaminMilde to have build it and keep it running.
"You know what some #character looks like, but you've forgotten its name or its #Unicode code point. Now what do you do? #Shapecatcher is a new website, that helps you to find specific Unicode characters, just by #sketching their shape. Currently about 10000 of the most important Unicode characters are compared to your sketch and are analysed for similarities.
Under the hood, Shapecatcher uses so called " #shape contexts" to find similarities between two shapes. Shape contexts, a robust mathematical way of describing the concept of similarity between shapes, is a feature descriptor first proposed by #SergeBelongie and #JitendraMalik."

Each time i use https://shapecatcher.com
I'm gratefull to #BenjaminMilde to have build it and keep it running.
"You know what some #character looks like, but you've forgotten its name or its #Unicode code point. Now what do you do? #Shapecatcher is a new website, that helps you to find specific Unicode characters, just by #sketching their shape. Currently about 10000 of the most important Unicode characters are compared to your sketch and are analysed for similarities.
Under the hood, Shapecatcher uses so called " #shape contexts" to find similarities between two shapes. Shape contexts, a robust mathematical way of describing the concept of similarity between shapes, is a feature descriptor first proposed by #SergeBelongie and #JitendraMalik."

Three small announcements:
1. RFC 9839, a guide to which Unicode characters you should never use: https://www.rfc-editor.org/rfc/rfc9839.html
2. Blog piece with background and context, “RFC 9839 and Bad Unicode”: https://www.tbray.org/ongoing/When/202x/2025/08/14/RFC9839
3. A little Go library that implements 9839’s exclusion subsets: https://github.com/timbray/RFC9839

#Unicode