On 2014-11-10 21:14-0000 phil rosenberg wrote: > Just to keep you updated on the Cygwin fonts, Someone on the Cygwin mailing list directed me to https://cygwin.com/ml/cygwin-announce/2014-07/msg00000.html. Look under the heading fontconfig - there is also a link where the devs explain why it happens. Basically when new fonts are placed in the tex folders the fontconfig cache must be updated by calling fc-cache and they were worried this wouldn't be done.
@Phil: Thanks for passing on those interesting links. My interpretation of your thread (started at https://www.cygwin.com/ml/cygwin/2014-11/msg00154.html) is that Ken Brown used your post to remind Yaakov once again to fix this issue that Ken had discussed previously in <https://cygwin.com/ml/cygwin-announce/2014-07/msg00000.html> and <https://cygwin.com/ml/cygwin-xfree/2014-05/msg00018.html>. So it does appear the Cygwin devels were already aware of the issue, but hopefully your user report will provide motivation for Cygwin to fix this issue in a timely manner. @Phil and Arjen: Until Cygwin gets this issue fixed, I suggest you use their suggested workaround (referred to in <https://cygwin.com/ml/cygwin-announce/2014-07/msg00000.html>. It appears that workaround is similar to what is stated now at doc/docbook/README.developers except that /etc/fonts/fonts.conf (part of the libfontconfig1-2.11.1-1 package) is edited instead of creating a new file /etc/fonts/local.conf, and instead of specifying <dir>/usr/share/texmf-dist/fonts</dir> alone (which contains huge numbers of fonts that are not all compatible with fontconfig, it is recommended that the more specific <dir>/usr/share/texmf-dist/fonts/opentype</dir> <dir>/usr/share/texmf-dist/fonts/truetype</dir> <dir>/usr/share/texmf-dist/fonts/type1</dir> directories are used instead which greatly limits the number and kind of TeX fonts that fontconfig has to deal with. Note, I don't think specifying the directories either in /etc/fonts/fonts.conf or /etc/fonts/local.conf should matter, but the latter is preferred since it doesn't mess up a file that is under package control. However, I now believe it is really essential to specify the 3 directories above rather than just the one. @Arjen: for the pure Cygwin case, I think if you move to the three-directory workaround, that might well be the solution to the BI.tfm font issue that you hit earlier today. That change will rightly exclude fontconfig being made aware of BI.tfm which does not reside in any of the above specific directories. After all *.tfm files are font metric files (see <http://en.wikipedia.org/wiki/TeX_font_metric>) and not true font files so it is extremely unlikely that fontconfig is designed to work with them at all. Anyhow, please let us know if the three-directory workaround for these Cygwin font issues works for you. Alan __________________________ Alan W. Irwin Astronomical research affiliation with Department of Physics and Astronomy, University of Victoria (astrowww.phys.uvic.ca). Programming affiliations with the FreeEOS equation-of-state implementation for stellar interiors (freeeos.sf.net); the Time Ephemerides project (timeephem.sf.net); PLplot scientific plotting software package (plplot.sf.net); the libLASi project (unifont.org/lasi); the Loads of Linux Links project (loll.sf.net); and the Linux Brochure Project (lbproject.sf.net). __________________________ Linux-powered Science __________________________ ------------------------------------------------------------------------------ Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk _______________________________________________ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
