• R/O
  • SSH
  • HTTPS

tsukurimashou: Commit


Commit MetaInfo

Revision461 (tree)
Time2013-08-27 02:04:02
Authormskala

Log Message

last-minute doc update; ready for 0.8

Change Summary

Incremental Difference

--- trunk/doc/usermanual.tex (revision 460)
+++ trunk/doc/usermanual.tex (revision 461)
@@ -941,7 +941,11 @@
941941 not observed recently and probably fixed by now.
942942
943943 \item FontForge rasterization to BDF via FreeType as opposed to whatever
944- other code FontForge would use: sometimes produces corrupt results.
944+ other code FontForge would use: sometimes produces corrupt results,
945+ which has complicated indirect consequences because the Tsukurimashou
946+ infrastructures uses BDF files as input to the auto-kerning program. As
947+ a result, when this bug bites the horizontal metrics go screwy on some
948+ fonts---notably, Jieubsida Batang PS ends up looking monospaced.
945949 Reported to FontForge mailing list in November 2011, inspiring FreeType
946950 maintainer Werner Lemberg to find and fix an unrelated bug in FreeType
947951 (it was unable to process BDF files with high code points; see
@@ -949,11 +953,18 @@
949953 actually affect us because FontForge uses its own code for BDFs instead
950954 of FreeType's anyway, and Lemberg says can't help with the corrupt
951955 rasterization. Workaround is to compile FontForge without FreeType
952- support; from GUI it is possible to just turn off FreeType rasterization
953- on individual bitmap-creation operations, but that option doesn't seem
954- to be available from the scripting language and so the package has to
955- actually be built without FreeType. As of April 2012, seems not to
956- be an issue with Arch Linux's packaged versions.
956+ support; from the GUI it is possible to just turn off FreeType
957+ rasterization on individual bitmap-creation operations, but that option
958+ doesn't seem to be available from the scripting language and so the
959+ package has to actually be built without FreeType. As of April 2012,
960+ seems not to be an issue with Arch Linux's packaged versions. However,
961+ as of a few minutes before the Tsukurimashou~0.8 release (ouch!), this
962+ is a problem again with the lastest FontForge, and the latest FontForge
963+ now requires FreeType, so the workaround of disabling FreeType no longer
964+ works. I've reported it as FontForge GitHub issue number 685
965+ (\url{https://github.com/fontforge/fontforge/issues/685}), am hacking my
966+ local copy of FontForge to generate distribution fonts, and will hope to
967+ get it resolved properly in mainline FontForge as soon as possible.
957968
958969 \item FontForge attempts to modify the names of all glyphs that it thinks
959970 are ``related'' whenever a glyph name changes for any reason.
@@ -2431,7 +2442,7 @@
24312442 spline geometry. A workaround, used in my Tsukurimashou 0.8 distribution
24322443 packages, is to override the options for \texttt{fontlint.pe} as follows:
24332444 \begin{verbatim}
2434-make DISTCHECK\_CONFIGURE\_FLAGS='FONTLINT_FLAGS="-w 2,3,5,23"' distcheck
2445+make DISTCHECK_CONFIGURE_FLAGS='FONTLINT_FLAGS="-w 2,3,5,23"' distcheck
24352446 \end{verbatim}
24362447
24372448 The \texttt{DISTCHECK\_CONFIGURE\_FLAGS} variable specifies additional flags
Show on old repository browser