@DavidCarlisle I never saw him (but I wasn't there very often). I also mailed him about some xcolor bug but never got an answer. The denic registration shows an address so one could try a real letter.
@cfr Thanks for the insight about Arch, I might install it in a test machine for fun. :) I am overclocking my iMac at the moment, so I will be able to have lots of virtual machines. :)
@UlrikeFischer sigh that's probably my fault. I regretted later making color pass things round using the driver specific \special strings rather than a unified format as used for input. It saved a bit of runtime but complicates pretty much everything else
@UlrikeFischer of course it's even more dubious to patch that in color.cfg, color.cfg is all about defaulting the back end driver option so adding code to define a luatex back end and selecting it is almost reasonable, but patching internal package commands a lot less so.
@DavidCarlisle Should I try to contact him by letter and offer him that the latex team takes over in case he no longer wants to maintain the package? (More work for you if he accepts ... )
@UlrikeFischer well I just asked (by email to tex@) if he hasn't time could he let us update it now just for luatex (rather than take over) but if you could do something that would be good, thanks
@egreg sigh. I miss all the 9 at the start of the number. It will take me ages to get them back. Perhaps I should make a feature request to show the number in another base. base22 looks ok: 98H1.
@daleif @barbarabeeton amsbook does \uppercase\@xp{\chaptername}\enspace\thechapter}\uppercase isn't going to work here: needs to be \MakeUppercase (or textcase version to avoid math)
@DavidCarlisle Probably we'll need to write a proper LuaTeX driver for hyperref (mechanically at first). Did you notice some of HO's other packages also have driver code?
@JosephWright not sure I have much more time in next day or so, so I'd be tempted to push out what's there to ctan (as @UlrikeFischer hinted a miktex update is imminent) and then clean up the rest via normal updates, but I'm happy to let you have a pass over it first if you wish
-- i've made a simpler file using amsart (which also applies automatic uppercasing). the complaint i get for that is ! Package inputenc Error: Keyboard character used is undefined (inputenc) in inputencoding `utf8'.
@DavidCarlisle -- i'm looking into the uppercasing, but most of the uppercased elements use \uppercasenonmath and that should be doing the right thing, i think.
@JosephWright you'd get more users if it worked with pdftex:-) meanwhile pointlessly waiting for election results (although the conservatives not getting all three seats is less likely that Leicester winning the league)
@DavidCarlisle -- and for me, that comes out correctly all uppercase. the character that disappears (in running heads -- had to extend the example) is áº. (hmmm. that seems to have been modified when i cut and pasted. i'm using emacs with mule utf-8 encoding.)
@daleif -- okay -- \uppercasenonmath simply disappears; \uppercase fails to uppercase the hooked u and o; \MakeUppercase does the right thing. before suggesting anything, will have to test to see what happens with math of various sorts. thanks.
@barbarabeeton if you want math to survive you need MakeTextUppercase from textcase (amsbook already looks for that and changes some definitions if it is there)
@DavidCarlisle -- i've discovered another problem in my cutting-and-pasting. the mule-utf-8 emacs file encoding seems to not work properly; but the "ordinary" utf-8 apparently does. more to investigate ... trying again with corrected files.
@DavidCarlisle my pleasure. Perhaps you could ask Uwe Kern to allow to set options like "table" and load colors after the package -- this would reduce the option clash danger.
Hello, I am rusty on my LaTeX (haven't needed to use it in awhile). I know there was a package that would upload code by calling the script python.py or matlab.m. What package is that again?
@dustin ??? what do you mean by upload here? if you just want to typeset code sections listings or minted are usual choices if you want syntax highlighting or verbatim if not
@DavidCarlisle I think I was able to do something like \include{name.py} and the script would be in LaTeX without copying an pasting. Been working in industry and not academia so I have forgotten so much.
@dustin I was, as I said, worked fine, filled in in a window like the one Joseph showed. Just added a new processing command and filled in hose options
@Canageek -- if you're lucky, the conflict was reported while you're reading in a package. then you only have to look at the packages loaded earlier. best to check what's been read in by what's in the log -- lots of packages load others ... and the log reports them all, as well as where they were loaded from.
@Canageek -- well, that's a bit of bad luck. are you, by any chance, a chemist? \latin is found in chemmacros.sty and chemstyle.sty. (also in liturg.sty, but i think that's unlikely.) grep is a good friend.
@Canageek -- if you can figure out how the different instances of \latin are defined, you can decide which one is likely to be necessary, then load that package last, and before you do, \let\latin\relax. (if you're lucky, they'll be defined the same, so letting the first one \relax would be entirely harmless.) good luck.
@DavidCarlisle You define the glossary terms before the start of the document, so you can use abbeviations. I think I'll just stop using that, it was a pain anyway.
@Canageek you can always adjust the timing but here the macro is so simple, it's just \ensuremath {{}^{\prime }} you could just define it in advance if you need it
Hey @JosephWright If you drop in, is there a reason that achemso makes it so hyperref no longer generates pdf bookmarks? I find that really useful when editing, as I can jump to the section of the paper I want to work on. Is there some way to turn it back on?
(I'll ask a question and generate a MWE after lunch if I don't hear back, not that you need the upvotes)