Fontforge glossary8/16/2023 This release contains numerous fixes and feature updates since the last release. made their first contribution in #5106.made their first contribution in #5135.made their first contribution in #4097.made their first contribution in #5074.made their first contribution in #5014.made their first contribution in #5055.made their first contribution in #5025.made their first contribution in #5035.made their first contribution in #5047.made their first contribution in #4971.made their first contribution in #4941.Record unicode cmap encodings when one glyph is in multiple slots by in #4586.Update tranlsations from Crowdin by in #5168.fvmetrics.c: partial revert of 1033bc6 by in #5167.ufo.c: emit guidelines key by in #5166.tottfgpos: Fix needless warning about 16-bit field by in #5136.fontinfo.c: fix crash from uninitialised other_pos by in #5165.Fix painting behaviour of the ruler linger window and layer change dialog by in #5163.Fix broken link on scripting page by in #5135.Upgrade to Unicode 15.0.0 and fix and expand the script lists by in #5110.Fix logic for CharString double-movetos after PR 4685 by in #5120.docs: Python scripting - update rgeFeature with details of boo… by in #5107.RFE: When reference to non-existent glyphs are present in an OpenTy… by in #4097.splinefit.c: Improvements to merge/simplify by in #5095.Include SFDUTF7 functions in libfontforge.so by in #5078.Shell-quote command sent to compressor in BDF by in #5060.splineutil.c: prevent hang on nan input by in #5058.Add a preference for saving editor state by in #5044.Prevents memory underflow in GFileMimeType() in gutils/fsys.c by in #5018.Fix drawing outside of expose calls by in #4949.GroupFindLPos() in fontforgeexe/groupsdlg.c null pointer fix by in #5025.Prevent floating point shenanigans in loop termination (fixes #5012) by in #5013.Fix Ascent & Descent Importing from SVG Font by in #5035.Define PATH_MAX and MAXPATHLEN for GNU/Hurd compatibility by in #5046.Undefine "extended" macro temporarily on GNU Hurd by in #5047.Support setting SplineChar width from importOutlines.Add flags to Python ansform() by in #4980.Expand the lists of languages and scripts by in #4982.FVSplineFontPieceMeal: Check that the clut is present before applying conversion by in #4999.Fix ChangeGlyph calcluations relative to new nonext/prevcp conventions by in #4979.Use 'cmap' for Adobe-Identity-0 CID fonts by in #4993.Better line handling in simplify by in #4981.Change which lookup types are suggested for jamo features by in #4994.Fix rect extraction from graphics stream for type3 fonts by in #4967.Handle non-array cm transforms while reading graphics stream from PDFs by in #4965.Fix normalisation of absolute paths by in #4963.cmake: Install fonttools and pycontrib by in #4941.Fix name extraction for Type3 fonts from pdfs by in #4960.Add resource file and Windows application manifest by in #4950.Support ToUnicode extraction from PDFs for Type3 fonts by in #4961.Fix resolution of program root by in #4956.Better control-drag handling for line-adjacent points by in #4945.gfilechooser.c: fix behaviour when changing file type by in #4939.Don't respond to wheel scrolls for buttons/tabsets by in #4940.Display the block name for reserved code points by in #4934.I only want to confirm the presence of the ligatures, for which a screenshot in a font editor will do. What’s the deal with these ligatures? How is it that the foundry clearly shows the presence of ligatures, but the font files do not have them? Does anyone, by any chance, have the Nexa font files with ligatures? (Of course, I’m not asking for the files themselves to be uploaded, as that’s piracy. This is also demonstrated in this demo picture. The exceptions are the Demo fonts (Light and Bold), which have a different type of fi-ligature altogether, where the hook of the ‘f’ covers up the dot of the ‘i’, as seen in the picture below. It is clear that the two glyphs are unconnected. Attached below is a screenshot from FontForge. I have downloaded the font from multiple sources, and not a single ligature is to be found in even one file or weight. Here, the bar of the ‘f’ is connected to the ‘i’, but the dot of the ‘i’ is not covered by the hook of the ‘f’.īut, out of all the samples of Nexa I have, not one of them has any ligatures, neither at the usual place (U+FB01), nor anywhere else in the file. ![]() On the one hand, the font’s display page clearly shows the presence of the fi-ligature. Nexa is a very mysterious font when it comes to ligatures.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |