Bug 1925496 Comment 37 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
(In reply to Jonathan Kew [:jfkthame] from comment #36)
> both U+1CBB and U+1CBC are unassigned Unicode codepoints, so I would expect them to display as missing-glyph hexboxes

Unfortunately, on win11 23h2 these are also shown as spaces, like 133FC
Revision 1 by
on 
(In reply to Jonathan Kew [:jfkthame] from comment #36)
> both U+1CBB and U+1CBC are unassigned Unicode codepoints, so I would expect them to display as missing-glyph hexboxes

Unfortunately, on win11 23h2 at least, these are also shown as spaces, like 133FC
Revision 2 by
on 
(In reply to Jonathan Kew [:jfkthame] from comment #36)
> both U+1CBB and U+1CBC are unassigned Unicode codepoints, so I would expect them to display as missing-glyph hexboxes

Unfortunately, on win11 23h2 at least, these are also shown as spaces, like 133FC
In any case I don't see a use for these, so encoding them shouldn't be a problem.

Back to Bug 1925496 Comment 37