f



[9fans] dvips(1) for Plan9: done

Hello,

With some delay, as usual, the work is done and now dvips(1) is up and
running in kerTeX 0.8.0.0.

As an "advertising" feature, I have put on the site a (poor resolution)
jpeg conversion of Tomas Rokicki test page (generated on Plan9 so it
works...) just to give you the incentive to look.

Next step (and last for first complete release) will be MetaPost.

Here is an extract of the README file to give you a taste of the work
and modifications. But mind you, it is called README, and I really mean
it ;-)

----------8<
KerTeX dvips(1) is a modified version. Shall be noted mainly:

	- This a pure C89 version; all system dependent code has been
	removed.
		Specially, dvips(1) doesn't try anymore to send PostScript
	directly to the spooler : it produces a the PostScript
	program. Period. And it sends it, by default, to stdout. 
	So, whether redirect to a file:

$ kertex/dvips file.dvi >file.ps

	or:

$ kertex/dvips -o file.ps file.dvi

	or transfer to the spooler:

$ kertex/dvips file.dvi | lpr

		Only the directory separator and the system encoding are
	handled. But this is done by the R.I.S.K. infrastructure, and not
	the dvips code by itself (adaptations should be made if necessary
	to the R.I.S.K parameter files and the code should be left alone).
	The main goal was to still support ebcdic.

	- The support for "backtick commands" has been removed: the commands
	embedded in a dvi file and supposed to be executed directly via
	system or popen are not handled. (This is an important security risk
	and furthermore the result can be achieved by the user via
	preprocessing.)

	- The automatic generation of missing fonts (METAFONT) is still
	here, but it is not on by default: you have to specify the (new)
	option "-G" to get it. If the automatic generation was not set or
	if it fails for a missing font, the command line to use is sent as a
	comment on stderr for the user to have hints about what and how to
	do. It shall be noted that the missfont.log that was previously
	written to hold this information is no longer created.
		By principle, dvips(1) creates streams (on stdout and stderr)
	and does not write anything by default. Hence it can be used "flying
	over" a read-only directory.

	- emTeX and TPIC \special's handling is removed.

	- Support for HyperTeX (for PDF hyperlinks) is included.

	- Support for Adobe T1 works. By default (in the dvips.cnf file),
	the T1 version of the Computer Modern are used. The use
	of the fonts is set by map files, that specify the name used by TeX,
	the name to use in PostScript, perhaps a different encoding, and
	perhaps a file to embed in the PostScript code.
		All is a question of configuration (map files), and the simpler
	is to read Tomas Rokicki's manual, included in source form in the
	KerTeX distribution.
---------->8

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

0
tlaronde (278)
11/9/2010 4:01:20 PM
comp.os.plan9 9252 articles. 1 followers. quanstro (3876) is leader. Post Follow

2 Replies
407 Views

Similar Articles

[PageSpeed] 9

And I have forgotten the links:

http://www.kergis.com/kertex.html (fran=E7ais)

http://www.kergis.com/en/kertex.html (laronde's pseudo-english)

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

0
tlaronde
11/9/2010 4:07:54 PM
On Tue, Nov 09, 2010 at 09:18:59AM -0800, David Leimbach wrote:
> That's really great!  Thank you for sharing!
> 
> Just wondering if you'd tried ConTeXt on it (I believe it should work as I
> think it's also macros like LaTeX is on top of TeX).

No, I use my own stuff, riding piggyback on D.E. Knuth's plain macros.

But the scheme is always the same. So look at the post-install script
(conf/KERTEX_T.post-install in kertex_T sources) for the normal case,
and to the notes about LaTeX that has a special bootstrapping process.

As you write, as long as it is just macros (TeX is the engine), it
should work just adjusting the definition of the environment variables 
for the paths (or putting the stuff where kerTeX expects them by default
to be).

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

0
tlaronde
11/9/2010 5:38:25 PM
Reply: