Just like this guy's, the color of my stove's flames were affected by the humidifier as well.
Why does this happen?
Is it a good thing or a bad thing ?
@JosephWright something doesn't work. If I do something like -eluatex53 it compiles but it still uses the normal luatex. (but complains that is can't find a luatex53 log). What is the internal call to luatex with this option?
@JosephWright saving works fine and uses luatex53, but checking doesn't work. l3build check -eluatex53 aaaaa-luakern uses the normal luatex and at the end complains:
FC: Kann .\BUILD\TEST\AAAAA-LUAKERN.LUATEX53.LOG nicht öffnen - Datei oder Ordner nicht vorhanden
--> failed
Check failed with difference files
- ./build/test/aaaaa-luakern.luatex53.fc
I've got a pdf that was created as a standalone tikz picture. Nothing complicated: a few circles and arrows and letters. I put this pdf inside a tikz node as \draw (0,-1) node[draw, dashed]{\includegraphics{fig.pdf}}, and surprisingly the dashed style of the node got transferred to the lines inside the pdf. Any ideas how I can prevent this beyond rasterizing my image? My google-fu is failing me.
I even tried using a scope to protect the image but scopes don't seem to work inside nodes...
@JosephWright I wouldn't mind to declare the engines explicitly in the build lua. E.g. something like engine["luatex53"]["latex"] = "luatex53 --fmt=lualatex53". This would be perhaps easier than trying to build the call with string matching everything.
@JosephWright even for the standard cases it would perhaps make live easier to have an explicit list. I at leasing I'm getting a bit lost currently about the real calls in all the ifthen-cases.
@JosephWright you know more than me about the variations already in use. imho either engines["luatex53"]["latex"] or formats["latex"]["luatex53"] depending on which is easier to traverse for you. context could fit in as engines["luatex"]["context"].
@DavidCarlisle ;-). But without the font it is difficult to test if coloring really doesn't work (after all I managed to color the cow font ... tex.stackexchange.com/a/387069/2388). But the main problem with luaotfload is currently that Hans "reshuffled" a lot of code and now deva is broken again and I guess it is a luaotfload problem, not of the fontloader ;-(.
@DavidCarlisle but perhaps you could also blame @JosephWright. pgfopts is his package ...
@DavidCarlisle @JosephWright Regarding the \zap@space issue, what if another space-stripping mechanism were used? Perhaps something like Joseph's code here that would only remove spaces outside braces and still preserve them.
@DavidCarlisle @JosephWright I think it might work, as the space stripping would (supposedly) be the same outside the braces, as the existing code expects it to be (unless I'm missing something).
@PhelypeOleinik it's fairly easy to make it safe but the problem is that there are approximatelly 100563 packages on ctan that patch that code and changing any of it without breaking any of them is proving a challenge.
@PhelypeOleinik braces fail with an error but spaces outside braces are also a problem if you want bb= 0 0 100 100 to work, the code currently checked in to github essentially ignore anything after = when doing the test for unused global arguments, which works quite well for the standard classes but has some "surprising" effects on the option handler in the koma classes, so I'm going to have to adjust it again.
@PhelypeOleinik and if you don't remove spaces at all things are a lot simpler but "accidental" but commonly used options like a4 paper and 12 pt stop working.
@DavidCarlisle But this would stop working at user-level, nothing that fixing the option name doesn't solve, right? From what I understood the actual problem is when packages start to break...
@PhelypeOleinik yes but that is the worst sort of failure. Fixing a package option handler can if necessary be done by getting the package updated but if I break a few thousand end user documents in arxiv for example they'd probably never update tex again
I have a problem with breaking lines in equation environment, can't really omit the text. I tried using \mbox and \parbox but they don't really give the effect I'm looking for.
example:
\documentclass[12 pt, leqno]{article}
\usepackage{amssymb, amsmath, multicol, titlesec, amsthm}
\begin{docum...
Sorry, this may be very easy question but I didn't get. When I use product symbol, I want to write c(as a cardinal product) in the lower suffix. I am using following command.
\documentclass{12 pt}{article}
\begin{document}
$\prod_{i = 1}^{n}_{c} A_{i}$
\end{document}
@PhelypeOleinik well that as well, especially option handling which affects every package. contemplating what all the off-ctan university thesis classes do doesn't encourage "brave" change in this area...
Just like this guy's, the color of my stove's flames were affected by the humidifier as well.
Why does this happen?
Is it a good thing or a bad thing ?
Sorry, this may be very easy question but I didn't get. When I use product symbol, I want to write c(as a cardinal product) in the lower suffix. I am using following command.
\documentclass{12 pt}{article}
\begin{document}
$\prod_{i = 1}^{n}_{c} A_{i}$
\end{document}
