Bitbucket is a code hosting site with unlimited public and private repositories. We're also free for small teams!

Close
Contents:
---------
        
ps-print.tar.gz has the following files:

   ps-print-X-Y-Z/README			This file
   ps-print-X-Y-Z/ps-print-20.new		News for Emacs 20
   ps-print-X-Y-Z/ps-print-21.new		News for Emacs 21

   ps-print-X-Y-Z/lisp/ps-print/ps-bdf.el	BDF font file handler
   ps-print-X-Y-Z/lisp/ps-print/ps-mule.el	multi-byte character facility
   ps-print-X-Y-Z/lisp/ps-print/ps-print.el	main file
   ps-print-X-Y-Z/lisp/ps-print/makefile	Makefile for byte-compiling
						ps-print with Unix-like systems
						(Unix or Win32 with cygwin)
   ps-print-X-Y-Z/lisp/ps-print/make.bat	Batchfile to byte-compiling
						ps-print with Win32-Systems

   ps-print-X-Y-Z/etc/ps-print/ps-prin0.ps	prologue file 0
   ps-print-X-Y-Z/etc/ps-print/ps-prin1.ps	prologue file 1

Where X is the version number, Y is the release number and Z is the subrelease
number.  The Z part is optional, so it's possible to exist ps-print-X-Y/.

   
Installation:
-------------

1. Add the lisp-subdirectory of your ps-print installation to your load-path.
   You can do this in your .emacs or site-start.el with:

   (add-to-list 'load-path "/your/path/to/ps-print/lisp")

2. Go to the lisp subdirectory of ps-print:

   cd ./ps-print/lisp/ps-print

3. Type:  make.
   On Unix or Cygwin-Environment, this will run the makefile file.
   On Windows 9X/NT/2000 environment, this will call make.bat.
   This will byte-compile all Emacs Lisp files (*.el files).

4. Install the prologue files.

   On GNU Emacs, the prologue files (ps-prin*.ps) should be installed in
   directory given by `data-directory' variable which contains a string like
   "/usr/share/emacs/20.3/etc/".

   On XEmacs, the prologue files (ps-prin*.ps) should be installed in directory
   given by `(locate-data-directory "ps-print")'.

   If you wish to install prologue files in another directory, you should
   customize `ps-postscript-code-directory' to contain the directory.  I
   recommend this way.

   One way to set `ps-postscript-code-directory' is to insert in your ~/.emacs:

      (setq ps-postscript-code-directory "/directory/of/prologue/files/")
      ;; (I recommend this way)

   Or type:

      M-x set-variable RET ps-postscript-code-directory RET
      "/directory/of/prologue/files/" RET

   Or type:

      M-x ps-print-customize RET
      and customize `ps-postscript-code-directory'.


Happy hacking


Vinicius
http://www.cpqd.com.br/~vinicius/emacs/

Recent activity

ben

Commits by ben were pushed to xemacs/ps-print

c500df5 - fix package compilation; update locale start files, profile docs XEmacs.rules: text-modes is also needed due to dependency of texinfmt on whitespace. XEmacs.rules: Remove auto-autoloads if ...
michaels

Commits by michaels were pushed to xemacs/ps-print

bcf92ae - 2004-07-25 Michael Sperber <mike@xemacs.org> * Makefile (ELCS): Include ps-mule.elc always, even when not building for Mule: it's required.
viteno

Commits by viteno were pushed to xemacs/ps-print

1c23225 - Robert Widhopf-Fenk's patch in <16415.37153.511654.989754@gargle.gargle.HOWL>.
Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for ProjectModifiedEvent.java.
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.