Received: by nummer-3.proteosys id <01C19443.A7E3CD5C@nummer-3.proteosys>; Thu, 3 Jan 2002 11:44:44 +0100 In-Reply-To: <9204260933.AA18413@danpost2.uni-c.dk> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C19443.A7E3CD5C" Return-Path: X-MimeOLE: Produced By Microsoft Exchange V6.5 x-vm-v5-data: ([nil nil nil nil nil nil nil nil nil][nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil]) Content-class: urn:content-classes:message Subject: L3 suggestion: different file extension Date: Sun, 26 Apr 1992 16:29:34 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Kresten Krab Thorup" Sender: "Mailing list for the LaTeX3 project" To: "Rainer M. Schoepf" Reply-To: "Mailing list for the LaTeX3 project" Status: R X-Status: X-Keywords: X-UID: 682 This is a multi-part message in MIME format. ------_=_NextPart_001_01C19443.A7E3CD5C Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Dominik Wujastyk writes: > >This may be a bit radical, but could it be possible for LaTeX files >to have the extension .ltx instead of .tex? > >I assume this is a function of tex the program, rather than of the >LaTeX macros. But I mention it in case there is some clever way >to achieve this by macro programming (Frank, Rainer and others >have already managed several things I would have said were impossible >with TeX). As TeX is now, it's not possible. The .tex extension is hardcoded into the program, and cant possibly be altered, without changing the TeX itself, and it would be impossible, to have all TeX installations changed to reflect this. The problem is not even specific to the command line, which at first glance may seem the only problem, but also, \input like commands, will fail, because, if you ask TeX to load the file `myfile' It will first try to see if it can find any files that are actually called `myfile', and then try `myfile.tex'. If a new macro for \input was coded to use `.ltx' as extension, it had to try to see if the expansion of the argument matched `.ltx' at the end, and then if not *always* apply this extension (This is quite hard to accomplish). You'd miss the possibility of having a name with either no extension or a extension different from `.ltx'. The other matter, the command line, is even harder. As TeX processes this, (or some pseudo first line of the document), the macro package (LaTeX) has not yet been loaded, and as so, I believe you can see why it's hard. In my oppinion it's a shame. In general, TeX i/o system is not much configurable in any way... Also, it would be nice if one could change the look of error messages, and also make some better way of displaying the fact that a file is beeing loaded. This is currently written as processing , which is quite hard to parse for some external program for possibly further processing. (I've made an attempt on writing a such parser for my LaTeX mode, AUC TeX, but it's much too heuristic (does guessing)). /Kresten ------_=_NextPart_001_01C19443.A7E3CD5C Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable L3 suggestion: different file extension

Dominik Wujastyk writes:
>
>This may be a bit radical, but could it be = possible for LaTeX files
>to have the extension .ltx instead of = .tex?
>
>I assume this is a function of tex the program, = rather than of the
>LaTeX macros.  But I mention it in case = there is some clever way
>to achieve this by macro programming (Frank, = Rainer and others
>have already managed several things I would have = said were impossible
>with TeX).

As TeX is now, it's not possible.  The .tex = extension is hardcoded
into the program, and cant possibly be altered, = without changing the
TeX itself, and it would be impossible, to have all = TeX installations
changed to reflect this.
        The = problem is not even specific to the command line, which at
first glance may seem the only problem, but also, = \input like
commands, will fail, because, if you ask TeX to load = the file `myfile'
It will first try to see if it can find any files = that are actually
called `myfile', and then try `myfile.tex'.  If = a new macro for \input
was coded to use `.ltx' as extension, it had to try = to see if the
expansion of the argument matched `.ltx' at the end, = and then if not
*always* apply this extension (This is quite hard to = accomplish).
You'd miss the possibility of having a name with = either no extension
or a extension different from `.ltx'.
        The other = matter, the command line, is even harder.  As TeX
processes this, (or some pseudo first line of the = document), the macro
package (LaTeX) has not yet been loaded, and as so, I = believe you can
see why it's hard.

In my oppinion it's a shame.  In general, TeX i/o = system is not much
configurable in any way... Also, it would be nice if = one could change
the look of error messages, and also make some better = way of
displaying the fact that a file is beeing loaded. = This is currently
written as <left paren><filename> = processing <right paren>, which is
quite hard to parse for some external program for = possibly further
processing. (I've made an attempt on writing a such = parser for my
LaTeX mode, AUC TeX, but it's much too heuristic = (does guessing)).

/Kresten

------_=_NextPart_001_01C19443.A7E3CD5C--