I have been carefully following this discussion of technical issues, API
conformance, and related issues,.
There has been no significant discussion of the user experience that
depends on the resolution of this problem.
Will non-BMP Unicode code points display correctly in terminal windows
(that use an appropriate font), e.g. mintty?
Non-BMP Unicode code points include emojis, mathematical script glyphs, and
many others.
For me, I care if a small Python script like:
$ cat main.py
print("U+01D49E ‹𝒞› GC=Lu MATHEMATICAL SCRIPT CAPITAL C")
outputs:
U+01D49E ‹𝒞› GC=Lu MATHEMATICAL SCRIPT CAPITAL C
as is currently does in Windows Terminal.
or
$ uname -a
CYGWIN_NT-10.0-26200 mercury 3.6.9-1.x86_64 2026-04-21 15:46 UTC x86_64
Cygwin
$ mintty --version
mintty 3.8.2 (Cygwin-x86_64)
$ date
Jun 2, 2026 11:36:33
$ python3 -V
Python 3.12.12
$ python3 main.py
U+01D49E ‹𝒞› GC=Lu MATHEMATICAL SCRIPT CAPITAL C
correctly displays the Mathematical Script Capital C glyph as seen below
and in the attached screen capture.
[image: image.png]
If the resolution of this problem changes "our" user experience, that will
be another problem.
As an after thought, I may be seeing success due to the byte stream
containing UTF-8 4-byte sequences all the way through Windows 11, without
any conversions to UTF-16 or UTF-32.
I am not so up-to-date with C to rattle off a demo in seconds, as I can in
Python. I would like to see such a demo program.
Just my take,
Doug
--
Doug Henderson, Calgary, Alberta, Canada - from gmail.com
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation: https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
