Joseph Wright comments

Results 1009 comments of


                                            Joseph Wright

argument of type v errors if the argument contains a tab

Looking back here: don't we simply need to add tab to `\dospecials`?

argument of type v errors if the argument contains a tab

@muzimuzhi Thanks - I think that confirms that this simply needs doing in `\dospecials` - one for the June 2025 LaTeX2e release.

argument of type v errors if the argument contains a tab

Fixed at the 2e end

undefined page references in l3backend-code and l3draw-code

The aim of having the `-code` file here was to look at having a cleaner split for docs: one for the API, one for the implementation. Most of the time...

undefined page references in l3backend-code and l3draw-code

Well it is to some extent this was intended as an experiment in how best to document the code - there is work to do in developing best practice. So...

undefined page references in l3backend-code and l3draw-code

There seems to be a consensus so I will make a change: as I said, one reason for the difference here was to allow exploration of what works for people.

undefined page references in l3backend-code and l3draw-code

> A further request: except when this is not feasible, please provide .pdf versions of _all_ .dtx, etc., files (including those that are "under development"). Not sure what you mean...

undefined page references in l3backend-code and l3draw-code

I wonder how we want to name the outputs here (and more widely). For `l3kernel`, we have `interface3` and `source3`, so an API doc and an API + code doc...

undefined page references in l3backend-code and l3draw-code

[Aside: for a document-level package like `siunitx`, `XXX` is the user docs, so `XXX-api` and `XXX-code`?]

undefined page references in l3backend-code and l3draw-code

On `l3draw`, there's quite a bit of setup in the 'user' `.dtx`: how do we want to make this available to the `-code` file? Split it out, copy-paste, something else?