9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: tlaronde@polynum.com
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] kerTeX upgrade: PostScript handling
Date: Sun, 18 Dec 2011 16:30:30 +0100	[thread overview]
Message-ID: <20111218153030.GB16479@polynum.com> (raw)

Hello,

I have published a new version of kerTeX: 0.9.6.3.

The main changes:

	- The handling of the reencoded fonts names for PostScript has been
	corrected; this impacts dvips(1) and MetaPost, and the dvips.cnf
	file.
	- Dvips(1) allowed more form of comments in the font map files than
	MetaPost, while the two programs were supposed to share some:
	MetaPost now accepts all the comments accepted by dvips(1).
	- The reserverd string "KERTEXSYS" can be added as the last
	alternative of a search path specification. This adds the default
	system search paths to the specification.

It can be noted that I found some blunders in the way the font names
were handled in the PostScript code generated by dvips(1), and despite
the advertised "with million of users! thousands of programmers!
hundreds of developers! a GPL code is reviewed by millions of pairs of
eyes!", these ones were still here after 15 years of "community"
software engineering...

Go figure!

Furthermore, there was some discrepancy between dvips(1) and MetaPost in
the way comments were handled in configuration files (psfonts.map) they
share.

To make a point, I use MetaPost for a great deal of my drawing, from
designing buttons for a GUI to layout scripting (legends and all) for
printed maps: the combination of MetaPost and TeX leads to a printing
solution I find hard to beat or to compete with (I use it
professionnaly, mind you...).

So I do encourage people to try. It's all here:

http://www.kergis.com/kertex.html

and please do! read the README!

--
        Thierry Laronde <tlaronde +AT+ polynum +dot+ com>
                      http://www.kergis.com/
Key fingerprint = 0FF7 E906 FBAF FE95 FD89  250D 52B1 AE95 6006 F40C



                 reply	other threads:[~2011-12-18 15:30 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20111218153030.GB16479@polynum.com \
    --to=tlaronde@polynum.com \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).