At 11:27 +1000 98/06/23, Richard Walker wrote: >Hans Aberg writes: > > So here, they way I see it, the long names (1) are only used really in > > order to keep the code straight and avoid code clashes. The user > > (preferably also developers) should only need to use short names by various > > of simplifying schemes; this is (2) then. But non-local names should expand > > to long names. > >Hmm . . . this is the exact opposite of what I was suggesting. >Developers use the long names to make it easier to write; these get >translated by docstrip/doc.sty into short names to minimize format >size and control sequence usage. Still no word from the Team as to >whether this matters for LaTeX3. This is an idea I did not think of. But I think we are speaking about different things here: By "long names", I thought of names with a sequence of module separators \foo/bar/.../blah, and short names abbreviations used locally by the user working in a local context which does not have those mpodule separators, or not as many of them. But I am not sure what translation procedure you think of: The reason of using a long name like \environment/begin instead of say \envir/begin would be to ensure this name does not clash with other names. If one wants to shorten those names, it wiuld be better to define a module named `envir' right away. Hans Aberg * Email: Hans Aberg <mailto:[log in to unmask]> * Home Page: <http://www.matematik.su.se/~haberg/> * AMS member listing: <http://www.ams.org/cml/>