* Use freetype's FT_Outline_Get_Bitmap to make freetype rasterize from our internal data structures. Use freetype by default for the fontview and metricsview (except in some cases).
* The bitmap dlg didn't work for multilayered fonts when told to use freetype to rasterize.
* If we had a contour nested inside another, and did an Overlap Exclude with the nested contour selected, then that contour was not excluded.
* The []Correct Direction check box when importing PostScript, didn't do anything. (or rather it did, but got overrulled later)
* In bitmap only fonts, bitmaps created without moving the width line would get lost.
* Added a scripting command "SelectByColor"
* Don't apply transformations to glyphs which aren't worth outputting
* Moving control points with the get point info command had problems in quadratic splines.
* When adding type42 support I broke multiple master support.
* Werner provided a patch to add a trailing newline to my type1 fonts.
* Support for PaintType==2 and stroked fonts.
* Various problems with the clustering command
* Oops, somehow a patch reverted and things didn't work on systems without iconv
* worked on a couple of other configuration problems for the mac
* Some people install libraries without headers. Be prepared.
* Uniscribe (MS unicode text layout routines) may ignore either the GPOS or the GSUB table depending on the script, and may even refuse to use the font at all if it doesn't have the right stuff in GPOS/GSUB. A Hebrew font must have both a GPOS and a GSUB. If it doesn't the font is not used. A latin font need not have either, but if it doesn't have GSUB then GPOS won't be used.
* CapsLock now makes the arrow keys scroll in the outline view
* We lost count of hints when generating type2 fonts in glyphs with references
to something containing hints which did not overlap. If we were unlucky,
<new-cnt+7>/8 was different than <real-cnt+7>/8 and we ended up with garbage
in the charstring.
* Add a TeX table to contain TeX metrics.
* TFM output was wrong. the TFtoPL doc says "reencoding with original encoding
could create a glyph table one too small resulting in writing/reading garbage
and an eventual crash.
* KANOU fixed a couple of problems in reading glyph names from bdf fonts.
* KANOU needed to disambiguate between "Point" a unit of measurement and
"Point" a geometric object.
python*-pth packages into meta-packages which will install the non-pth
packages. Bump PKGREVISIONs on the non-pth versions to propagate the
thread change, but leave the *-pth versions untouched to not affect
existing installations.
Sync all PYTHON_VERSIONS_AFFECTED lines in package Makefiles.
XMBDFED CHANGES
Version: 4.5
Date : 09 November 2001
==========================
1. Fixed handling of double quotes in properties.
2. Fixed an incorrect value in a switch statement having to do with EOL's.
3. Fixed a bug dealing with adding properties to fonts.
4. Fixed numerous warnings about possible use of uninitialized variables.
5. Fixed an invalid indication of no next page when glyphs pasted span more
than one page.
6. Fixed a problem with drawing offsets in the GlyphTest widget in
right-to-left drawing.
7. Started a "Tips" section in the Help text.
changes:
2.2.97
Fc-cache sleeps before exiting to ensure filesystem timestamps are well
ordered.
Added Punjai orthography.
The timestamp in fonts.conf is gone now. Too many problems.
The default font path includes all of the X fonts; use selectfont/rejectfont
to eliminate bitmaps, as shown in the sample local.conf file.
<include> configuration elements may now reference a directory. Files
in that directory matching [0-9]* are loaded in UTF-8 collating sequence order.
<selectfont> configuration added to control which fonts are used.
fontformat font pattern elements built from the FT_Get_X11_Font_Format
function in newer versions of FreeType.
'capability' list constructed from gsub/gpos and silf values in TrueType
files.
Multi-lingual names (style, family, fullname) extracted and stored with
parallel <foo>lang properties marking language.
2.2.98
Share object name strings (Michael Meeks)
Eliminate a couple of codepoints from Russian orthography (John Thacker)
Add synthetic emboldening configuration changes (Jakub Pavelek)
Change FcFontSetSort to ignore language after fonts with the requested
languages have been found. (Owen Taylor)
Add some RedHat font configuration changes (Owen Tayler).
Add full Unicode case folding support to case-ignoring string functions
(Keith Packard)
Remove Han characters from Korean orthography (Tor Andersson)
* Ah, windows pfm files expect the metrics to be output in win latin encoding
order, not in the encoding defined by the pfb file. (Actually there are other
posibilities for encoding, but as none is documented, I must ignore them).
* ReplaceWithReference broke at some point
* Add an argument-pair to the ReplaceWithReference() scripting command to allow
the user to specify the amount of error that will be accepted.
* When generating a Type1 font, if a glyph had a single reference to a glyph not
in adobe encoding, and that glyph itself had a single reference (in adobe enc)
and some splines, then ff would make a reference to the ref in adobe enc and
ignore the splines.
* Upgrade to Adobe-Japan1-6
* Various fixes to svg output
* Ghost hints could get outside a glyphs bounding box in a type2 font.
* The generated truetype unique id string had an off by one error in the month
* Add support for dashed lines in multilayered mode
* In Full Page Glyph printing, the glyph was offset slightly from where it
should have been.
* Pasting a reference into a multi-layered font produced a very odd layer
* ff didn't update the metrics view if the user pasted the selection with the
middle mouse button.
* if a character were not in the current encoding then ff would not display it
in the metrics view (even if it were in the font)
* Make the behavior of control points at the ends of open paths more reasonable
* The Point->Curve command did not adust control points correctly
* The View->Display Substitutions had numerous problems
* Fix several problems from unicode unification of accents. Many characters
which are said to be based on cedilla actually use a comma, other characters
said to be carons also use comma. Make the n-with-apostrophe character be
treated as an accented letter.
* Werner points out that straight lines should generally not be simplified (as
they will no longer be straight afterwards). Add this knowledge to the
simplify command.
they do not get generated as side effect of the installation of other
packages and break PLISTs. With help from salo to get it right, thanks.
Bump PKGREVISION.
EC PostScript Type1 fonts with TFMs for TeX
These are PostScript Type1 renderings and TFMs of the EC variant of
the standard TeX CMR font family. These fonts include characters with
European accents.
GNU LilyPond depends on this.
Authors: Han-Wen Nienhuys <hanwen@cs.uu.nl>
Jan Nieuwenhuizen <janneke@gnu.org>
Previously, ttmkfdir's output was redirected to fonts.dir,
while the correct behaviour is to let it create fonts.scale
and then let mkfontdir merge fonts.scale into fonts.dir.
type1 handling had a similar problem.
Get the wanted behaviour by automatically appending the contents of
FONTS_TTF_DIRS and FONTS_TYPE1_DIRS to FONTS_X11_DIRS.
Also, save a subshell in install/fonts while there.
Bump PKGREVISION for all affected packages.
jmmv@ says ok.
module directory has changed (eg. "darwin-2level" vs.
"darwin-thread-multi-2level").
binary packages of perl modules need to be distinguishable between
being built against threaded perl and unthreaded perl, so bump the
PKGREVISION of all perl module packages and introduce
BUILDLINK_RECOMMENDED for perl as perl>=5.8.5nb5 so the correct
dependencies are registered and the binary packages are distinct.
addresses PR pkg/28619 from H. Todd Fujinaka.
Changes 20041115:
* If ff started without a prefs file, then creating a new font would crash
* If a copyright string contained a newline then ff would generate bad
postscript
* If user added a comment to an empty glyph then the comment wasn't saved in
the sfd file.
* If ff saved a utf7 string to an sfd file (ttf names, etc.) and that string
contained a hyphen that followed immediately after something that needed to
be encoded in base64, then the hyphen would be lost.
* new french UI
* ff was (usually) setting the ascent/descent fields of the 'hhea' table to 0.
When the font was drawn on the mac it was clipped to nothing.
But it is needed to build.
So use BUILD_DEPENDS instead of DEPENDS.
(This is the way the xorg-fonts* packages do it.)
Also bump PKGREVISIONs for these.
(Okayed by maintainer, Juan RP.)
ttf2pk/ttf2tfm permit using TrueType fonts with teTeX.
To be used for pkgsrc-wip/cjk-latex & friends (fixes and
a working cjk-latex-wadalab font pkg to be committed too)
in the process. (More information on tech-pkg.)
Bump PKGREVISION and BUILDLINK_DEPENDS of all packages using libtool and
installing .la files.
Bump PKGREVISION (only) of all packages depending directly on the above
via a buildlink3 include.
