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: Fri, 14 Jan 2022 18:12:56 +0100
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: <[log in to unmask]>
Content-Type: text/plain; charset=UTF-8; format=flowed
From: Frank Mittelbach <[log in to unmask]>
Parts/Attachments: text/plain (31 lines)
Hi Robert

> Thank you!  I should have examined this more thoroughly.  I used dox
> because I needed a macro to describe options.  But now I see that I
> can say \NewDocElement{Option}{option}, which is fine.

one of the reasons for upgrading doc after such a long time was to add 
the ability to document other kind of code beside macros/envs so it how 
essentially offers what dox offered in the past but with a somewhat 
different API and a bit more functionality.

the other reason for upgrading was to enable hyperref support out of the 
box, because this is also usually wanted/needed.
> Something similar affects the colordoc package because it redefines
> doc's \macro@finish, which has been changed.
> What should we do?  Will the LaTeX3 team contact the authors of these
> packages or should rather I do it myself?

If could would do that and talk to Didier and Federico, it would be very 
much appreciated ... we are  stretched a bit thin, but if you prefer 
I'll do it.

Might also be worth talking to Scott because his skeletons could then 
perhaps also see some update