![](https://secure.gravatar.com/avatar/b16ca16bcbc474a1ba15813999e212da.jpg?s=120&d=mm&r=g)
From: frantisek holop
hmm, on Sat, Apr 08, 2006 at 11:12:56PM +0100, Sanjoy Mahajan said that
Thanks, those two space removals in enco-pfr.tex fix it. I guess when I upgrade to pdftex 1.30 I'll unchange it.
it seems that people are more afraid to upgrade their pdftex than context. in my opinion upgrading context is much harder, there are much more things which can go wrong.
Upgrading context is easy now that I keep it in ~/texmf/, so updates to the Debian tetex packages don't overwrite or shadow the latest context. My worry about upgrading pdf(e)tex is that when I do the next apt-get update && apt-get upgrade then my pdftex 1.30 will get wiped out by the v1.21 that comes with the slightly updated tetex-3.0. Then I'll have to regenerate the context formats (the apt-get upgrade will regenerate only the system formats, not my own). Already this overwriting happens with metapost 0.91: After upgrading the tetex, it gets returned to 0.63 or something like that. So I keep the 0.91 install tree around and wrote a Makefile to reinstall it over the 0.63 version (Taco has put that Makefile in the metapost distribution). But I'd like to minimize the amount of homebrew administration, which is why I keep my hands off pdftex. -Sanjoy `Never underestimate the evil of which men of power are capable.' --Bertrand Russell, _War Crimes in Vietnam_, chapter 1.