Subscript unicode values not set

[mwyschan]

Describe the bug

Specifically referring to subscript glyphs with unicode 2080-2089, which are named zero.subs to nine.subs, but have no unicode value.

This is also inconsistent with superscript glyphs with unicode 2070-2079, which are named uni2070 to uni2079, but have the correct unicode value set.

Steps to reproduce the bug

Inspect subscript glyphs U+2080 to U+2089

Expected Behavior

Subscript glyphs U+2080 to U+2089 should have correct unicode values set.

Related code

No response

Screenshots

From fontdrop.info:

System setup

• Public Sans v2.001

Additional context

No response

Code of Conduct

• I agree to follow this project's Code of Conduct.
• I checked the current issues for duplicate bug reports.

[ewagoner]

This appears to be the case for all the digit glyphs, not just subscripts. For example, only three.glyph has a unicode parameter: <unicode hex="0033"/> and if you inspect any of the variations on three they all show a unicode value of 0033.

As a result, the browser falls back to other installed fonts to display those numeric glyphs and if there are no other fonts, the .notdef slashed rectangle is displayed. Unfortunately, that's the situation I'm in.