|author||Drew Parsons <email@example.com>||2009-10-29 20:26:23 +1100|
|committer||Drew Parsons <firstname.lastname@example.org>||2009-10-29 20:26:31 +1100|
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.
1 files changed, 15 insertions, 0 deletions
diff --git a/README b/README
new file mode 100644
@@ -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
+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.