fix: render U+FFFD replacement character instead of ? (#366)

The current behavior of rendering `?` for an unknown Unicode character
can be hard to distinguish from a typo. Use the standard Unicode
"replacement character" instead, that's what it's designed for:

https://en.wikipedia.org/wiki/Specials_(Unicode_block)

I'm making this PR as a draft because I'm not sure I did everything that
was needed to change the character set covered by the fonts. Running
that script is in its own commit. If this is proper, I'll rebase/squash
into one commit and un-draft.

Co-authored-by: Maeve Andrews <maeve@git.mail.maeveandrews.com>

This commit is contained in:

Maeve Andrews

2026-01-19 05:58:43 -06:00

committed by

GitHub

parent 7a792a5384

commit 5fef99c641

37 changed files with 620 additions and 100 deletions

									
										2

lib/Utf8/Utf8.h
									
												View File
												
				@@ -2,4 +2,6 @@

				#include <cstdint>

				#define REPLACEMENT_GLYPH 0xFFFD

				uint32_t utf8NextCodepoint(const unsigned char** string);

fix: render U+FFFD replacement character instead of ? (#366)

2 lib/Utf8/Utf8.h Unescape Escape View File

2

lib/Utf8/Utf8.h

View File