Description of problem: There is a problem when changing setting through glyph point settings window. All the changes are not applied. Version-Release number of selected component (if applicable): fontforge-20080429-1 How reproducible: Always Steps to Reproduce: 1. Open Liberation Fonts 1.04 file LiberationSans-Regular.sfd with fontforge. 2. Double click on 'y' (U+0079) glyph to open edit window. 3. Right click filled dots in the centre junction of strokes and select Get Info. 4. On Location tab, change Normal to Interpolated. 5. Click OK button. Actual results: The glyph point is still filled dot which means still Normal. Expected results: The glyph point is changed to hollow dot which means interpolated. Additional info: Liberation Fonts 1.04 is available at: https://fedorahosted.org/liberation-fonts/export/b2fa06aa4d23caecaac324e6e09317a4bbdf82f0/tags/liberation-fonts-1.04/src/LiberationSans-Regular.sfd
Reported bug to upstream mailing lists.
Created attachment 314682 [details] Patch from George Williams George Williams (gww AT silcom DOT com) is one of contributors in fontforge-devel mailing lists.
excellent. :) Whats the impact here? Should we apply this patch now? Or wait for a new upstream release? Thoughts?
Hi Kevin, I have just tested this patch when I patched on bug #458592 and this patch resolves the problem. I support the application of this patch. Unsure if his patch is accepted to be included in next upstream release yet. Cheers, Caio.
http://sourceforge.net/mailarchive/message.php?msg_name=10614175.91219110957804.JavaMail.cchance%40sashimi.bne.redhat.com
Happily, this patch seems to be already applied in the latest upstream version which I have just built in rawhide. ;) Did you need this update in f9 as well? We try and not update fontforge in stable releases because fonts might also then need updating, leading to a lot of churn and problem. ;(
IMHO, since F10 is due very soon, you don't need to update in f9. :)
requested by Jens Petersen (#27995)
Can you confirm that this is now fixed in f10?
This seems already applied upstream, I am gonna go ahead and close this now. If you spot any problems with it, feel free to reopen or file a new bug.