From: Jin Guojun (ITG staff) <jin@george.lbl.gov>
BJC-240 in color mode is supported as well by the bjc600 and bjc800 driver.
BJC-240 b&w is supported by bj200. Added this to configure dialogue.
From: Luigi Rizzo <luigi@labinfo.iet.unipi.it>:
Support for encrypted PDF files by replacing pdf_sec.ps with the
free and legal version from:
http://www.ozemail.com.au/~geoffk/pdfencrypt/pdf_sec.ps
Deceided to update the pathnames of font files for easier
maintenance, because they revamped their ftp archive structure
to "5.10/files".
Submitted by: various people
The FreeType engine is a free and portable TrueType font rendering
engine. It has been developed to provide TT support to a great
variety of platforms and environments.
From the release notes: 5.10 is a special release to clear up
problems in the PDF writer (ps2pdf) affecting NSF's FastLane proposal
submission program: we have tested its output and verified
compatibility with the Acrobat software that NSF uses. Relative to
5.03, the only other changes in 5.10 are some improvements in the
PDF interpreter to handle more PDF 1.2 (Acrobat 3.x) constructs,
and a number of bug fixes.
PR: 5095
Reviewed by: maintainer
Submitted by: Jeff Bartig <jeffb@doit.wisc.edu>
Delete empty line in pkg/DESCR to make portlint happy and
add a @dirrm in pkg/PLIST.
round of improvments made it much larger, was instead an exact duplicate
of the new a2ps. This commit should fix that.
I'm the maintainer of the new port, and seeing as this one won't be changing
again (unless to remove it) I guess it won't need one.
Ordered by: asami
bsd.port.mk that will be committed soon, this will disable automatic
package building when PACKAGE_BUILDING is defined (so they can be
built from separate scripts).
These are no-ops for ordinary users (i.e., when PACKAGE_BUILDING is
not defined).
This is a development release, but I can't get any of the "stable" releases
to build properly and run w/o dump core with xforms 0.86.
(they use an even/odd version numbering scheme like Linux)
Lyx has entered a somewhat code-freeze for an upcoming 0.12. So this version
should be ok (better than "stable" 0.10.7 is on FreeBSD at the moment...)
See: http://bonk.ethz.ch/hp850/hp850.html
Additional driver will be fetched directly from internet now
Because this driver source is packed as a .zip file (tada *sigh*)
and contains ^M's (where the combination \^M confuses gcc) we have
to BUILD_DEPEND on unzip and pipe the source and header files through
sed to wipe out the ^M's ...
As requested by: Lars Koeller
Makefile:
- Changed WRKSRC
- New GS_SOURCES
- Make symbolic link from jpeg-6a and libpng port's workdir into
WRKSRC, instead of patching unix-gcc.mak further:
ln -s ${PORTSDIR}/graphics/jpeg/work/jpeg-6a ${WRKSRC}/jpeg-6a
ln -s ${PORTSDIR}/graphics/png/work/libpng-0.96 ${WRKSRC}/libpng
- updated md5 files
patches/patch-aa:
- new unified diff because some of the above mentioned changes
- Only commented out the default DEVICE_DEVS
- make our zlib compile again
pkg/DESCR:
- bumped version number
pkg/PLIST:
- updated PLIST
- added proper @dirrm's for a successfull pkg_delete action
scripts/configure:
- added new drivers
"la70t" "DEC LA70 printer with low resol. text enhancement" ON \
"lq850" "EPSON LQ-850 (360x360), ok for Canon BJ300 in LQ850 emul" ON \
- rmoved one unnecessary "pdfwrite"
- same for scripts/configure.batch
As requested by: Lars Koeller ;-)
"?=" to "=" for MAKE_FLAGS, bsd.port.mk is read later anyway. Change
"/usr/local" to "${PREFIX}" and "/usr/bin/false" to ${FALSE}. Remove
spurious empty lines.
Many of the above found by: portlint
- merged patch-af into patch-aa, both patches hacked unix-gcc.mak
- merged the scripts/{configure,configure.batch} changes into
patch-aa, so that unix-gcc.mak is hacked only by patch-aa
- when doing interactive configuration, every device driver is
now turned on, so you have to deselect devices
- when using BATCH compilation, you now get every supported device,
this one is especially for Satoshi, when making gs packages !
- Added a note into unix-gcc.mak, that DEVICE_DEVS now completely
are removed in the makefile, instead of this, the two configure
scripts now completely control, which devices have to be compiled in.
So, the configure target "patches" the unix-gcc.mak Makefile and
puts a DEVICE_DEVS line at line 1. When doing batch compilation
every device is included in this line, or the wanted devices ...
- The compilation option -DA4 is now included if you compile the port
by saying "make A4=yes".
I hope, I didn't forget a driver, look at that long line ;-)
BTW, I didn't create that DEVICE_DEVS line by hand, I did the
interactive installation, which created it automatically, and
after that I "stealed" that DEVICE_DEVS line for inclusion
into configure.batch ;-) So the devices in configure and configure.batch
are exactly the same, you only have to compare devices.mak with one
of the configure scripts.
BTW, should we nuke ghostscript4 ??? Does somebody know if any
port needs gs4 ???
would think if looking for it there... but I have been quite wrong before.
But then I also don't think this and all the TeX stuff belong in "print"
either. They are wordprocessing tools. But I guess we really don't
have that categrory, with editors being the closest. But then TeX
is probably the farthest port we have to actually being an editor.
Maybe "lang"??? It is a translstor afterall. :-)
on this list (which will set their files/md5 entry to "IGNORE") or
have a correct checksum. There were two files missing from this
list and their checksum entries were not updated (they included
version numbers).
(2) Don't set NO_CHECKSUM in a port to get around bug (1). ;)
on this list (which will set their files/md5 entry to "IGNORE") or
have a correct checksum. There were two files missing from this
list and their checksum entries were not updated (they included
version numbers).
(2) Don't set NO_CHECKSUM in a port to get around bug (1). ;)
PostScript interpreter itself. The problem is that some (most?) PostScript
level 1 interpreters (such as the Apple Laserwriter Plus!) don't define
the ISOLatin1 encoding vector AND don't define a character called `minus'.
Therefore, substituting `hyphen' (which is always defined) for `minus',
isn't really `wrong' aesthetics not withstanding! :-) A conditional patch
would (IMHO, say Jeremy) be overkill: the only people that would be
interested in it are typographers, and they probably don't use mp to
format their mail anyway.
Submitted by: Jeremy Prior <jez@netcraft.co.uk>
