Joseph Wright
Joseph Wright
> > [Aside: for a document-level package like `siunitx`, `XXX` is the user docs, so `XXX-api` and `XXX-code`?] > > I would stick with either just XXX.pdf or XXX-doc.pdf for...
> Also that, in order to make sense, this last often needs to contain "user-level" information and "api information" and etc., etc. That is to say, all that is necessary...
Of course, I will sort whatever people feel is best practice ...
Back with the issue itself, the one `??` I can find in `l3backend` is where we create `color.sc`, which is documented for use in the PostScript workflow but otherwise undefined....
> @josephwright I'm not looking at the dev version but in my l3backend-code.pdf from texlive, I've got a dozen or more ??'s. For example `\l_graphics_search_ext_seq`, `\@makecol@hook`, etc. True. These are...
> In the case of l3backend, I must admit I'm confused why there are page references at all. There is no associated user/API documentation, so shouldn't all commands be in...
I think `l3backend` is now sorted - I could do with thoughts on `l3draw`.
I'd say we need (as a community) to be making these kind of moves: see what we did with the kernel to shift to UTF-8 but leave a way 'out'....
> BCP-47 would be great if there were an interface we as package maintainers could use. At the moment we have to piece together `babel` and `polyglossia` interfaces and sometimes...
I've just realised this is a bit more tricky than I originally realised, at least for the 'documented elsewhere' cases. They _do_ work already in `source2e`, so we need to...