Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <194230-220029412194917207@cantv.net>
Reply-To: rodmedina AT cantv DOT net
X-ORIGINATOR-IP: 200.44.136.133
From: "rodmedina AT cantv DOT net" <rodmedina AT cantv DOT net>
To: cygwin AT cygwin DOT com
Subject: Bugs in CYGWIN teTeX
Date: Thu, 12 Sep 2002 15:49:17 -0400
MIME-Version: 1.0
Content-type: text/plain; charset=ISO-8859-1

Dear Mr. Esser:
 I have just installed the teTeX distribution that comes with CYGWIN, I
have found various bugs that, after a week of pain, I have resolved.
The problems were:

1- XDVI Configuration: Unconvinient shrink buttons; the initial shrink ratio
  does not correspond to any button. In the texconfig v0.99
  in the run_xdvi_setup_mode() function are defined 4 buttons, but actually
  the shrink buttons are only 3. The fullsize button is not the #1. Instead
  of "b1=1; b2=2; b3=3; b4=4" it should be "b1=2; b2=3; b3=4". Actually, for
  a small screen with 300dpi I have found better "b1=2; b2=4; b3=6".

2-xdvi fails to find poscript fonts. After generating the ghostscript fonts
  with the t1mapper, xdvi still makes pk files for postscript fonts.
  The problem is with the file ps2pk.map in which the gs fonts appear with
  an encode number they should not have. Example, instead of
 
ptmr8r NimbusRomNo9L-Regu "TeXBase1Encoding ReEncodeFont" <8r.enc
<utmr8a.pfb
                                                                       ^^
it should be

ptmr8r NimbusRomNo9L-Regu "TeXBase1Encoding ReEncodeFont" <8r.enc <utmr.pfb

3-All the fonts are allways done in the working  directory and not
  in VARTEXFONTS. The problem is due to the kpathsea script mktex.opt. Here
  the path-separator is set SEP=';' as in DOS, but CYGWIN is like  UNIX.
  The problem is that such script uses the fact that COMSPEC is defined
  to deduce that the OS is DOS-WINDOWS. In CYGWIN COMSPEC is also defined.

4- Using the terminal RXVT the texconfig dialog does not appear. The fact
   is that RXVT claims to be xterm but actually it is not. But it is vt100
   compatible, so if one sets TERM=vt100, everything is OK. With the true
   xterm of X11 texconfig works fine.

I hope that this information could be useful.

	Rodrigo Medina
	Centro de Fisica,IVIC, Venezuela
	rmedina AT ivic DOT ve



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/