From: Alexis Ballier <aballier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: USE flag transition: tetex and latex
Date: Sat, 10 Nov 2007 12:04:57 +0100 [thread overview]
Message-ID: <20071110120457.12f958f4@toz.strangled.net> (raw)
In-Reply-To: <19F48F64-7A56-4278-9C9B-6B3F481F7194@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1553 bytes --]
Hi,
> >
> > I don't think documentation using texinfo.tex (the documentation
> > that comes in .texi files) uses latex --- I believe that
> > texinfo.tex uses just plain tex.
actually you got a point; but let me show how the boundary is small:
take a texi file, process it with tex -> it works.
remove the \input texinfo at the beginning -> fails
run:
$ tex -ini -jobname=texinfo -progname=texinfo texinfo.ini
that will give you: texinfo.fmt and texinfo.log in the current directory
run as root:
# ln -s tex /usr/bin/texinfo
then run texinfo on your .texi file where you have removed the \input
(and in the same directory where you had texinfo.fmt) -> it works
funny heh ?
what is a format ? it's just : run tex on a file, dump the memory
of the interpreter and write it to a file.
what is latex ? bah it's just more or less the same thing: some tex
macros and definitions, processed through a tex engine to get latex.fmt
If you check it, the latex executable is just a symlink to the tex
engine used by your distribution ;)
Seeing that, should we call it tex, texi or texinfo ? is latex really
latex or should we call it tex ?
I don't have any answer to that, and I think we should have useflag
names that refer to commonly used names for what they represent. If you
tell me that .texi files are commonly referenced as tex stuff, then why
not tex; but I'd call it texinfo.
> Do we even provide plain tex via an ebuild or useflag?
for the above reasons, we have tex ;)
Regards,
Alexis.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-11-10 11:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-07 13:09 [gentoo-dev] Re: USE flag transition: tetex and latex Ferris McCormick
2007-11-10 2:03 ` Robert Buchholz
2007-11-10 11:04 ` Alexis Ballier [this message]
2007-11-10 14:12 ` Christian Faulhammer
-- strict thread matches above, loose matches on Subject: below --
2007-10-31 7:03 [gentoo-dev] " Christian Faulhammer
2007-10-31 10:38 ` Alexis Ballier
2007-11-01 8:10 ` [gentoo-dev] " Steve Long
2007-11-06 13:13 ` Christian Faulhammer
2007-11-06 14:42 ` Tobias Klausmann
2007-11-06 14:46 ` Christian Faulhammer
2007-11-06 16:44 ` Tobias Klausmann
2007-11-07 8:13 ` Alexis Ballier
2007-11-10 14:16 ` Christian Faulhammer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20071110120457.12f958f4@toz.strangled.net \
--to=aballier@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox