[1682] in Release_7.7_team

home help back first fref pref prev next nref lref last post

latex2e conversation with boojum

daemon@ATHENA.MIT.EDU (oliver thomas)
Thu Feb 25 12:32:57 1999

To: release-team@MIT.EDU
Cc: oliver thomas <othomas@MIT.EDU>
Reply-To: oliver thomas <othomas@MIT.EDU>
Date: Thu, 25 Feb 1999 12:32:50 EST
From: oliver thomas <othomas@MIT.EDU>


hi, i spoke with laura regarding latex2e dependencies and compatibility.

latex2e as the default would be very good.

backwards compatibility is very good.  

a few things to watch out for:

postscript fonts are different for latex2e, so users manipulating
postscript fonts directly may notice compatibility problems.  fonts that
are currently handled through sty files won't be affected.  expected
impact is light, and consulting can handle the few who run into problems.

sipb and consulting need to be notified to update some latex utilities and
sty files supported by these groups (consider consulting notified).  sipb
supports tgrind.  laura has been building lgrind in newtex for various
platforms, but not for all platforms.  if latex2e becomes the default,
lgrind should probably move into sipb which is where tgrind is now.  (fyi
lgrind does for latex2e what tgrind does for latex.)

some matlab latex dependencies will need updating, so alex should be
notified.

the thesis templates as they currently stand work with latex2e.  they do
cause latex2e to run in compatibility mode, so some of the latex2e
specific features are not available.  a two-line change is required to not
make latex2e run in compatibility mode for these templates.  laura and one
of our students are going to take care of that.

i think that's it.  let me know if i missed anything.

thanks,

oliver

home help back first fref pref prev next nref lref last post