Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
bluevalues array (FF showed it as not having a bluevalues array at all, the two are different).
(pfb files with empty arrays worked as expected).
|
|
fail to open it (and produce a garbage error message). I suspect the underlying problem would cause other problems too, but haven't found any yet.
|
|
changes).
|
|
the window. So... let's try not doing that.
|
|
smaller than it should have. Well that's screen size and window manager dependant. It did allow 10 pixels of horizontal border (not knowing what the WM would give it). That's probably too much. And even if a tiny bit of the window is off the screen, it probably doesn't matter much.
|
|
other files which reference them).
|
|
|
|
|
|
Someone complained ff was expecting "exact" arithmetic, when, in fact, he did not understand the nature of the logic involved. The exact tests were not likely to be hit, but were present just in case. The real test was elsewhere.
|
|
|
|
direction) in the "Change glyph" dialog. This approach produces
better results for glyphs like "N" or "g", and thus seems more logical
even for the Latin script, where vertical stems are normally "thick"
and horizontal ones are "thin".
This patch also affects some gdraw internals, since the new layout
of the "Change glyph" dialog makes it necessary to dynamically switch
the captions of some labels, and the text strings should fit to the space
initially reserved for those labels. So it is now possible to assign a
list of strings to a label, just like if it was a list button.
|
|
by my previous patch and occurs due to a wrong selection of the expose area:
when doing vertical scrolling, the whole table, rather than just the current
line, should be redrawn).
Also FF used to set the list mark width (and related values) at the very end
of the matrix edit control creation process, and so function indicators
were disregarded when calculating the initial column widths.
|
|
broke Add Extrema. Reinstate it.
|
|
caused by an uninitialized variable. Fixed.
|
|
per glyph in the coverage table. This meant that it would sometimes make a table that was slightly too big to be supported and not realize it. I've fixed the bug, and put in checks so that if there's yet another problem like this, at list it will be reported to the user.
|
|
in the outline glyph window. This builds on that and supports it in (I hope) all windows. Also adds support for apple's wheel which can do both horizontal and vertical motion.
|
|
that's not what Adobe does. Many cids get mapped to several code points each. So I've revamped the format to support this. The new map files need the new code (obviously) so don't download one without the other.
|
|
|
|
|
|
|
|
support: filename(fontname) notation for pdf).
|
|
returned an empty array when asking if they contained fonts.
|
|
|
|
|
|
work as expected (mostly expose issues, affecting vertical scrolling).
|
|
|
|
|
|
|
|
|
|
edit rather than the old clumsy list with editing area kludge.
|
|
to English speakers, dlg won't have fields overrunning other fields in French).
|
|
|
|
locale but convert them to the "C"==PostScript locale when storing them. That is a French user could enter [3,5 20] for BlueValues, but it needs to be converted to [3.5 20] when put in the sfd file (or PS font file).
|
|
|
|
|
|
|
|
become "long double" when appropriate, but doubles stay doubles. I didn't get everything, just the ones I thought important.
|
|
|
|
1. Since the {Everything Else} class is now recognized by FF as a valid
glyph class, it was possible to occasionally modify a kerning value
involving this class in the metrics view. So when asking user if he
is going to modify a class-based kerning value or create a new kerning
pair, inform him if one of the glyphs from this pair has been actually
matched by the {Everything Else} class.
2. Make it possible to easily deselect all glyphs in the metrics view
by pressing [Escape].
|
|
scripts), and a particular glyph is present in more than one set, then
attempting to find a matching kerning value between this glyph and a
subsequent glyph might result in selecting the combination with the
{Everything Else} class from the first set being processed, even if there
are better matches in other sets.
Also FF would still complain that the "{Everythin Else}" string in the
kern class dialog represents a missing glyph.
|
|
with freetype. This guarantees more accurate rendering of hinted fonts
in monochrome mode.
|
|
bitmap-only fonts. This seems to make no sense for TTF, where widths of
rasterized glyphs can be set independently for each PPEM.
|
|
window, the add_char_to_name_list preference item was not respected.
|
|
|
|
|
|
|
|
here are some errors in quadratic spline processing.
|
|
|
|
been there a long time.
|