[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[AUCTeX-devel] Re: Missing bits and pieces...

From: Ralf Angeli
Subject: [AUCTeX-devel] Re: Missing bits and pieces...
Date: Thu, 21 Jul 2005 00:00:10 +0200
User-agent: Gnus/5.110004 (No Gnus v0.4) Emacs/22.0.50 (gnu/linux)

* David Kastrup (2005-07-20) writes:

> We have an install-contrib target for bib-cite.el and tex-jp.el, and
> the undocumented tex-fptex.el (as opposed to tex-mik.el).
> That's pretty much inconsistent.  I think we should include everything
> in a normal installation (yes, this also means tex-mik.el and
> tex-fptex.el on a Unix-type installation currently), and the "contrib"
> distinction does not seem to make sense to me.  I think I'd also want
> to include tex-jp.el even on non-MULE XEmacs installations where
> tex-jp.elc can't be generated.

I'm mostly with you.  But what use are tex-mik.el and tex-fptex.el in
a Unix-style environment?  If it's easy to determine if AUCTeX is
being built in/for such an environment, they could be excluded from
the installation.  But as they are small files it's not a big deal to
leave them in in case such a test is hard to do or error-prone.

BTW, regarding tex-jp.el: What happens if tex-jp.elc is included in an
RPM package or something like this and loaded by a non-MULE XEmacs?
Will this throw an error?

> I am not conclusive about what documentation to include in the
> packages.  After Ralf has rearranged the doc directory, recompiling
> the texi sources is trivial even without Makefile.  Should people be
> able to compile a printable manual?  Or should we just include the
> info file?  How about the plain text stuff?
> People in the States will need to have reference sheet and so compiled
> with a different paper size if we include any PS or PDF.  So maybe
> just include the sources?

In general we should include it completely in an accessible and
neutral format (e.g. not for a specific paper size).  That means
besides the info format, the manual should be included either as plain
text or HTML.  As the plain text files we know have (README, INSTALL,
etc.) are a mostly generated from the manual, I think we don't need to
ship them separately.

The refcard is somewhat special.  How about providing PDF files both
in A4 and letter format for it?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]