diff options
author | Drew Parsons <dparsons@debian.org> | 2009-10-29 20:26:23 +1100 |
---|---|---|
committer | Drew Parsons <dparsons@debian.org> | 2009-10-29 20:26:31 +1100 |
commit | e5dfe6b4987b5723ea0c7fe88f5ff821ee3e44f5 (patch) | |
tree | e1dce4e3500be1643f42642c5a773c64d78dc8d7 | |
parent | 48dcb52fb56999b59d8b8ff037a127cbd4fddca1 (diff) |
README discusses build issues around libXfont 1.4.
libXfont 1.4 removed Xprint font support, so need built-in fonts:
Need ./configure --enable-builtin-fonts
However this causes unresolved segfaults in client programs.
The default situation (--disable-builtin-fonts) successfully uses
external fonts but only builds against libXfont 1.3.
Also included suggestion to use libcairo instead of Xprint for those who
need the WYSIWYG or print-to-pdf/postscript functionality.
-rw-r--r-- | README | 15 |
1 files changed, 15 insertions, 0 deletions
@@ -0,0 +1,15 @@ +Xprint is now deprecated. + +For a WYSIWYG-style printing API giving equivalence between what appears in an +X windows and what gets printed on paper or to pdf or postscript, you may want +to consider using libcairo, the Cairo graphics library +(http://cairographics.org/) + +Font support for Xprint was removed from libXfont 1.4. To build Xprt under +libXfont 1.4 (or later) you will need to use built-in fonts + ./configure --enable-builtin-fonts +(By default built-in fonts are not used, equivalent to --disable-builtin-fonts). + +However built-in fonts may cause a segfault in client programs, which has not +been debugged since Xprint is deprecated. For an operational Xprt you may want +to built against libXfont 1.3. |