LATEX-L Archives

Mailing list for the LaTeX3 project


Options: Use Classic View

Use Monospaced Font
Show HTML Part by Default
Condense Mail Headers

Topic: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Sender: Mailing list for the LaTeX3 project <[log in to unmask]>
Date: Sun, 17 Mar 2013 11:28:22 +0000
Reply-To: Mailing list for the LaTeX3 project <[log in to unmask]>
Message-ID: <[log in to unmask]>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
In-Reply-To: <20130316121332.GA5586@csmvddesktop>
Content-Type: text/plain; charset=ISO-8859-1
From: Joseph Wright <[log in to unmask]>
Parts/Attachments: text/plain (32 lines)
On 16/03/2013 12:13, dongen wrote:
> There may be a better way.
> Why don't the latex3 team provide a kernel method that people can use to
> register their prefixes? The idea is that this method takes the prefixes
> as input and writes them to some auxiliary file. When a package is uploaded
> to CTAN, all the CTAN team have to do is use the package once and add the
> output of the auxiliary file to the prefix database.

I've thought about something similar, but as Frank outlines there is
then the question of collecting up the data. In my mind, I'd wondered
about an extension of \ProvidesPackage or something akin

      author = A. N. Other,
      prefix = foo,

At the moment, I'm simply aiming to make a start on the concept of
'managing the namespace'. That's done in other languages: the Perl
people have a lot of advice on that for picking names, for example. (One
thing we have that's different from say Perl is that CTAN is run by a
very small team and isn't set up to take an 'enforcement' line, whereas
CPAN does seem to have an element of that.)

The idea of a simple database is that we can start now and then look to
improve things. At least at the moment, adding things is manageable for me.
Joseph Wright