ChangeLog:
3.18: 2017-08-01
Fix a packaging error, include NEWS in the tarball.
3.17: 2017-07-31
Add -b option to generate a table with binary code-points.
3.16: 2017-07-18
Add -a option to print in 4-column mode.
0-fill fix and octal code-point literals.
Performing substitutions during post-patch breaks tools such as mkpatches,
making it very difficult to regenerate correct patches after making changes,
and often leading to substituted string replacements being committed.
Problems found locating distfiles:
Package colorls: missing distfile ls.tar.gz
Package molden: missing distfile molden-4.6/molden4.6.tar.gz
Package softmaker-office-demo: missing distfile ofl06trial.tgz
Otherwise, existing SHA1 digests verified and found to be the same on
the machine holding the existing distfiles (morden). All existing
SHA1 digests retained for now as an audit trail.
(1) ${PREFIX} handling was not correct
(2) It is said ascii.cgi is deleted in ChangeLog, it was not taken care
properly.
3.14: 2013-11-27
ascii.cgi deleted: the <isindex> it relies on is archaic and nonconformant.
Thanks joerg@ for review.
- Add LICENSE= modified-bsd
(upstream)
- Update 3.08 to 3.14
From: http://www.catb.org/~esr/ascii/NEWS
---------------------------------
3.14: 2013-11-27
Recognize \0 as ASCII NUL.
ascii.cgi deleted: the <isindex> it relies on is archaic and nonconformant.
Markup improvements on the manual page.
3.13: 2013-11-20
Tweak Makefile to obey $(PREFIX) convention (from MacPorts).
3.12: 2012-11-23
Cygwin port fix.
3.11: 2011-03-15
Recognize single decimal or hex digits.
Minor bug fixes and additional character names from Debian.
3.10: 2010-10-19
License change to BSD. Polish code to modern fully-ANSI C.
3.9: 2010-10-13
Fix some bugs in the name table.
INSTALLATION_DIRS, as well as all occurrences of ${PREFIX}/man with
${PREFIX}/${PKGMANDIR}.
Fixes PR 35265, although I did not use the patch provided therein.
developer is officially maintaining the package.
The rationale for changing this from "tech-pkg" to "pkgsrc-users" is
that it implies that any user can try to maintain the package (by
submitting patches to the mailing list). Since the folks most likely
to care about the package are the folks that want to use it or are
already using it, this would leverage the energy of users who aren't
developers.
