Sender: |
|
Date: |
Sat, 15 Jan 2022 09:41:08 +0100 |
Content-Disposition: |
inline |
Reply-To: |
|
Subject: |
|
MIME-Version: |
1.0 |
Message-ID: |
|
In-Reply-To: |
|
Content-Type: |
text/plain; charset=us-ascii |
From: |
|
Parts/Attachments: |
|
|
Hi Frank,
On Fri, Jan 14, 2022 at 06:12:56PM +0100, Frank Mittelbach wrote:
> 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.
I read the documentation last night. These are great improvements,
thank you!
> >
> > 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
I just did. I opened an issue on Github for dox and passed on a few
lines to Frederico Garcia (colordoc) and Scott about incompatibilities
and upcoming changes.
Best,
Robert
> best
> frank
> >
|
|
|