Characters are present and encoded, but Font Info: Unicode Ranges and Compact don't know about them, nor does Word

[JSColburn]

• Provide a general summary of the issue in the Title above.
• Before you open an issue, please check if a similar issue already exists or has been closed before.

Important

Mark with [x] to select. Leave as [ ] to unselect.

When reporting a bug/issue:

• Screenshot
  
  
• The FontForge version and the operating system you're using: 20230101 under Windows 10 version 22H2 for x.64
• The behavior you expect to see, and the actual behavior: Characters have been added at their proper Unicode slots, and the font generated (all errors were corrected except some noninteger coordinates that did not respond to Round). Apps cannot find these characters; Word 2019 switched to a different font for them. In FF, Font Info: Unicode Ranges reports zero characters present, even though, when I click the line for that range, Font View comes up with the characters highlighted as shown in the first screenshot. Second screenshot is the Glyph Info for one of them. They did not (at first; see below) show up in Compact either.
• Steps to reproduce the behavior
• (optional) Possible solution/fix/workaround: After closing the .sfd, closing FontForge, and reopening, I found that the new characters now show up in Compact, even though Font Info: Unicode Ranges still reports 0/123 characters, Generated the font, reopened the generated .ttf in FontForge, and from this file Font Info: Unicode Ranges now reports 72/123 characters present. Installed the font and it now works in Word. All's well that ends well, but the original .sfd still says 0/123 characters.

When you open an issue for a change/improvement/feature request:

• A description of the problem you're trying to solve, including why you think this is a problem
• If the feature changes current behavior, reasons why your solution is better
• (optional) Possible solution/fix/workaround

[JSColburn]

After I added 4 more characters to the range, Font Info: Unicode Ranges was still at 72/123 when it should have been 76/123.

In short, adding characters to a range does not update the count in Font Info: Unicode Ranges. Because apps such as Word apparently rely on that count to ascertain whether there are any characters in the range, if you start with an empty range, apps will not know there are any characters, will not attempt to access them, and will substitute from other fonts instead,