On 2014-11-04 05:59-0800 Alan W. Irwin wrote: > On 2014-11-04 12:16-0000 phil rosenberg wrote: > >> I just wanted to let you know that I just successfully managed to > build the documentation under Cygwin - Alan you were right, I just > needed the actual font files to be put in the correct location. I > thought it would be good to document things somewhere, but not sure > where - the Wiki perhaps? Or should this be included somewhere in the > build or developer docs? > > The right location is doc/docbook/README.developers. >
To Arjen and Phil: I am quite impressed by this big Cygwin breakthrough pioneered by Phil since building our documentation in the past on anything but Debian systems was not easy. But on reflection I am concerned that moving font files around (which is what Phil appears to have done above) is only a workaround for some Cygwin font issue that could and should be solved in a much more straightforward way. Therefore, I urge you two to follow up here with discussion of what the correct solution to the above Cygwin font issue should be. I have no idea how Cygwin handles fonts. Nevertheless, here are two possible solutions to the above issue that I can think of right away from my font experience on Linux. 1. It is possible the above issue could be solved by installing another Cygwin font package beyond the TeX font package that Phil installed. In this case, a bug report concerning the TeX font package should be reported to Cygwin since Phil's installation of the TeX font package should have also automatically installed the additional font package. 2. It is possible the correct solution to the above issue might just be that Phil needs to configure Cygwin to look in additional locations for Windows system fonts. Or if Cygwin has no flexibility about where it looks for system fonts, then a wish-list bug report should be fired off to them to implement this flexibility in future. I have mentioned these two possibilities only to get the discussion going, and I hope you two follow up and figure out together the correct way to solve this Cygwin font issue if it is not one of the above two possibilities. @Arjen: I strongly suggest you attempt to replicate everything Phil is doing concerning building the documentation on Cygwin on general principles (so you gain important experience with everything possible on Cygwin) but also to allow Phil to benefit from your own Cygwin expertise, e.g., to figure out what he has to do to get Cygwin to interact properly with Windows system fonts. 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 __________________________ ------------------------------------------------------------------------------ _______________________________________________ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
