The Unicode Blog

The Unicode Blog
skip to main
skip to sidebar
News, announcements, release info, and calendar updates
from the Unicode Consortium
Monday, April 13, 2026
ICU4X 2.2 released!
The ICU4X Technical Committee is happy to announce
ICU4X
2.2, an update to our modular, portable, and secure i18n library.
ICU4X is Unicode's modern, lightweight, portable, and secure i18n library. Built from the ground up, its binary size and memory usage footprint is 50-90% smaller than ICU4C. It is memory-safe, written in Rust with interfaces into C++, JavaScript, Dart, TypeScript, Kotlin — with other languages in the timeline. Mozilla Firefox, Google Chrome, Google Pixel Watch, core Android, numerous Flutter apps, and more clients are already using ICU4X.
Important changes in ICU4X 2.2 include:
1. Latest i18n data:
This release includes an update to
CLDR 48.2
and support for TZDB 2026a.
2. New and improved
icu_calendar
This release contains new APIs in
icu_calendar
, as well as some behavior changes in
icu_calendar
; see the migration notes
on GitHub
a.
Datetime arithmetic:
It is now possible to add and subtract dates.
b.
More flexible date construction:
Build dates from all kinds of constituent data: extended years, era years, ordinal months, month codes, etc., with support for different kinds of overflow handling.
c. Typed months:
The new
Month
type replaces month codes in a type safe way.
d. Experimental third-party crate integration:
We now support converting and formatting types from the
jiff
chrono
, and
time
crates. See
icu_datetime::input::third_party
. We’re not yet sure if these integrations should live in ICU4X, in the third party crates, or some adapter crate. We
welcome your feedback
e. Changes to Japanese and Hijri calendars:
We no longer support pre-Meiji eras because CLDR removed them, and we now always use Umm al-Qura data for simulated Hijri. See the migration notes on GitHub for more details.
3. Experimental Kotlin Bindings:
We now have Kotlin bindings for ICU4X (found under
ffi/mvn
), with the same set of supported APIs as our other cross-language bindings.
4. Experimental features:
a. Display names:
Adds new internal data layout exposed via RegionDisplayName and ScriptDisplayName APIs. The old data layout, optimized for loading multiple names at once, is moved into the multi module. Please share feedback on our
tracking issue
b.
Compact decimal formatter:
Please
share feedback
in preparation for stabilization in a future release.
c. ML segmentation:
Initial code for RAdaBoost word segmenter for Chinese and CNN word segmenter for Thai.
5. Better hour cycles:
Adds support for Clock12 and Clock24 in datetime formatting.
See the GitHub release for more details
Check out our
quickstart tutorial
interactive demo
, or
C++
TypeScript
, and
Dart
documentation.
As before, the Rust crate is available at
crates.io
, with documentation at
docs.rs
Please post any questions via
GitHub Discussions
----------------------------------------------
Adopt a Character and Support Unicode’s Mission
Looking to give that special someone a special something?
Or maybe something to treat yourself?
🕉️💗🏎️🐨🔥🚀爱₿♜🍀
Adopt a character or emoji to give it the attention it deserves, while also supporting Unicode’s mission to ensure everyone can communicate in their own languages across all devices.
Each adoption includes a digital badge and certificate that you can proudly display!
Have fun and support a good cause
You can also
donate funds
or
gift stock
Posted by
Unicode, Inc.
at
8:02 AM
BlogThis!
Share to X
Share to Facebook
Share to Pinterest
Tuesday, March 31, 2026
Unicode ICU 78.3 and CLDR 48.2 released
Unicode® CLDR
is the most widely used provider of locale data. It provides the essential building blocks that allow software to display dates, times, and currencies correctly in every language and region.
Unicode® ICU
provides widely used C/C++/Java internationalization (i18n) libraries and APIs.
We have just published new maintenance releases of ICU and CLDR, with some small but significant changes. To find out more and to download these releases, go to:
ICU 78.3 Release Note
CLDR 48.2 Release Note
CLDR and ICU have each published a maintenance release in March instead of a major release. The next major releases, CLDR 49 and ICU 79, are planned for October and will include the data from the next CLDR general submission period, planned to start in early Q2 2026, as well as Unicode 18.
The following issues are fixed in the
CLDR 48.2
and
ICU 78.3
maintenance releases:
Several important locale data bug fixes including:
Group separator for number formatting was updated to
in fr_CH for consistency with other Swiss locales.
Some fixes to date and time formats including:
Hv
available formats were updated to match behavior in CLDR 47. The previous change caused web compatibility issues related to current JS capabilities.
Fixes for Emoji annotations issues, such as collisions between emoji short names.
Updated abbreviated and narrow AM/PM for
ko
and
ps
for consistency with how the wide forms are localized.
Full list of changes are available in
Δ48.2
ICU 78.3 includes the CLDR 48.2 changes
ICU also fixes a C++ code point iterator bug
Updates for timezone data 2026a
----------------------------------------------
Adopt a Character and Support Unicode’s Mission
Looking to give that special someone a special something?
Or maybe something to treat yourself?
🕉️💗🏎️🐨🔥🚀爱₿♜🍀
Adopt a character or emoji to give it the attention it deserves, while also supporting Unicode’s mission to ensure everyone can communicate in their own languages across all devices.
Each adoption includes a digital badge and certificate that you can proudly display!
Have fun and support a good cause
Posted by
Unicode, Inc.
at
4:02 PM
BlogThis!
Share to X
Share to Facebook
Share to Pinterest
Labels:
CLDR
CLDR 48
ICU
ICU 78
Tuesday, March 3, 2026
UTS #18: More Unicode Properties in Regular Expressions
Regular Expressions, or “Regex”, are the invisible workhorses of the digital world. Regex allows apps and computer systems to find, validate, and change text based on patterns rather than specific words. Unicode properties play a vital role in this. Rather than an application using a fixed list of characters like a-z, A-Z — and failing badly for all but English — Unicode properties take on the burden of supplying meaningful sets of characters, like
letters
Greek characters
, or
Emoji
. Properties can be combined, such as
Greek letters
with an expression like [\p{script=greek}&\p{letter}].
This specification has an update for now covering over 100 different properties. The following are the most important changes, with others found in the modification section.
Section 2.7 Full Properties
lists the full set of properties recommended for support. This version adds: IDS_Unary_Operator, NFKC_Simple_Casefold, ID_Compat_Math_Start, ID_Compat_Math_Continue, Indic_Conjunct_Break, and RGI_Emoji_Qualification
Special rules called “matching rules” are used when looking up properties and their values by name. This version recommends the matching rules from Section 5.9 Matching Rules of UAX #44.
By expanding and refining property support in UTS #18, this update strengthens the foundation for global text processing.
----------------------------------------------
Adopt a Character and Support Unicode’s Mission
Looking to give that special someone a special something?
Or maybe something to treat yourself?
🕉️💗🏎️🐨🔥🚀爱₿♜🍀
Adopt a character or emoji to give it the attention it deserves, while also supporting Unicode’s mission to ensure everyone can communicate in their own languages across all devices.
Each adoption includes a digital badge and certificate that you can proudly display!
Have fun and support a good cause
You can also
donate funds
or
gift stock
Posted by
Unicode, Inc.
at
8:56 AM
BlogThis!
Share to X
Share to Facebook
Share to Pinterest
Thursday, February 26, 2026
From Central Bank to Code Point: A Roadmap for Currency Symbol Implementation
n the past year, several new currency symbols have been proposed for encoding in the Unicode Standard:
February 2025: The Saudi Central Bank
announced
the creation of a new symbol for the Saudi riyal.
March 2025: The Central Bank of the U.A.E. announced creation of a new symbol for the UAE Dirham (cf.
Dirham Currency Symbol Guideline
).
May 2025: A
proposal
was submitted to encode the symbol for the Maldivian Rufiyaa. (The symbol was created by the Maldives Monetary Authority in 2022.)
November 2025: The Central Bank of Oman
announced
the creation of a new symbol for the Omani Rial.
The Saudi riyal sign was proposed for encoding just barely in time for it to be included in version 17.0 of the Unicode Standard, released in September 2025. Proposals for the other currency symbols were submitted too late for version 17.0, so the symbols will be encoded in version 18.0, which will be released in September 2026.
Recent currency symbol trend
Distinct currency symbols are not essential for local or international financial transactions, and most currencies are denoted with their written name or an abbreviation; e.g. “kr” for krone. However, in recent years, since the creation of the euro currency and its distinct symbol, several monetary authorities have created distinct symbols to denote their currency. A currency symbol could potentially be created only for private use of the monetary authoring — printing on bills or embossing on coins. Usually, however, currency symbols are intended for public use: to appear on shop signs, online retail sites, or anywhere that currency amounts are presented.
Such public usage leads to a need for the symbol to be encoded in the Unicode Standard and supported in commercial software and services. Standardization of a new character and subsequent support by vendors takes time: typically, at least one year, and often longer. All too often, however, monetary authorities announce creation of a new currency symbol anticipating immediate public adoption, then later discover there will be an unavoidable delay before the new symbol is widely supported in products and services.
For a contrast with another recent currency development, Bulgaria transitioned from their local
lev
currency to the euro in January 2026, but the transition was formally decided and announced in July 2025, several months before the change went into effect. This allowed several months for vendors to prepare for the change.
Implementing support for the new currency symbols
Vendor support for a new currency symbol can involve many different things, such as the following:
Updates to fonts
Updates to software keyboard layouts or new designs for physical keyboards
Updating locale data and programming interfaces for formatting currency values
Updating software used for generation of financial statements and reports
Updates to applications, online services or devices for commercial transactions
However, all of these require development time, and development can only begin after the new symbol is encoded in the Unicode Standard. People wishing to start using a new currency symbol in applications and services should anticipate that, from the time the symbol is proposed for encoding, it could take many months or even years before vendors have distributed product updates.
Because there is unavoidable delay from when a new currency symbol is proposed to when it can be supported by vendors,
monetary authorities are strongly encouraged to engage with the Unicode Consortium at least one year in advance
of when a new currency symbol is expected to go into public usage.
Note regarding support on devices
For many devices, including some mobile phones, many vendors do not routinely provide updates, or discontinue providing updates on older devices. For this reason, users should not be surprised if a new currency symbol is not supported natively on a device years after the symbol was introduced. Applications or online services accessed on those devices can have a different update policy however, so experience using such devices could reflect partial support.
Recommendations for implementation of Unicode 18.0 currency symbols
The following three new currency symbols have been approved for encoding in Unicode version 18.0, which will be published in September 2026:
U+20C2 RUFIYAA SIGN
U+20C3 UAE DIRHAM SIGN
U+20C4 OMANI RIAL SIGN
Complete details for these characters are included in the
Unicode 18.0 Alpha preview release.
The technical details — character names, code points, property data — are unlikely to change before Unicode 18.0 is released, but these details are not completely stable until the Unicode Technical Committee has made the final technical decisions for Unicode 18.0. For this reason, vendors can choose to start working on implementations once the Alpha preview is available, but vendors should not distribute product updates until after Unicode version 18.0 is released in September 2026.
Extending support with CLDR
Many implementations use Unicode CLDR data for currency formatting, so incorporating the new symbols is an important step for widespread support. A CLDR release will follow not long after release of Unicode version 18.0, and will contain the new currency symbols for applicable currencies and locales.
However, the symbols will initially be listed as “alternative” symbols for the respective currencies. The reason for a symbol being an alternative, rather than the default, is to avoid the symbol being displayed in contexts in which available fonts might not yet support the new symbol, causing users to see a missing glyph for their currency; e.g.,
instead of
Later, when there is confidence that the symbols are more widely supported in platforms and fonts, a future CLDR version can update details to list the new currency symbol as the default, rather than as an alternative.
Working together to support local monetary authorities
When monetary authorities introduce a new symbol for their currency, it marks a significant milestone for financial and commercial activity in their domain. The Unicode Consortium is honored to work with monetary authorities, and would like to help make the launch of a new symbol as smooth as possible. With that in mind, we invite monetary authorities planning creation of a new currency symbol to engage with us well in advance of a planned launch.
----------------------------------------------
Adopt a Character and Support Unicode’s Mission
Looking to give that special someone a special something?
Or maybe something to treat yourself?
🕉️💗🏎️🐨🔥🚀爱₿♜🍀
Adopt a character or emoji to give it the attention it deserves, while also supporting Unicode’s mission to ensure everyone can communicate in their own languages across all devices.
Each adoption includes a digital badge and certificate that you can proudly display!
Have fun and support a good cause
You can also
donate funds
or
gift stock
Posted by
Unicode, Inc.
at
10:13 AM
BlogThis!
Share to X
Share to Facebook
Share to Pinterest
Tuesday, February 24, 2026
UTS #58: Making URLs Readable for Humans: From %E0%A4%AE… to महात्मा
People around the world need to use their writing systems in URLs. This is important: in writing their native languages, the majority of humanity uses characters outside of A-Z, and they expect those characters to also work seamlessly.
Browsers and other programs  generally handle Unicode in domain names well. But
not
all browsers and other programs do a good job with domain names, and many make the
rest
of the URL unreadable.  For example, consider the common practice of providing user handles such as the following two:
x.com/rihanna
www.youtube.com/@핑크퐁
The first of these works well in practice — because it is all ASCII. Copying from the address bar and pasting into text provides a readable result. However in the second example, in many browsers and other programs, copying the address bar gives an unreadable string:
www.youtube.com/@핑크
youtube.com/@%ED%95%91%ED%81%AC%ED%90%81
The names also expand in size and turn into very long, unreadable strings, such as:
hi.wikipedia.org/wiki/महात्मा_गांधी
hi.wikipedia.org/wiki/%E0%A4%AE%E0%A4%B9%E0%A4%BE%E0%A4%A4%E0%A5%8D%E0%A4%AE%E0%A4%BE_%E0%A4%97%E0%A4%BE%E0%A4%82%E0%A4%A7%E0%A5%80
The other side of the coin is making sure that when programs add links to URLs in a predictable way, linkifying the entire URL, and without extending the link to include sentence punctuation. For example, many programs don’t add links properly to:
… see
A commonly used email program, for example, stops midway through:
… see
δεζ?θικ#λμν.
Others may include the sentence period, question mark, surrounding parenthesis, etc.:
… see
Users often insert spaces to prevent this. It should be automatic:
… see
The new
UTS #58:
Unicode Link Detection and Formatting: URLs and Email Addresses
specifies how to format and linkify URLs and email addresses in readable, predictable, user-friendly ways. The data files cover all of the 159,000+ characters in Unicode.
We encourage implementers to adopt this specification for a consistent experience for users worldwide.
----------------------------------------------
Adopt a Character and Support Unicode’s Mission
Looking to give that special someone a special something?
Or maybe something to treat yourself?
🕉️💗🏎️🐨🔥🚀爱₿♜🍀
Adopt a character or emoji to give it the attention it deserves, while also supporting Unicode’s mission to ensure everyone can communicate in their own languages across all devices.
Each adoption includes a digital badge and certificate that you can proudly display!
Have fun and support a good cause
You can also
donate funds
or
gift stock
Posted by
Unicode, Inc.
at
5:26 PM
BlogThis!
Share to X
Share to Facebook
Share to Pinterest
Tuesday, February 10, 2026
Unicode 18.0 Alpha review
Unicode 18.0 Alpha Review Opens for Feedback
By: Peter Constable, Chair of the Unicode Technical Committee
The repertoire for Unicode Version 18.0 is now open for early review and comment. During alpha review, the repertoire is reasonably mature and stable but is not yet completely locked down. Discussion regarding whether certain characters should be removed from the repertoire for publication is welcome. Character names and code point assignments are reasonably firm, but suggestions for improvement may still be considered.
For the alpha review, preliminary data files are also available, with data covering existing and new character repertoire. In addition, a draft for the core specification is available, with new block descriptions for some of the newly-added blocks and scripts.
The primary focus for the alpha review should be on the new character repertoire. This early review is provided so that reviewers may consider the repertoire and data file issues prior to the start of beta review (currently scheduled to start in May 2026). Once beta review begins, the repertoire, code points, and character names will all be locked down, and no longer be subject to changes.
Notable changes
The planned repertoire for Unicode 18.0 adds 13,048 new characters, which would bring the total number of characters to 172,849 characters.
The additions include four new scripts:
Small Seal (“Seal”): This comprises the largest portion of the new characters, with 11,328 ideographs. Seal is an important precursor to modern Han ideographs (aka, “CJK”), and has important cultural significance in China and for Chinese speakers throughout the world.
Chisoi: A modern script used in eastern India.
Jurchen: A historic ideographic script that was used in northeastern China during the Jin and Ming dynasties.
Proto-cuneiform—in this version, just numeric signs (other characters have been proposed for a future version).
Other additions include nine new emoji characters, 72 historical mathematical symbols, 323 Cuneiform numeric signs, and three new currency symbols for modern currencies:
Maldivian Rufiyaa
Omani Rial
UAE Dirham
Feedback for the alpha review should be reported under
PRI #536
using the
Unicode contact form
by March 31, 2026.
----------------------------------------------
Adopt a Character and Support Unicode’s Mission
Looking to give that special someone a special something?
Or maybe something to treat yourself?
🕉️💗🏎️🐨🔥🚀爱₿♜🍀
Adopt a character or emoji to give it the attention it deserves, while also supporting Unicode’s mission to ensure everyone can communicate in their own languages across all devices.
Each adoption includes a digital badge and certificate that you can proudly display!
Have fun and support a good cause
You can also
donate funds
or
gift stock
Posted by
Unicode, Inc.
at
12:23 PM
BlogThis!
Share to X
Share to Facebook
Share to Pinterest
Older Posts
Subscribe to:
Comments (Atom)
Links of Interest
What is Unicode?
The Unicode Consortium
Archived Announcements
Blog Archive
2026
(8)
April
(1)
ICU4X 2.2 released!
March
(2)
February
(4)
January
(1)
2025
(29)
December
(2)
November
(1)
October
(4)
September
(2)
July
(2)
June
(1)
May
(6)
April
(1)
March
(4)
February
(4)
January
(2)
2024
(38)
December
(2)
November
(3)
October
(4)
September
(6)
August
(1)
July
(2)
June
(2)
May
(5)
April
(3)
March
(6)
February
(2)
January
(2)
2023
(33)
November
(3)
October
(6)
September
(5)
August
(4)
June
(2)
May
(3)
April
(3)
March
(2)
February
(3)
January
(2)
2022
(27)
December
(1)
November
(2)
October
(4)
September
(4)
August
(1)
June
(2)
May
(2)
April
(3)
March
(4)
February
(3)
January
(1)
2021
(28)
December
(1)
November
(2)
October
(3)
September
(3)
August
(1)
July
(2)
June
(1)
May
(2)
April
(4)
March
(4)
February
(3)
January
(2)
2020
(26)
December
(1)
October
(4)
September
(3)
August
(1)
June
(4)
April
(4)
March
(3)
February
(1)
January
(5)
2019
(28)
November
(3)
October
(5)
September
(2)
August
(1)
July
(2)
June
(3)
May
(3)
April
(1)
March
(5)
February
(2)
January
(1)
2018
(36)
December
(2)
November
(1)
October
(6)
September
(2)
August
(2)
July
(3)
June
(4)
May
(1)
April
(4)
March
(4)
February
(5)
January
(2)
2017
(46)
December
(4)
November
(2)
October
(2)
September
(2)
August
(7)
July
(7)
June
(6)
May
(2)
April
(4)
March
(5)
February
(4)
January
(1)
2016
(34)
December
(3)
November
(2)
October
(2)
September
(3)
August
(2)
July
(3)
June
(4)
May
(3)
April
(1)
March
(3)
February
(2)
January
(6)
2015
(35)
December
(2)
November
(6)
October
(4)
September
(4)
August
(3)
July
(1)
June
(4)
May
(1)
April
(1)
March
(3)
February
(4)
January
(2)
2014
(32)
December
(2)
November
(4)
October
(1)
September
(6)
August
(3)
July
(1)
June
(3)
May
(4)
March
(2)
February
(2)
January
(4)
2013
(31)
December
(3)
November
(3)
October
(2)
September
(4)
June
(1)
May
(2)
April
(5)
March
(5)
February
(4)
January
(2)
2012
(40)
December
(4)
November
(1)
October
(2)
September
(2)
July
(3)
June
(9)
May
(3)
April
(2)
March
(8)
February
(4)
January
(2)
2011
(47)
December
(2)
October
(3)
September
(6)
August
(6)
July
(10)
June
(3)
May
(3)
April
(3)
March
(3)
February
(5)
January
(3)
2010
(31)
December
(3)
November
(2)
October
(3)
August
(5)
July
(5)
June
(3)
April
(5)
March
(2)
February
(2)
January
(1)
2009
(24)
December
(1)
November
(2)
October
(3)
September
(4)
August
(2)
July
(4)
June
(3)
May
(5)
Labels
CLDR
(78)
emoji
(75)
Unicode
(42)
ICU
(36)
AAC
(18)
beta
(17)
alpha
(13)
IUC
(12)
UTR #51
(11)
adopt-a-character
(11)
9.0
(10)
POD
(10)
conference
(10)
LDML
(9)
The Unicode Standard
(9)
UTS #51
(9)
Gold Sponsor
(8)
ICU4X
(8)
bidi
(8)
paperback
(8)
Arabic
(7)
IVD
(7)
UTC
(7)
UTS #18
(7)
UTS #46
(7)
Unicode 16.0
(7)
cover art
(7)
Collation
(6)
Survey Tool
(6)
UTS #10
(6)
UTS #39
(6)
Unicode 14
(6)
board of directors
(6)
cldr 43
(6)
locales
(6)
10646
(5)
7.0
(5)
8.0
(5)
SEI
(5)
emoji 12.0
(5)
membership
(5)
regular expression
(5)
security
(5)
unicode 15.1
(5)
10.0
(4)
CJK
(4)
CLDR 26
(4)
CLDR 36
(4)
CLDR 37
(4)
CLDR 39
(4)
CLDR 44
(4)
IDNA
(4)
Mayan
(4)
Rust
(4)
UAX #9
(4)
UTR #50
(4)
UTW
(4)
Unicode 12
(4)
Unicode 13.0
(4)
cldr 38
(4)
cldr 40
(4)
cldr 41
(4)
cldr 42
(4)
emoji 15.0
(4)
regex
(4)
repertoire
(4)
vertical text
(4)
11.0
(3)
12.0
(3)
Bob Jung
(3)
CLDR 35
(3)
CLDR 45
(3)
CLDR 46
(3)
FFI
(3)
Greg Welch
(3)
I18n
(3)
Jennifer Daniel
(3)
Mark Davis
(3)
UAX #29
(3)
UCA
(3)
UTS #37
(3)
Unicode 11
(3)
Unicode 12.1
(3)
Unicode 13
(3)
adoption
(3)
board
(3)
candidates
(3)
cldr 32
(3)
cldr 33
(3)
cldr 34
(3)
core specification
(3)
diversity
(3)
emoji 11.0
(3)
emoji 5.0
(3)
flags
(3)
keynote
(3)
officers
(3)
properties
(3)
reiwa
(3)
schedule
(3)
spoofing
(3)
tutorial
(3)
webinar
(3)
13.0
(2)
14.0
(2)
Addison Phillips
(2)
Adobe-Japan1
(2)
Alolita Sharma
(2)
Anshuman Pandey
(2)
BCP47
(2)
Berkeley
(2)
Beta Review
(2)
CLDR 24
(2)
CLDR 30
(2)
Cherokee
(2)
DDL
(2)
ESC
(2)
Egyptian hieroglyphs
(2)
Elymaic
(2)
Emoji2019
(2)
Extension G
(2)
Georgian
(2)
Google
(2)
Hanifi Rohingya
(2)
ICU 62
(2)
ICU 72
(2)
ICU 73
(2)
IUC 37
(2)
IUC 38
(2)
IUC 41
(2)
IUC 42
(2)
IUC 43
(2)
IUC 45
(2)
Japanese era
(2)
Kristi Lee
(2)
MSARG
(2)
Message Format Working Group
(2)
Microsoft
(2)
Moji Jōhō Kiban
(2)
Moji_Joho
(2)
Nandinagari
(2)
PDAM
(2)
Peter Constable
(2)
RGI
(2)
Roozbeh Pournader
(2)
Salesforce
(2)
Sunuwar
(2)
Teresa Marshall
(2)
Toral Cowieson
(2)
UAX
(2)
UAX #31
(2)
UAX #38
(2)
UAX #44
(2)
UTR #36
(2)
UTR #53
(2)
UTW2024
(2)
Unicode 15
(2)
Unicode Technology Workshop
(2)
Unihan
(2)
Vint Cerf
(2)
World Emoji Day
(2)
award
(2)
bidirectional
(2)
bulldog
(2)
calendar
(2)
candidate
(2)
design
(2)
egyptian
(2)
emoji 13.0
(2)
emoji 13.1
(2)
event
(2)
frequency
(2)
grant
(2)
holiday
(2)
ideographic
(2)
internationalization
(2)
keyboard
(2)
message format 2
(2)
person names
(2)
script
(2)
script_extensions
(2)
scripts
(2)
source code
(2)
standards
(2)
unicode 14.0
(2)
15.0
(1)
2021
(1)
6.3
(1)
AMTRA
(1)
Adlam
(1)
Adobe
(1)
Andy Heninger
(1)
Anne Gundelfinger
(1)
Apple
(1)
Arika Okrent
(1)
Babel
(1)
Bhojpuri
(1)
Bravanese
(1)
Brent Getlin
(1)
CJK Radical
(1)
CLDR 23
(1)
CLDR 25
(1)
CLDR 27
(1)
CLDR 28
(1)
CLDR 29
(1)
CLDR 33.1
(1)
CLDR 36.1
(1)
CLDR 47
(1)
CLDR 48
(1)
CLDR 50
(1)
CLDR-TC
(1)
Caddo
(1)
CanadaDay
(1)
Carlos Pallan Gayol
(1)
Carrier
(1)
Cathy Wissink
(1)
Chorasmian
(1)
Chuvash
(1)
DAM 1
(1)
DNS
(1)
Dachuan Zhang
(1)
David Singer
(1)
Dhives-Akuru
(1)
Dives Akuru
(1)
Dogri
(1)
Du Lilyu
(1)
Ebrima
(1)
Elango Cheran
(1)
Emoji 14.0
(1)
Emoji One
(1)
Emoji12
(1)
Eric Muller
(1)
Extension I
(1)
FAQ
(1)
(1)
French
(1)
Fulani
(1)
Gabee Ayres
(1)
Gabrielle Vail
(1)
Garay
(1)
Georgian Mtavruli
(1)
GivingTuesday
(1)
Gonggong
(1)
Gretchen McCulloch
(1)
Gurung Khema
(1)
Hanyo Denshi
(1)
Harald Alvestrand
(1)
Haryanvi
(1)
Haumea
(1)
Hindi
(1)
Hinglish
(1)
Huijun Shan
(1)
IAU
(1)
IBM
(1)
ICU 58
(1)
ICU 59
(1)
ICU 63
(1)
ICU 64
(1)
ICU 65
(1)
ICU 66
(1)
ICU 67
(1)
ICU 68
(1)
ICU 69
(1)
ICU 70
(1)
ICU 71
(1)
ICU 74
(1)
ICU 75
(1)
ICU 76
(1)
ICU 78
(1)
ICU4X 1.3
(1)
IDC
(1)
IDS
(1)
IRG
(1)
IUC 39
(1)
IUC 40
(1)
IUC IUC 39
(1)
Igbo
(1)
Indigenous
(1)
Iris Orriss
(1)
JSON
(1)
Japan
(1)
Jennifer 8 Lee
(1)
Jeremy Burge
(1)
John H. Jenkins
(1)
KRName
(1)
Kaktovik Numerals
(1)
Kangxi
(1)
Kashmiri
(1)
Kawi
(1)
Khitan
(1)
Khwarezmian
(1)
Kirat Rai
(1)
Kulpreet Chilana
(1)
LDML Keyboard
(1)
LanguagePreservation
(1)
Lari
(1)
Linkification
(1)
Luce Foundation
(1)
Macao
(1)
Maithili
(1)
Makemake
(1)
Malayalam
(1)
Manat
(1)
Manipuri
(1)
Mark Jamra
(1)
Mazahua
(1)
Medefaidrin
(1)
Michele Coady
(1)
Monica Tang
(1)
NEH
(1)
Nag Mundari
(1)
Naija
(1)
National Endowment for the Humanities
(1)
Nattilik
(1)
Ned Holbrook
(1)
Nepal Bhasa
(1)
Neptune
(1)
Netflix
(1)
New Tai Lue
(1)
Nigerian Pidgin
(1)
Nigerian-Pidgin
(1)
Norbert Lindenberg
(1)
Norwegian
(1)
Nyiakeng Puachue Hmong
(1)
Ojibway
(1)
Ol Onal
(1)
Orcus
(1)
Osage
(1)
PDAM 2.2
(1)
PRI #359
(1)
PRI #365
(1)
PRI #366
(1)
PRI #408
(1)
PRI #418
(1)
PRI #435
(1)
Pahlavi
(1)
Peter Edberg
(1)
Phoreus
(1)
Pluto
(1)
Public Review Issues
(1)
QID
(1)
Quaoar
(1)
RBNF
(1)
Rajasthani
(1)
Rathna Ramanathan
(1)
Rohingya
(1)
Ruble
(1)
SC2
(1)
SCWG
(1)
Saagar Setu
(1)
Salvatore Giammarresi
(1)
Sanskrit
(1)
Santali
(1)
Sayisi
(1)
SignWriting
(1)
Sindhi
(1)
Sinhala
(1)
Siyaq
(1)
Sogdian
(1)
Stanford
(1)
Stanford SILICON
(1)
Support Unicode
(1)
Swiftkey
(1)
Syloti Nagri
(1)
TNO
(1)
Tableaux des caractères
(1)
Tangsa
(1)
Tayfun Karadeniz
(1)
Thomas Mullaney
(1)
Todhri
(1)
Tom Mullaney
(1)
Toto
(1)
Tulu-Tigalari
(1)
Typotheque
(1)
UAX #14
(1)
UAX #15
(1)
UAX #45
(1)
UCA UCD
(1)
UCD
(1)
UTC #175
(1)
UTC #177
(1)
UTC #179
(1)
UTC #180
(1)
UTC #181
(1)
UTC #182
(1)
UTR #23
(1)
UTS #35
(1)
UTS #52
(1)
UTS #55
(1)
Uighur
(1)
Unicode 15.0
(1)
Unicode 16
(1)
Unicode 17.0
(1)
Unicode Fellows
(1)
Unicode Technical Committee
(1)
UnicodeEmoji
(1)
UnicodeEmojiMirror
(1)
Vithkuqi
(1)
Wancho
(1)
Warsh
(1)
Webdings
(1)
Wingdings
(1)
Xhosa
(1)
Yezidi
(1)
(1)
ZWJ
(1)
Zawgyi
(1)
Znamenny
(1)
alpha review
(1)
amendment
(1)
annotations
(1)
art
(1)
astronomy
(1)
beta 6.3 bidi
(1)
bloomberg
(1)
cambridge
(1)
character property model
(1)
cldr 31
(1)
cldr 35.1
(1)
community engagement
(1)
compatibility
(1)
conjoining form
(1)
corrigendum
(1)
currency
(1)
customization
(1)
directionality
(1)
document register
(1)
domain names
(1)
donations
(1)
draft
(1)
dwarf planets
(1)
emoji 12.1
(1)
emoji 16.0
(1)
emoji proposal
(1)
emojixpress
(1)
era name
(1)
executive director
(1)
family
(1)
feedback
(1)
flag
(1)
font
(1)
française
(1)
gender
(1)
general category
(1)
general counsel
(1)
glyphs
(1)
grafematik
(1)
graphemics
(1)
guide
(1)
hashtag
(1)
hentaigana
(1)
hieroglyphs
(1)
highlights
(1)
icu 60
(1)
icu 61
(1)
icu 64.2
(1)
ideographic description characters
(1)
interview
(1)
iuc 44
(1)
keyboards
(1)
language
(1)
locale
(1)
maya
(1)
mongolian
(1)
myanmar
(1)
noncharacters
(1)
oman
(1)
participation
(1)
person-names
(1)
phone
(1)
planning
(1)
playlist
(1)
policies
(1)
publication
(1)
publishing
(1)
quick start
(1)
reference code
(1)
release
(1)
resources
(1)
segmentation
(1)
shopify
(1)
smiley face
(1)
soyombo
(1)
space
(1)
speaker
(1)
sponsor
(1)
stability policies
(1)
submission
(1)
syllabics
(1)
symbol
(1)
technical preview
(1)
text segmentation
(1)
turkey
(1)
typography
(1)
unicodeaac
(1)
valentines day
(1)
variation
(1)
workshop
(1)
文字情報盤
(1)
Followers
Subscribe to this blog
Posts
Atom
Posts