aboutsummaryrefslogtreecommitdiff
path: root/graphics/fontforge/README
diff options
context:
space:
mode:
Diffstat (limited to 'graphics/fontforge/README')
-rw-r--r--graphics/fontforge/README13
1 files changed, 7 insertions, 6 deletions
diff --git a/graphics/fontforge/README b/graphics/fontforge/README
index 9ad488289b56..b6cef4ebe8d7 100644
--- a/graphics/fontforge/README
+++ b/graphics/fontforge/README
@@ -6,10 +6,11 @@ another. FontForge has support for many Macintosh font formats.
From the README-unix file inside the source:
If you want to edit CID-keyed fonts (for CJK fonts) you may want to pull
down the cidmap package from http://fontforge.sf.net/cidmaps.tgz
-If you download this file and place it in the directory with the SlackBuild
-script, the script will automatically place the cidmaps inside the package.
+We have included it with our tarball, but you might want to check for a
+newer version just in case. If you have it in the directory with the
+SlackBuild script, it will automatically place the cidmaps inside the package.
-You might also want to have an extracted copy of the freetype source code
+You will also want to have an extracted copy of the freetype source code
available inside the extracted SlackBuild tarball directory - in other words:
/somedir/fontforge/
README
@@ -17,6 +18,6 @@ available inside the extracted SlackBuild tarball directory - in other words:
fontforge.info
slack-desc
freetype-2.3.5/
-Fontforge seems to build (and function) just fine without doing this, but
-it does look for the freetype sources while compiling, so it's probably
-best to make them available just in case :)
+Fontforge seems to build (and function) just fine without doing this (this is
+at least true for prior versions), but it does look for the freetype sources
+while compiling, so it's probably best to make them available just in case :)