Description of problem:
When a set of hinting instructions is inserted into a glyph/char, will be cleared after save.
Version-Release number of selected component (if applicable):
Sometimes. About 50% chance.
Steps to Reproduce:
1. Start fontforge with a font file. (I used .sfd)
2. Copy a set of hinting instructions from other glyph. (Hints > Edit instructions.)
3. Paste into a glyph. (Hints > Edit instructions)
4. Save the font file. (File > Save)
5. Check the little box above the glyph on main window.
The box should be hollow (grey color as background) which the glyph is correct.
The box is in blue background which the glyph has no hinting instructions.
This bug is discovered during process of bug #460090.
Has it been reported upstream?
Additionally, can you see if the latest fontforge in rawhide shows this bug?
It was just updated yesterday to a new version.
(In reply to comment #1)
> Has it been reported upstream?
(In reply to comment #2)
> Additionally, can you see if the latest fontforge in rawhide shows this bug?
> It was just updated yesterday to a new version.
I am resolving the original liberation-fonts bug on F9. This is what I have discovered as side-bug.
According to George Williams (fontforge contributor) via fontforge mailing lists, "This build is out of date. A bug similar to this has been fixed. Please
try the current build."
Please kindly triage and close if not found on new version.
Well, we dislike updating fontforge in stable releases, as it means we need to rebuild a bunch of fonts that use it as a BuildRequires, but we can discuss it if it's needed of course.
I don't see this on the new rawhide fontforge version...
This bug is not a critical one: you just need another 'save' and fontforge will listen to you. If you think it is not appropriate to update in stable releases, I would have no objection on that.
George Williams is mentioning about latest upstream build.
Yeah, we might update stable releases, but will have to consider...
In any case I think this is fixed with the version in rawhide, so I will go ahead and close it. If you find any further issue with it, feel free to re-open this or file a new bug.