Download

Quick search

Rate this software

• Currently 0/5 Stars.
• 1
• 2
• 3
• 4
• 5

No. Votes

0

Linux

Windows

Mac

Mobile

Drivers

Scripts - DHTML

Web Developer Blog

Scripts and Applications

FontForge

Details

FontForge is an outline font editor that lets you create your own postscript, truetype, opentype, cid-keyed, multi-master, cff, svg and bitmap (bdf) fonts, or edit existing ones.
Also lets you convert one format to another. FontForge has support for many macintosh font formats.
FontForge's user interface has been localized for: (English), Russian, Japanese, French, Italian, Spanish.
With the appropriate libraries, FontForge can import png, tiff, and gif images to act as character backgrounds for tracing purposes (FontForge can import bmp and xbm formats without external libraries).
With libxml2 FontForge can read SVG fonts. With the freetype library FontForge will do a better job making bitmap characters for you.
None is required for the proper compilation/execution of FontForge, if the libraries are not present they will not be used.
What's New in This Release:
· New Vietnamese translation from Clytie
· New Russian translation from Alexandre Prokoudne.
· New Polish translation from Michal N. .
· FF could crash if a cmap subtable contained invalid encoding points.
· Add various new features/scripts/language tags from OpenType draft 1.5.
· Add two proposed features from the pre-draft of OT 1.6
· Drop Caps
· Character Variants 00-99
· The warnings window didn't resize properly. It didn't let you copy text (ie. a warning) It didn't enough. It should have scrolled with keypad keys (arrows, page up/down, etc). There should be a way to clear the windows so you know that all the warnings are from a given operation. Added a popup menu.
· Fixed a problem in the auto hinter.
· Could not attach lookups to mac feature settings.
· Clean up some display problems in the type3 layers palette and layer info dlg.
· Autoinstructor: turned on strong point interpolation:
· Various important outline points are correctly placed between hints' edges.
· Potential benefits for DStem positioning.
· Drawbacks: 2x slower, code generated is now much bigger.
· The merge (and simplify) command could produce odd results if the points surrounding the merge had no control points.
· Extend find/replace to handle changing angles.
· The Display/Print dlg would crash when the user pressed the reset button if there were at least two pointsizes of the font on display. Perhaps in other cases too.
· Make shift click in the lookup dialog (but not the subtable part) select all lookups between current click and a previously selected point.
· glyph.addPosSub doesn't work for ligatures or multiple substitutions. It treats both as alternate substitutions.
· Michal Now. points out that there are some strings not marked for translation in cvruler.c.
· FontForge never checked that fonts had fewer than 65536 glyphs. I just blythely assumed I wouldn't have to worry. Well someone handed me a font with 65731 glyphs, and FF treated it as having 195 glyphs. Things got nasty after the 196th.
· Fix a crash in autohint.c and an infinite loop in stemdb.c.
· Font Compare would crash if one font had a lookup subtable which was not in the other.
· Improve the algorithm used to detect reference points for stem edges. Enable snapping "corner extrema" to predefined hints.
· Remove the obsolete Private Dict to CVT table command.
· Michal Now. wants short cuts to change grid fit attributes, so a new sub menu with things like increase point size, change AA, etc. (with shortcuts, of course).
· Patch by Michal Nowakowski. In Show Grid fit not setting the mono bit correctly in freetype.
· Bug in pfm file output.
· If we failed to open a plugin library during init, it would call LogError before the display was initialized, leading to a crash.
· Autoinstructor: If a horizontal stem interpolated between blue zones was very close to one of them, it often jumped beyond that zone in small ppems. This was especcially annoying for serif fonts.
· Improvements (I hope) to the ruler tool
1. Make it snap to splines (in addition to points)
2. Have it draw a line from the start point to the mouse
3. If they start on a spline, then include info on the offset in coordinates parallel to the spline and normal to it.
4. Provide a "spline length" if the start and end points are on the same spline (instead of just if they were the end-points of the spline).
· In python scripting contour.reverseDirection only worked on closed contours.
· If you click wildly in the cvt editor it would eventually go into infinite recursion.
· If there were no free anchor class then attempting to add an anchor point would pop up the Mark Classes pane of Font Info (rather than Lookups). This is sufficiently close to Anchor Class as to be very confusing.
· Make label gadgets (and buttons which are also labels) handle multiline text.
· If the user closes the font info dlg when there are mark class dialogs floating around then close them too (there was code which was supposed to do this, but it didn't work).
· Try to make it clear in the Mark Classes pane of the Font Info that mark classes are not anchor classes. Someone got confused...
· Fix some bugs in parsing mark anchors in feature files.
· When adding an hvcurve point into an existing spline it behaved like a curved point and laid parallel to the spline rather than being either horiz or vert.
· FontForge uses floats (which have ~24 bits of precision internally) to represent coordinates. Type2 fonts use a 16.16 fixed notation, which means that we only represent coordinates <256 >
· So instead, when loading and saving a Type2 font use double precision temporaries. This should mean there will be no errors to accumulate. There will be slight errors when converted to SplinePoints, but these errors will not accumulate.
· Check several adjacent splines when detecting active zones for curved segments and thus make the algorithm less dependent from the number of additional points on a contour and their exact positions.
· Fix a number of problems that -pedantic complains about.
· Some mnemonics in the Element menu are used for two items. Clean it up a bit.
· Add a "Find Problems" for non integral coordinates.
· Change the "Ref with bad ttf transformation" so that it checks for integral coordinates too.
· the glyph.validate function in python was marked as taking NOARGS in the method table, but, in fact, does take arguments.
· Oops. Validate used to complain if the StemSnap[HV] array were missing. But that's perfectly ok.
· Be more lenient when closing a path (when reading in a type1/2 font)... we can get rounding errors.
· Add a little LogError to let the user know if there are sfnt tables we ignore.
· Deep in the heart of Find Problems check for bad contour direction, was a bug where it looked at the wrong spline.
· Just as it is possible to have things in 'morx' that are not in 'GSUB', it is possible that a 'GPOS' table contains no kerning information but a 'kern' table does. We used not to read 'kern' if we had 'GPOS', be a little subtler and check for the presence of a 'kern' feature inside 'GPOS' before deciding whether to read the 'kern' table.
· The anchor control dialog didn't work for mark to mark anchors when looking at a base mark.
· When a font contained glyphs with multiple encodings, then ff would produce bdf files with a char count which matched the glyphs, not the number of encoding slots used.
· In a compacted cid font, the status line (containing unicode, unicode block/name, etc) was junk.
· Barry wants to be able to mark that it's ok for a spline to have intermediate extrema.
· The []TeX Table checkbox was always disabled in the save font dlg.
· The DejaVu people want to be able to associate a comment with a cvt entry.
· Find Problems->ATT->Missing glyph name complains about the special string which I used in Apple lookups to represent the "Delete Glyph" action that apple supports and OT does not. Don't complain about this any more.
· Add a problem which will look at the glyphs a lookup is active for, and then checks the script of each glyph against the scripts attached to the features which invoke this lookup. If the script doesn't match anything, then complain.
· If a font contained an empty anchor class (having either no base glyphs or no mark glyphs) then when dumping out the font subsequent anchor classes got the wrong data associated with them.
· Barry wants non-integral hints.
· Barry points out that Scale To Em doesn't scale the guidelines.
· Barry also complains that spiro points are rounded. This is more debatable. The bezier conversion will put bezier points where there were spiros, so if we don't round the spiros we get non-integral points. But if we do round the spiros we mess up the splines. Hmm.
· When complaining about a bad class in a mark (GPOS) sub-table, specify the name of the offending mark if we can.

0 comments

Add to

 Del.icio.us   Digg It   Furl   YahooMyWeb   Blinklist

FontForge Version History

Related Software