www.delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1999/05/19/07:40:10

Date: Wed, 19 May 1999 13:39:47 +0200
From: Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
Message-Id: <199905191139.NAA04486@acp3bf.physik.rwth-aachen.de>
To: djgpp AT delorie DOT com
Subject: Re: txi, texi files supposed to be read?
Newsgroups: comp.os.msdos.djgpp
Organization: RWTH Aachen, III. physikalisches Institut B
X-Newsreader: TIN [version 1.2 PL2]
Reply-To: djgpp AT delorie DOT com

In article <7hu23a$9lj$1 AT hfc DOT pacific DOT net DOT hk> you wrote:
> I had found so many files with the extension txi, texi in the current
> release of djgpp (v2)

That shouldn't be the case in a 'normal' installation. The .txi and
.texi files should only be in the *d.zip and *s.zip files, but not in
the *b.zip ones that you normally should be installing. *s.zip is the
source and *d.zip is *extra* documentation for printing and other
purposes. For a typical DJGPP installation, you shouldn't need either
of them, unless you want to modify DJGPP itself.

> I realized that I could use makeinfo.exe to convert those files into .inf
> format that were to be read by info.exe

Actually, the resulting .info files will generally already be in the
*b.zip distribution files, so you shouldn't have to generate them
yourself.

> Just did not understand that whether txi and texi (and so on related
> files)were to be read by a human user or not?

In a nutshell: no, they're supposed to be *written* by humans, and
read by the computer, to be translated into either readable .info or
printable .dvi files.

Of course, you can read the .txi file directly, if you want to, but
the .info or printed output is way easier to read, normally.

-- 
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019