Re: Release / status of teTeX
> As already mentioned in an announcement on the tetex-pretest list > >(http://www.mail-archive.com/tetex-pretest%40informatik.uni-hannover.de/msg00369.html) > you can have the latest teTeX beta (2002-04-02) _and_ the fix by applying > http://www.tug.org/teTeX/teTeX-src-beta-20020402-expdvips.patch.gz. > Afterwards the dvips(k) version is still 5.86g, but the bug is fixed > (at least for me). After some testing of the patch, it was applied to the main version of dvips and the version number was increased. So, a patched 5.86g is about the same as the new 5.90a. Thomas
Re: Release / status of teTeX
On Wed, 29 May 2002, Erik Frisk wrote: > Hi, > > > The -G1 option in dvips (can be activated on the commandline or in a > > config file; typically it is enabled in config.pdf) turn on a feature > > named "character shifting". This works around bugs in various other > > software, by shifting characters of a font to the "upper" area of a > > font. This works well e.g. with CM fonts, but it fails if the upper > > slots are not free in the font. > > Yes, this I have noted and have therefore commented out G in config.pdf > Which softwares has bugs that make character-switching necessary? The "bug" is the use of a zero byte to mark the end of a string in standard C strings (you lose \Gamma and math minus). Problems have been seen in early versions of Acrobat Reader, and many drawing programs that claim to import PS files. Since the native graphics API's on most common platforms use C strings, character shifting remains useful in situations where you want to import a PS file or translate it to another format. One notable exception was NeXTStep, which used Display PS and Objective-C. -- George White <[EMAIL PROTECTED]> Halifax, Nova Scotia
Re: Release / status of teTeX
Thomas Esser wrote: >> >>I, for another reason, updated to the latest teTeX beta (2002-04-02) and >>the dvips version included is: >> >>>dvips --version >> >>dvips(k) 5.86g >>kpathsea version 3.3.7 > > > The *next* teTeX pretest will have that fixed dvips. TeX Live 7 won't > have that fix. But, Sebastian is working on a "TeX Live Special Edition > for TUG 2002" which will also have that fix, I guess. As already mentioned in an announcement on the tetex-pretest list (http://www.mail-archive.com/tetex-pretest%40informatik.uni-hannover.de/msg00369.html) you can have the latest teTeX beta (2002-04-02) _and_ the fix by applying http://www.tug.org/teTeX/teTeX-src-beta-20020402-expdvips.patch.gz. Afterwards the dvips(k) version is still 5.86g, but the bug is fixed (at least for me). +Thomas -- Thomas Anders <[EMAIL PROTECTED]> Hahn-Meitner-Institut Berlin, Germany
Re: Release / status of teTeX
> Which softwares has bugs that make character-switching necessary? I am not the expert on this, but the things I know are Acrobat Reader (don't know exactly when they fixed that bug, but version 3.x are broken) and Adobe Illustrator. > I, for another reason, updated to the latest teTeX beta (2002-04-02) and > the dvips version included is: > > dvips --version > dvips(k) 5.86g > kpathsea version 3.3.7 The *next* teTeX pretest will have that fixed dvips. TeX Live 7 won't have that fix. But, Sebastian is working on a "TeX Live Special Edition for TUG 2002" which will also have that fix, I guess. Thomas
Re: Release / status of teTeX
Hi, > The -G1 option in dvips (can be activated on the commandline or in a > config file; typically it is enabled in config.pdf) turn on a feature > named "character shifting". This works around bugs in various other > software, by shifting characters of a font to the "upper" area of a > font. This works well e.g. with CM fonts, but it fails if the upper > slots are not free in the font. Yes, this I have noted and have therefore commented out G in config.pdf Which softwares has bugs that make character-switching necessary? > The new fix (dvips(k) 5.90a or later) checks on a per font basis if > character shifting is possible. I, for another reason, updated to the latest teTeX beta (2002-04-02) and the dvips version included is: > dvips --version dvips(k) 5.86g kpathsea version 3.3.7 Or did I misunderstand and it is texlive who has the updated dvips? /E - Erik Friskemail: [EMAIL PROTECTED] Dept. of Electrical Engineering tel:+46 13 285714 Linköping Universityfax:+46 13 282035 S-581 83 Linköping SWEDEN www.fs.isy.liu.se/~frisk -
Re: Release / status of teTeX
> No, not a 100% corresponding release. I have the -G1 fix for dvips and > the "downgrade update" for Omega (1.15 is the best version currently > available, the TeX Live version is not that stable). What is "the -G1 fix for dvips"? /Erik - Erik Friskemail: [EMAIL PROTECTED] Dept. of Electrical Engineering tel:+46 13 285714 Linköping Universityfax:+46 13 282035 S-581 83 Linköping SWEDEN www.fs.isy.liu.se/~frisk -
Re: Release / status of teTeX
> > No, not a 100% corresponding release. I have the -G1 fix for dvips and > > the "downgrade update" for Omega (1.15 is the best version currently > > available, the TeX Live version is not that stable). > > What is "the -G1 fix for dvips"? The -G1 option in dvips (can be activated on the commandline or in a config file; typically it is enabled in config.pdf) turn on a feature named "character shifting". This works around bugs in various other software, by shifting characters of a font to the "upper" area of a font. This works well e.g. with CM fonts, but it fails if the upper slots are not free in the font. Example: $ cat x.tex \font\x=ptmr7t\x fi\end $ tex x; dvips -G1 x -o The fi ligature appears as some other character when a broken dvips is used. The new fix (dvips(k) 5.90a or later) checks on a per font basis if character shifting is possible. Thomas
Re: Release / status of teTeX
> Now that the latest tex-live release is practically on its way out the > door, can we expect a corresponding teTeX release? No, not a 100% corresponding release. I have the -G1 fix for dvips and the "downgrade update" for Omega (1.15 is the best version currently available, the TeX Live version is not that stable). In the very near future, I plan to release a new teTeX-pretest. teTeX-2.0 (the next "stable" release) is not too far away, too. There are so many improvements that have been recently made, which justify raising the version number to 2.0 for the next stable release. > (The relationship between tex-live and teTeX seems shady to me at best...) program sources === It is like this: TeX Live is available in an online repository which I can read/write. I have a separate (non-public) source tree where I keep the teTeX sources. If I have something new, I usually put it into the teTeX tree first. If I ask Sebastian if he wants that for TeX Live, he always says "yes". Then, either I send him something, or I check it in directly. But, I am not the only person who contributes to teTeX / TeX Live. Other people make fixes / new stuff available for TeX Live either by sending stuff to Sebastian or by directly updating the online repository. >From time to time (sometimes several times a day) I sync my local copy of TeX Live with the online repository and get all the updates. Then, I take all the useful stuff and put it into the teTeX source tree. Having the software at different places causes some maintenance overhead, but I think that no real development work is doubled. texmf tree == We both maintain our own "texmf" tree, but from time to time we copy stuff from each other... > I currently > run the latest teTeX beta personally, but don't dare expose more than > a select few of my users to it - although I must say have had no I think that the latest "beta" stuff has much less problems than the old "stable" stuff. That's yet another reason why it is time for a new stable release. Thomas