Reputation
45,670
Next tag badge:
311/100 score
16/20 answers
Badges
5 129 183
Newest
 Good Answer
Impact
~3.2m people reached

12h
answered How to put a bar on top of a hat
12h
comment Callback to be run at the end of the job
There's no reasonable way to process the dvi files created by LuaTeX, right? I'm not sure if the output-agnostic requirement is all that necessary. But not running in draft mode is more likely a feature not a bug for that, so doesn't help in this case :)
22h
comment How to get subs/sups for figures but not letters?
Of course. I wrote it in my answer already: \fakesuperscript. There's an unfortunate typo in the documentation, though. The first sentence of section 2 should read "The OLD commands are defined in starred form (e.g., \textsubscript*) for cases where the new commands are not appropriate.".
23h
answered How to get subs/sups for figures but not letters?
23h
comment Pgfplots and ClassicThesis: two plots side-by-side
@Alenanno — Oh sure, you could cram them in. But then it looks more crammed in :) The example I chose is for a particular sparse plot as well. As with many decision in typography, there's no definite wrong or wrong — just competing design decision.
23h
comment Pgfplots and ClassicThesis: two plots side-by-side
@Alenanno — sure, I don't think you can have a rigid rule here. See my example below for something that I don't think is typographically ugly :)
23h
answered Pgfplots and ClassicThesis: two plots side-by-side
1d
comment Pgfplots and ClassicThesis: two plots side-by-side
@Alenanno — I mildly disagree when it comes to figures and tables. The function of a small linewidth is better readability — this isn't necessary for two graphs stacked side-by-side. In addition, the overall text becomes easier to read because each page is more dense — there's less page flipping when inspecting the figures.
1d
comment Pgfplots and ClassicThesis: two plots side-by-side
This is almost exactly that I did in my thesis, too. One remark: I prefer having the caption outside the wide environment.
1d
comment l3doc adds unwanted backslash in margin box of {function}
{macro} is basically inherited from ltxdoc with a few bells and whistles to interface to {function} — i.e., it's used to document the actual code definition of the function. There's no technical requirement to use expl3-style functions — it just ignores any formatting niceties in that case. As Joseph is fond of saying, l3doc needs an overhaul; it's really only designed for one thing: documenting expl3 and friends.
2d
comment Issue with \xrightarrow
@barbarabeeton — actually I don't really see why unicode-math needs to reimplement amsmath whenever something doesn't work; it would preferable to fix amsmath instead :) Presumably the problem would go away if U+23AF (horizontal line extender) were being used directly without the need to "back up" as in @egreg's answer below.
Feb
9
answered Followup on \def@
Feb
5
comment Modifying fraction macro for in-line text and exponents
Nice use of \footnotesize, I think we could call these "only-partially-vulgar" fractions :)
Feb
5
comment Does XeLaTeX in TeX Live 2015 force unicode quotation marks?
Have you updated to the very latest version of fontspec? There was a bug, quickly corrected, in the second-to-last release.
Feb
4
awarded  Good Answer
Feb
4
comment Make entire equation sans-serif
Why are you trying to make the symbols sans serif? It might be better to use a sans serif math font instead.
Feb
4
comment New version of fontspec gives WordSpace error
Thanks egreg. If you really wanted to work around the new restriction, I guess it would work to write \ExplSyntaxOn\__fontspec_keys_define_code:nnn {fontspec-addfeatures} {WordSpace} {}\ExplSyntaxOff after loading fontspec.
Feb
4
comment New version of fontspec gives WordSpace error
Apologies for the oversight with the release notes.
Feb
1
revised LuaLaTeX and mathspec
added 135 characters in body
Feb
1
answered LuaLaTeX and mathspec