For use of the LaTeX discussion group. The purpose of this list is to discuss the development of the successor to LaTeX version 2e. Please direct general questions about version 2.09 and 2e to other lists. It is, however, perfectly allowed to point out deficiencies which should be improved in the next version. Note: ----- If mail to a list member is rejected three times, the corresponding mail address is deleted without further notice.
Any of the -dev engines fail to compile the attached .dtx file if the “dox” package is loaded, but I am not sure the failure is caused by this package.
(pdf|xe|lua)latex-dev engines seem to bump into \@doc@describe which is defined in doc-v3beta.sty.
Am Fri, 14 Jan 2022 08:44:06 +0100 schrieb Robert Alessi:
> Dear List, > > Something happened with today's update. > > Any of the -dev engines fail to compile the attached .dtx file if the > “dox” package is loaded, but I am not sure the failure is caused by > this package. > > (pdf|xe|lua)latex-dev engines seem to bump into \@doc@describe which > is defined in doc-v3beta.sty.
On Fri, Jan 14, 2022 at 09:07:13AM +0100, Ulrike Fischer wrote: > Am Fri, 14 Jan 2022 08:44:06 +0100 schrieb Robert Alessi:
[More ...] > > Any of the -dev engines fail to compile the attached .dtx file if the > > “dox” package is loaded, but I am not sure the failure is caused by > > this package. > > the new doc version used in latex-dev incorporates a few ideas of > dox, see the documentation. Beside others it now also defines the > command \SpecialMacroIndex, and defines it defined > \SpecialUsageIndex with it: > > \def\SpecialUsageIndex{\SpecialMacroIndex}. >
> 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.
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 >
First, there's a really valuable and important accessibility thread for us on the Blind Math mailing list. It's deeply rooted in real-world problems and solutions. Mainly it's Jonathan Godfrey's response to Brandon Bigg's query: Tutorial on Using RMarkdown? http://nfbnet.org/pipermail/blindmath_nfbnet.org/2022-January/010146.html
In tomorrow's (Thursday) TeX Hour I'll share my initial thoughts on an architecture for accessible typesetting. This will be a technical session, focused on having control over what happens whenever input text is added to TeX's horizontal list for the current paragraph. Last year a similar TeX Hour conversation led to the concept of a Portable TeX Document, so finger's
Happy New Year. May you and those around you be safe and happy.
When a year ago I started the weekly TeX Hour video meetings, I had ideas as to what would happen. I'm pleased to say that I paid some attention to what was going on around me, and that I was able to let go of many of my previous ideas. Experience, someone said, is knowledge you get just after you needed it!
