Menu
▾
▴
fontforge-announce — Used by me to announce changes to fontforge
You can subscribe to this list here.
| 2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
(1) |
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2007 |
Jan
|
Feb
|
Mar
(3) |
Apr
|
May
(1) |
Jun
|
Jul
(1) |
Aug
|
Sep
(1) |
Oct
(1) |
Nov
|
Dec
|
| 2008 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
|
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2010 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2011 |
Jan
|
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2016 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(6) |
Nov
|
Dec
|
| 2017 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2019 |
Jan
|
Feb
|
Mar
|
Apr
(4) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2020 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
|
From: Frank T. <fra...@gm...> - 2020-11-07 22:57:09
|
[image: org.fontforge.FontForge.png] Hi, all. On Wednesday, November 7th, 2000, George W. Williams V first published a piece of software called PfaEdit that allowed rudimentary editing of PostScript fonts. It lacked the features and polish of such prominent products as Fontographer and Font Studio, but it had one big advantage: it was free. Twenty years later, Fontographer and FontStudio are gone, and the whereabouts of George Williams are unknown, but FontForge has grown into a highly capable and mature product. It supports dozens of file formats and includes such features as spline stroking, overlap removal, and Python scripting. And it is still free software. With over 100,000 users, it is the most widely used typeface design tool in the world. It may seem anti-climactic that today's 20th anniversary release includes no major changes or new features, but it perfectly befits a product that has evolved carefully and slowly over its entire lifecycle with almost no breaking changes. Whether for the special commemorative splash screen or for the countless small improvements and fixes, we hope that you will try it. It is available, as always, on the FontForge website <https://fontforge.org/>. The entire project team thank you for your support. Best wishes, Frank |
|
From: Frank T. <fra...@gm...> - 2020-03-14 05:03:29
|
[image: org.fontforge.FontForge.png] Hi, all. I am happy to announce the March 2020 release of FontForge. Changes include the following. - FontForge now has much improved stroke expansion functionality. The main change is that it actually works most of the time. New features include support for arbitrary convex nibs and the miter-clip and arc join styles from SVG 2. All functionality is accessible from the Python and native APIs. (By Skef Iterum.) - Remove overlap handles certain important edge cases better. (By Skef Iterum and Frank Trampe.) - The Python API now has a function called `genericGlyphChange` that matches the "Change Glyph" command in the GUI. See #4133 for more details. (By Skef Iterum.) - The Python API now has functions for getting Unicode script and for interrogating glyph boundaries. (By Fred Brennan.) - One can now use text flags (rather than just numerical flags) when opening a font file via the Python API. (By Skef Iterum.) - UFO import now outputs the note field properly. (By Skef Iterum.) - SVG import is much more robust. (By Skef Iterum.) - We have dropped most gnulib and autotools logic in favor of CMake, which dramatically simplifies the build system and just as dramatically improves build time. (By Jeremy Tan.) - As part of the switch to CMake, per the deprecation of Python 2, and per the lack of objections to the proposal on the mailing list, we have dropped support for building FontForge with Python 2 support. The non-build-system Python 2 code remains, but it is neither tested nor maintained nor supported and is likely to follow a trajectory of decay and then removal. - Documentation is now rendered in Sphinx, which makes maintenance and improvement easier. (By Jeremy Tan.) - Translations now happen on crowdin, which makes contributions easier. (By Jeremy Tan.) - We got such a contribution for Croatian. (By Milo Ivir.) - Character view point coloring is more consistent, and preview fills support transparency. (By Skef Iterum.) - The user can now move and close tabs in the character view. (By Fred Brennan.) - The metrics view now allows for entry of negative kerning values and runs a bit more smoothly. (By Fred Brennan.) - There is now a warning when a user is about to discard an unsaved script. (By Fred Brennan.) - We fixed bugs all over, as always, with particular attention given to the metrics view, Python, Spiro, and high-resolution displays. Go to the FontForge website <https://fontforge.org/> to get the right package for your system. Best wishes, Frank |
|
From: Frank T. <fra...@gm...> - 2019-04-15 15:23:52
|
Yes. The build process broke in the midst of other changes. They will be ready with the next release. Please try the AppImage if that works. On Mon, Apr 15, 2019 at 10:11 AM Mauro Sacchetto <mau...@gm...> wrote: > .deb packages are not yet ready? > thanx > > ms > > Il 13/04/19 12:45, T J ha scritto: > > Hi all, > > > > FontForge has been updated to the 2019-04-13 release. > > > > This is mostly a bugfix release on top of the 2019-03-17 release. Most > > notably, it resolves a crash on MacOS when browsing directories that > > contain empty files. Plugins support and direct http/ftp integration has > > also been removed. > > > > The source tarball, MacOS, Linux (AppImage) and Windows binaries are all > > available from https://fontforge.github.io. > > > > Thanks, > > > > Jeremy > > > > > > > > _______________________________________________ > > Fontforge-announce mailing list > > Fon...@li... > > https://lists.sourceforge.net/lists/listinfo/fontforge-announce > > > > > _______________________________________________ > Fontforge-announce mailing list > Fon...@li... > https://lists.sourceforge.net/lists/listinfo/fontforge-announce > |
|
From: Frank T. <fra...@gm...> - 2019-04-14 14:52:38
|
I did not issue notes for the previous release since a new one was imminent anyway. I am attaching them here. - The user interface is now able to use GDK instead of X11, which means much smoother operation on Windows and Macintosh. - UFO 2 and UFO 3 are now handled as separate formats, which allows us to support more of the UFO 3 format. Some workflows may need adjustment as a result. See this bulletin <http://fontforge.github.io/en-US/bulletins/ufo3_2018_1/> for more information. - FontForge now tolerates a much wider range of syntax in feature files. - FontForge can now import and export WOFF2. - FontForge now supports Unicode 12.1.0. - The Python interface now allows finer interaction with splines. On Sun, Apr 14, 2019 at 3:43 AM T J <jt...@ou...> wrote: > Hi all, > > > > FontForge has been updated to the 2019-04-13 release. > > > > This is mostly a bugfix release on top of the 2019-03-17 release. Most > notably, it resolves a crash on MacOS when browsing directories that > contain empty files. Plugins support and direct http/ftp integration has > also been removed. > > > > The source tarball, MacOS, Linux (AppImage) and Windows binaries are all > available from https://fontforge.github.io. > > > > Thanks, > > Jeremy > _______________________________________________ > Fontforge-announce mailing list > Fon...@li... > https://lists.sourceforge.net/lists/listinfo/fontforge-announce > |
|
From: Mauro S. <mau...@gm...> - 2019-04-14 08:49:17
|
.deb packages are not yet ready? thanx ms Il 13/04/19 12:45, T J ha scritto: > Hi all, > > FontForge has been updated to the 2019-04-13 release. > > This is mostly a bugfix release on top of the 2019-03-17 release. Most > notably, it resolves a crash on MacOS when browsing directories that > contain empty files. Plugins support and direct http/ftp integration has > also been removed. > > The source tarball, MacOS, Linux (AppImage) and Windows binaries are all > available from https://fontforge.github.io. > > Thanks, > > Jeremy > > > > _______________________________________________ > Fontforge-announce mailing list > Fon...@li... > https://lists.sourceforge.net/lists/listinfo/fontforge-announce > |
|
From: T J <jt...@ou...> - 2019-04-13 10:45:20
|
Hi all, FontForge has been updated to the 2019-04-13 release. This is mostly a bugfix release on top of the 2019-03-17 release. Most notably, it resolves a crash on MacOS when browsing directories that contain empty files. Plugins support and direct http/ftp integration has also been removed. The source tarball, MacOS, Linux (AppImage) and Windows binaries are all available from https://fontforge.github.io. Thanks, Jeremy |
|
From: Hübner P. <pet...@ph...> - 2017-01-18 09:17:53
|
Hello, my characters are already drawn with Illustrator, which is my favorite vector program. Unfortunately copy + paste from Illu to Fontforge doesn’t work (on my Mac). Is there any solution? Thanks in advance! Friendly Greetz Peter Hübner Homepage: http://PH-Layout.de E-Mail: pet...@ph... |
|
From: Frank T. <fra...@gm...> - 2016-10-21 16:46:12
|
Hi, Judith. The announcement list is only for release announcements, so incoming mail only goes to the list administrators rather than to the user community. If you want community support, I would suggest joining the users list <https://lists.sourceforge.net/lists/listinfo/fontforge-users>. I also don't understand your question, but I'll inquire further when you post there. Best wishes, Frank On Thu, Oct 20, 2016 at 11:19 PM, Dr. Judith Martha Prewitt < mad...@at...> wrote: > Is it possible to merge the following two sets of fonts: one in FontBook > on Mac Mini running under Sierra, available for Pages, and one in > LibreOffice on same machine running under same operating system? > > Judith Prewitt > > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, SlashDot.org! http://sdm.link/slashdot > _______________________________________________ > Fontforge-announce mailing list > Fon...@li... > https://lists.sourceforge.net/lists/listinfo/fontforge-announce > |
|
From: Mike W. <mik...@gm...> - 2016-10-21 15:22:02
|
Hi Judith, Here's something similar: http://superuser.com/questions/490922/merging-two-fonts Mike On 21 October 2016 at 16:16, Mike Wallbridge <mik...@gm...> wrote: > Hi Judith, > > For some reason I don't understand, your question about merging fonts came > into my inbox. I'm not a techy so don't know exactly what you mean but I > may have done something similar of late in editing a font to use certain > symbols I wanted to bring in for the purpose of music annotations. It was a > case of feeling my way along but ended up being much easier than I thought. > Anyway I used a free Mac app called FontForge and it was very intuitive, > though you do need to install XQuartz first. If you open a ttf font into > Font Forge you get basically a map of the keys and the symbols within and > can edit them by using copy and paste. So by opening up two fonts you can > shift symbols around to get what you're after. Very straightforward. The > file you end up with doesn't have the ttf suffix (I can't remember what it > is) but you can easily go on-line and find a converter. Rename the "new" > font and put it in the font folder. It should work with both Pages and > LibreOffice. I hope this helps. > > Cheers > Mike > > On 21 October 2016 at 05:19, Dr. Judith Martha Prewitt < > mad...@at...> wrote: > >> Is it possible to merge the following two sets of fonts: one in FontBook >> on Mac Mini running under Sierra, available for Pages, and one in >> LibreOffice on same machine running under same operating system? >> >> Judith Prewitt >> >> >> ------------------------------------------------------------ >> ------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, SlashDot.org! http://sdm.link/slashdot >> _______________________________________________ >> Fontforge-announce mailing list >> Fon...@li... >> https://lists.sourceforge.net/lists/listinfo/fontforge-announce >> > > |
|
From: Mike W. <mik...@gm...> - 2016-10-21 15:16:49
|
Hi Judith, For some reason I don't understand, your question about merging fonts came into my inbox. I'm not a techy so don't know exactly what you mean but I may have done something similar of late in editing a font to use certain symbols I wanted to bring in for the purpose of music annotations. It was a case of feeling my way along but ended up being much easier than I thought. Anyway I used a free Mac app called FontForge and it was very intuitive, though you do need to install XQuartz first. If you open a ttf font into Font Forge you get basically a map of the keys and the symbols within and can edit them by using copy and paste. So by opening up two fonts you can shift symbols around to get what you're after. Very straightforward. The file you end up with doesn't have the ttf suffix (I can't remember what it is) but you can easily go on-line and find a converter. Rename the "new" font and put it in the font folder. It should work with both Pages and LibreOffice. I hope this helps. Cheers Mike On 21 October 2016 at 05:19, Dr. Judith Martha Prewitt < mad...@at...> wrote: > Is it possible to merge the following two sets of fonts: one in FontBook > on Mac Mini running under Sierra, available for Pages, and one in > LibreOffice on same machine running under same operating system? > > Judith Prewitt > > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, SlashDot.org! http://sdm.link/slashdot > _______________________________________________ > Fontforge-announce mailing list > Fon...@li... > https://lists.sourceforge.net/lists/listinfo/fontforge-announce > |
|
From: Dr. J. M. P. <mad...@at...> - 2016-10-21 04:20:02
|
Is it possible to merge the following two sets of fonts: one in FontBook on Mac Mini running under Sierra, available for Pages, and one in LibreOffice on same machine running under same operating system? Judith Prewitt |
|
From: Jason P. <zi...@gm...> - 2016-10-04 19:46:05
|
Can the new version be compiled to run on earlier versions of Mac OSX than 10.10? On Tue, Oct 4, 2016 at 7:09 AM, Frank Trampe <fra...@gm...> wrote: > [image: Inline image 1] > Hi, folks. > > I'm happy to announce the October release of FontForge, a little late > perhaps, but worth the wait. It brings a number of changes. > > - The modern-looking theme featured on the website, created by Andreas > Larsen, now ships by default with FontForge. All old themes continue to > work. > - Handling of CID ranges, certain bitmap typeface formats, and spline > stroking is better and more consistent. > - FontForge now supports Unicode 9.0. > - We (and I mean mostly Jeremy Tan) fixed a number of user interface > quirks. > - And we fixed some crashes. > > > Go to the FontForge website <http://fontforge.github.io/en-US/> to get > the right package for your platform. > > Best wishes, > > Frank > > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, SlashDot.org! http://sdm.link/slashdot > _______________________________________________ > Fontforge-announce mailing list > Fon...@li... > https://lists.sourceforge.net/lists/listinfo/fontforge-announce > > -- -- Jason Pagura zimbach at gmail dot com |
|
From: Frank T. <fra...@gm...> - 2016-10-04 14:09:41
|
[image: Inline image 1] Hi, folks. I'm happy to announce the October release of FontForge, a little late perhaps, but worth the wait. It brings a number of changes. - The modern-looking theme featured on the website, created by Andreas Larsen, now ships by default with FontForge. All old themes continue to work. - Handling of CID ranges, certain bitmap typeface formats, and spline stroking is better and more consistent. - FontForge now supports Unicode 9.0. - We (and I mean mostly Jeremy Tan) fixed a number of user interface quirks. - And we fixed some crashes. Go to the FontForge website <http://fontforge.github.io/en-US/> to get the right package for your platform. Best wishes, Frank |
|
From: George W. <gw...@si...> - 2011-02-22 14:00:47
|
----- Khaled Hosny <kha...@eg...> wrote: > On Mon, Feb 21, 2011 at 07:25:31PM -0800, George Williams wrote: > > I've packaged up a new release of fontforge. > > Great! Not so great. I left out two patches. There's a new, new release now please use it instead. |
|
From: George W. <gw...@si...> - 2011-02-22 03:25:39
|
I've packaged up a new release of fontforge. |
|
From: George W. <gw...@si...> - 2010-04-29 20:25:59
|
I fear I no longer have time to provide (and support) binary releases, so the current release is source (and documentation) only. |
|
From: George W. <gw...@si...> - 2009-09-14 23:44:51
|
I have, I hope, posted a new release of fontforge. Sourceforge has changed it's release upload mechanism. It no longer seems possible to have sourceforge send out automatic emails announcing this fact. More troubling, sourceforge claims there is a 15 minute delay between my posting files and them being available for release. It has been several hours, and at the moment only three of the files I posted are displayed. Perhaps it takes longer than 15 minutes. Perhaps something more is broken. |
|
From: Barry S. <che...@ch...> - 2008-11-17 05:18:45
|
gw...@si... skribis: > The first time you run fontforge with Pango something takes several > minutes to initialize itself. This delay does not occur on > subsequent invocations. Building a font cache, perhaps, especially if it isn't depending on fontconfig for all the font info and so has to open all the fonts for itself. One has to wait similarly while LuaTeX uses fontforge code to build a font cache. :) |
|
From: <gw...@si...> - 2008-11-16 18:18:35
|
First release with Pango and Cairo. The first time you run fontforge with Pango something takes several minutes to initialize itself. This delay does not occur on subsequent invocations. The version of Cairo available from fink on the mac is so old that FontForge can't use it. The default fontconfig setup on the mac does not seem to find any outline fonts (reverting to bitmaps). Create a ~/.fonts directory yourself, and put some fonts there. Pango crashes on my cygwin system, so the cygwin build does not contain either Pango or Cairo. |
|
From: George W. <gw...@si...> - 2007-10-03 21:35:01
|
Support for Adobe's proposed cmap format=14 subtable (variation selectors) Support for making fontforge a python extension. |
|
From: <gw...@si...> - 2007-09-01 16:48:55
|
31-August-2007
* New traditional Chinese translation of the UI by Wei-Lun Chao.
* Updated Vietnamese translation by Clytie Siddall.
* Removed the old MetaFont command (which didn't work) and replaced it with
a styles menu (incorporating the old Effects menu, and a command to change
weight, to condense/extend, and to oblique. Added python scripting commands
{font,glyph}.{changeWeight,condenseExtend}
* Lots of new work on the truetype autoinstructor by Alexej and Michal.
* Add a validation dialog which can be run just before generating a font.
* Try a different algorithm for approximating splines by line segments (for
drawing them in the outline glyph view and elsewhere). This one should show
symmetry better.
* Provide the ability to ask freetype to rasterize glyphs without hints in
the Print/Display dlg (even if the glyphs have hints, rasterize them without).
* Oh dear, rasterizing stroked fonts only worked if multilayer was defined.
* Try to improve display of stroked fonts.
* When stroking splines don't let miter joins grow excessively.
* FF would remove instructions from glyphs that had at least two contours
the first of which started with a control point.
* Add a short cut for Hide Grid in the metrics view.
* Python 2.5 initializes itself differently from Python 2.[34]. 2.[34] delay
the init until an import happens, while 2.5 does it at start up. I just assumed
that when I called Py_Initialize that it did so. This led to a crash on 2.[34]
when I tried to use my types before the user had tried to import fontforge.
* Further improvements to tile path.
* When moving a control point in a ttf font where one side of the cp was a
real point, I would allow an implicit point on the far side of the real point to
become real.
* When dragging truetype points around, adjacent implicit points would
remain where they were (and not be implicit any longer).
* FF would randomly crash after removing a lot of glyphs.
* The knife tool would not cut a contour if it landed on a point.
* Trying to add a stylename to the size pane of fontinfo generally caused a
crash.
* All blank lines in the display dlg had the same line spacing as that of
the first character displayed in the dlg.
* I don't think feature files where handling classes defined with '-' properly.
* Read the "lib" structures from UFO/GLIF files into our python persistant
data. (And write our persistant data out if it's a dict).
* Add the ability to call hooks (python functions) when various fontforge
events take place.
* Make fontforge's basic types (Point, Contour, and Layer) be picklable so
they can now be saved in an sfd file.
* Oops. With the inclusion of the library check argument, ff would not
compile if NODYNAMIC were set.
* FontForge now stores the "userdata" python members into the sfd file as
pickled objects. (FontForge's own types are not currently pickleable).
* Add the ability to mark a glyph so that just before being saved its
references will be unlinked and we will run remove overlap on it. This means the
user can work with the references (and get the automatic updating they confer)
and still not have a self-intersecting glyph in the output (think Aring,
Ccedilla, Eogonek).
* Create a fontlint script file.
* When dumping both apple and opentype bitmap tables if there were a BDF
table, then we'd get garbage for 'bloc'/'bhed'.
* Add some user interface commands to python, and more importantly, add the
ability to create menu items which will invoke python scripts, and the ability
to add import/export conversion filters (again, python scripts).
* Counter hints for LCG glyphs came out wrong if autohint had not been
applied first.
* Counter masks were not read out of sfd files properly.
* Selecting a counter mask in Glyph Info caused FF to crash.
* The Execute Script dlg would sometimes complain about invalid scrollbar
size when it got closed.
* AddAnchorPoint (scripting command) should be prepared to cast real args to
integers.
* Just as I needed a special "in use" pass of GSUB when reading from a TTC,
so I also need an "in use" pass of the MATH table.
* All this time and I've mapped "nonmarkingreturn" (GID=2) to Unicode+000C
instead of Unicode+000D. I'm a twit.
|
|
From: George W. <gw...@si...> - 2007-07-24 02:39:11
|
23-July-2007
* I have merged (and substantially rewritten) the Print and
Display Dialogs. There is now only one menu item (Print) which
(vaguely) the old Display dlg except that it can now be printed.
The text area widget now supports OpenType features just as the
metrics view does. It also supports ligature carets.
The dialog is no longer modal, however it does not get updated
with each change to the font (that would make moving a point
around in the outline view far too sluggish), instead there is a
[Refresh] button the user can press to force an update.
* It occurred to me that fontforge's current mechanism for setting
ligature carets requires that there be a ligature substitution
is the exact number of components used to make the glyph. But in
indic fonts ligatures are often made up out of other ligatures
(I think) which means that there won't be enough caret
positions.
So I've added a Ligature Caret count to the Element->Glyph Info
dialog to give the user control over it when necessary.
* Add minimal support for applying apple state machine lookups in
metrics view. Support is minimal because:
* Apple seems to figure line breaks before doing
substitution process but I do it afterward so I don't
know where the line breaks are and I can't enter either
the line start or line end state.
* When I delete a glyph I delete it. Apple inserts a
deleted glyph mark and then removes that later. State
machines can respond to deleted glyphs, but I can't.
* I don't try to figure out which feature,settings should
be on by default. So the user must pick them out
manually.
* Add popup graphics to the Glyph Info and Lookup subtable dialogs
to show substitutions (that is if there is an entry like 'smcp'
a => a.sc then create a popup window showing the "a" glyph and
the "a.sc" so the user can see what happens.
* Another futile attempt at an embolden command. Element->Embolden
* Add shortcuts to the anchor control dlg (Page Up/Page Down) to
move to the next/previous glyph.
* Michal Nowakowski has improved the truetype autoinstructor. He
warns that it probably still has bugs (as what does not?) so I
am leaving the old code available for now. He says it works best
in "a clean (uninstructed) font with well defined blue zones and
stems".
* If we have a glyph with multiple encodings, and the secondary
encodings occur after the primary ones, then the backmap will
probably contain a secondary encoding, which means that when we
go to load the font in we will probably notice the secondary
encoding twice and forget the primary.
* I used not to distinguish between ligature anchors and normal
mark to base anchors. Unfortunately when I moved to lookups
(from features) I had to introduce that distinction. But I
didn't work through all the implications and have fixed a number
of bugs related to that.
* Barry SCHWARTZ complains that font info says "fontnames must"
but that the cited adobe tech note only says "should". So change
"must" to "should".
* When processing class-based contextual lookups fontforge could
not handle class 0 (the class containing "all glyphs not in
another class") add code to do that.
* If the user did not select a Gasp Version (note: active
selection was needed, just seeing that it was correct and
leaving it didn't work) then [OK] would leave the font with an
invalid version and on some systems caused a crash.
* View->Insert Glyph After didn't work well on a ligature glyph.
It would insert the glyph after the first component of the
ligature, not after the last -- which would make more sense.
* Misnamed some private dict entries when loading from otf.
* Make entry of ghost hints better.
* Add the ability to determine whether a point is selected or not
from python.
* Add a mechanism so the user can ask fontforge to check for the
existance of optional libraries.
* Add range checks to some library routines which blindly
referenced some BMP arrays with codepoints outside bmp. Broken
by UCS2->UCS4 change.
* Werner wants GotoChar to be able to switch sub-fonts in a cid
keyed font. This may introduce bugs...
* Revert glyph still wasn't working.
* Someone complained that using a negative stroke took a very long
time but produced correct results. Um. Ok. It's easy always to
use the absolute value.
* Oops. The mac uses UCS2 for filenames, so when I moved to UCS4 I
should have changed the mac resource file interface.
* When creating a mac resource file we only set the type/creator
fields and failed to initialize the finderFlags.
* Fixed crash bug in generating a cursive connection anchor
sub-table.
* In TrueType composite glyphs with the USE_MY_METRICS bit set the
lock icon wasn't scrolled properly.
* The change from UCS2 to UCS4 broke text copy/paste.
We failed to add a terminating NUL of the right size in all
cases
We continued to use charset=UCS-2 when it should have been UCS-4
* FF crashed when trying to View->Show ATT on a font that appears
to me to contain an invalid 'kern' sub-table. I have removed the
proximate cause of the crash. I have provided a warning that the
kern table appears invalid. And I have cleaned up my internals
after detecting the bad sub-table (I had a lookup with a feature
but no script and this caused problems).
* Multiple substitutions in the metrics view did not properly
update the count of glyphs to be displayed.
* If nothing changed in the metrics input field and the output
contained a ligature (or a mult subs I suspect). FF would
complain.
* in python, font.generate() didn't work. The
PyArg_ParseTupleAndKeywords behaves in a way I did not expect.
* [Bottom] and [Down] still didn't work for lookup subtables.
* Try to force the text field in the metricsview to a fixed size.
In some fonts it seems to be initialized to a huge value.
* Add ability to display italic side bearings in the char view.
* The lines drawn for italic fonts to show the italic origin and
width were at slightly the wrong angle (I used a sine when I
should have used a tangent).
* If a font did not have any horizontal metrics then ff would not
set the em-size.
* Show Att trampled on memory when displaying apple contextual
substitution state machines.
* Wasn't parsing apple's 'lcar' table properly.
* if a font contained a 'post' table but didn't name all names (or
something like that), then the attempt to name the glyph based
on the encoding was broken after the encoding change.
* FF did not recognize that a bdf file was greymaped. Broken by
the bdf properties work a year ago or so.
* The import lookups button in fontinfo forgot about the subtables
(sort of).
* The metricsview used the wrong count field to determine whether
things changed. It used the glyph count, not the char count
(which meant that when we had a ligature and the number of chars
was greater than the number of glyphs, things got confused.)
* In the metrics view, anchored attachments only worked if the
base glyph were itself unmoved (that is the mark was placed
relative to the unmoved location, not the actual location).
* The search dialog should provide user with control over the
error bound.
The rotate checkbox didn't work if the flip checkbox wasn't
checked.
* If a replace contour added a control point to a point that did
not have one (went from a line to a curve) then that control
point would get lost.
If a search matched across the start point of a contour then
search/replace could go into an infinite loop if the search and
replace paths were the same.
* Find/Replace (replace) didn't work on quadratic splines.
* Add two python methods:
* Layer.interpolateNewLayer(other-layer,amount)
* Font.createInterpolatedGlyph(glyph1,glyph2,amount)
The first creates a new layer by interpolating between the
current layer and the layer in the first argument.
The second creates a new glyph in the font by interpolating
between the first two arguments. The glyph's unicodecode point
and name will be copied from the first argument (the font must
not already contain this glyph).
If amount is 0 the result will look like the first glyph, if 1
then like the second.
* When recovering from a crash, FF would sometimes complain about
a mismatched version number. Don't.
* Problems parsing 'mort' tables could cause a crash.
* When building a contextual lookup, don't list that lookup as
something that it could invoke (ie. list all lookups in this
table (GPOS/GSUB) except for ourselves). Don't want to encourage
users to create infinite lookup loops.
* Point matching didn't work when there were references to
references and multiple references within a glyph.
* FF was having problems with extension lookups with multiple sub
tables.
* We were trying to print a trailing NUL in some strings from the
fontview.
* Kerning by classes got broken in metricsview by the addition of
support for device tables.
* A GPOS contextual lookup only listed GSUB lookups in the
lookup/sequence dlg
Pressing [OK] in the lookup/sequence dlg caused a crash if no
lookup selected.
* Openfontdlg was looking at the filter listbutton rather than the
rename namelist listbutton.
* mf2pt1 now uses "glyph_dimensions" rather than "bbox"
* The metrics view should now handle device tables.
* Goto could crash when used on small encodings.
* -lang wasn't permitted before -c.
* Use numeric text fields for anchor positioning.
* Graham Asher points out that the meanings of underline position
in the 'post' table and the FontInfo dictionary are different.
One refers to the top of the underline rectangle and one to the
center of it.
* Align point would crash if the selected point were the end point
of a contour (or if the two points around it were in the same
place).
* The baseline was not properly located when displaying it in the
fontview.
* The scripting command BitmapsAvail would generally cause FF to
crash if done when there was a UI..
* We seem to be misimplementing my obsolete (sfd file) convention
for having duplicate encodings point to the same glyph. Result
was that occasionally a glyph would be removed and a pointer to
something it refered to would be put in its place.
* Change the name of activeFontInUI to activeFont
Add an activeGlyph method.
Add the ability to call a python script from a outline view.
* Hmmm. If a textfield is shifted right, and then resized so
there's now room for all the text, the unshift it.
* Werner suggests that it would be useful to be able to specify
wildcards in the goto dlg.
* Michael Zedler tells me that glyphs output by mf2pt1 contain a
line:
% MF2PT1: bbox 0 90 834 422
where the third (so called) bounding box entry is actually the
glyph's advance width. I was reluctant to use this at first,
because that clearly isn't something that belongs in a bounding
box...
* Werner tells me that lilypond uses a slightly different syntax
for the MF2PT1 bbox comment, so make our parsing slightly more
generous.
* When creating a new lookup subtable for an anchored lookup, it
did not get marked as having anchor classes and feature file
output failed because of that.
* When outputing single lookups, the feature, script and language
tags all had ^A where they should have had the second letter of
the tag.
* Remove the code to produce the old, broken, 'size' feature.
|
|
From: George W. <gw...@si...> - 2007-05-02 05:13:43
|
I have posted a new release of fontforge. This release represents a
major change for fontforge.
1) OpenType features and lookups are handled quite differently now
(and non-OpenType stuff has been forced into that mold so it's
different too).
The changelog goes through the major differences
http://fontforge.sf.net/changelog.html
2) FontForge now supports python scripting. The (fontforge) python
modules are described at
http://fontforge.sf.net/python.html
this is not well tested, because I'm not very familiar with
python.
Not all of the executables have been build with python (because
I didn't know what the "standard" python version might be for that
system or because I did not want to force people to download
python in order to use fontforge.
I would like to thank Apostolos Syropoulos, Lee Chenhwa, Michal
Nowakowski, Philipp Poll, and Pierre Hanser for providing translations.
|
|
From: George W. <gw...@si...> - 2007-03-22 19:00:45
|
On Wed, 2007-03-14 at 19:01, George Williams wrote: > On Tue, 2007-03-13 at 07:40, George Williams wrote: > > Sometime later this week I hope to post an experimental build containing > > a major rewrite of the UI. > I had hoped that I would have time to finish rewriting the The metrics view has changed considerably. It displays all the features in the font, and allows you to select which ones you want active in the view. It lets you set the script & language. It will apply lookups that it couldn't handle previously like ligatures and contextuals. It does not do Indic glyph reordering. I'm not sure how to and last I checked MS had not updated their docs to reflect their new procedures. |
|
From: George W. <gw...@si...> - 2007-03-15 02:59:42
|
On Tue, 2007-03-13 at 07:40, George Williams wrote:
> Sometime later this week I hope to post an experimental build containing
> a major rewrite of the UI.
I had hoped that I would have time to finish rewriting the
documentation, but it appears that is not to be. (I go on vacation
tomorrow to run a marathon).
Instead I shall post an experimental source tarball into the file
release system (in the 12-March release), update the cvs tree, and write
a few words here about the differences.
The major change is that fontforge now presents lookups to the user
rather than features. I think this makes simple things more difficult
(which is why I avoided this when I started), but it makes complex
things possible.
Sadly the world is not simple.
So when a piece of typographic information is created (a ligature, a
kern pair, a glyph substitution, etc.) it must be tagged with a lookup
(actually a lookup sub-table) rather than a feature tag.
The lookup itself will be tagged with a feature tag (possibly several
tags) and with scripts and languages in which that lookup should be
active.
NOTE: This reverses the way GPOS/GSUB think about things, but it
contains the same information.
The Font Info dialog now contains a Lookup pane which allows you to
create and edit lookups and their subtables. You can also reorder them.
The order shown in the dialog is the order in which they will be
applied.
A mac feature/setting subtable also gets converted into this format.
The Font Info dialog no longer has Anchor Classes, Contextual, or State
Machine panes.
Instead you can edit a lookup subtable's data. There are new dialogs
which list all the information for each lookup type (ie. a dialog which
lists all kern pairs in a subtable), and these provide access to the old
anchor class, contextual or state machine dialogs.
The Glyph Info command has also changed. It looks simpler and more
comprehensible (I think), but the act of creating a new substitution has
become more complex because (potentially) one must create a new lookup
and lookup subtable before doing the simple task of adding a new
replacement glyph.
The kerning class, contextual and state machine dialogs have all changed
in that they no longer request a feature tag, they now need a lookup
subtable.
The metrics view also needs a subtable.
And so do many other dialogs.
Show ATT has changed, but it is still not editable. I hope that the
Lookups pane will do that instead.
There used to be a scripting command which indicated what ligature
features got stored in afm files. Now each ligature lookup has a flag
set on it which conveys this information.
The Element->Typographic Features menu has been removed. It's
functionality has moved into Font Info->Lookups (I hope I've got
everything).
Some scripting commands have been removed, others have been changed and
others have been added. I apologize for this, as it will break existing
scripts, but some basic concepts no longer exist and others, very
different, have replaced them.
Removed:
DefaultATT
ControlAfmLigatureOutput
ApplySubstitutions
CopyGlyphFeatures
AddATT Replaced with AddPosSub
RemoveATT
GlyphInfo(Position/Pair/Substitution/AltSubs/MultSubs/Ligature)
SelectByATT Replaced with SelectByPosSub
Changed
Set(V)Kern takes an optional third argument, a lookup subtable name
(if not specified it choses one)
AddAnchorClass(name,type,lookup-subtable-name)
GetPosSub(subtable-name)
AutoKern(spacing,threshold,subtable-name[,kernfile])
Added
AddLookup(name,type,flags,feature-script-lang-array[,after-lookup-name])
n*[feature-tag,script-lang-array]
n*[script-tag,lang-array]
n*[lang]
GetLookupInfo(lookup-name) => [type,flags,feature-script-lang-array]
AddLookupSubtable(lookup-name,subtable-name[,after-subtable-name])
GetLookupOfSubtable(subtable-name)
GetSubtableOfAnchorClass(anchor-class-name)
AddPosSub(subtable-name,variant(s))
(subtable-name,dx,dy,dadv_x,dadv_y)
(subtable-name,other-glyph-name,dx,dy...)
RemoveLookupSubtable(subtable-name)
RemoveLookup(lookup-name)
MergeLookupSubtables(subtable-name1,subtable-name2)
MergeLookups(lookup-name1,lookup-name2)
SelectByPosSub(subtable-name,search_type)
GetLookups("GPOS"/"GSUB")
GetLookupSubtables(lookup-name)
LookupStoreLigatureInAfm(lookup-name,store-it)
LookupSetFeatureList(lookup-name,feature-script-lang-array)
The sfd format has changed. New files are tagged as version 2. Old files
will still work, but ff will no longer produce file in the old format.
I'm not aware of any bugs...
:-)
|