@HenriMenke Thanks! There was some confusion which is in my opinion related. I think what happens is that circuittikz redefines the to syntax (only) if some keywords are used. Among other things, paths can get broken into smaller pieces, which is good for arrows but not so good for closed cycles.
* wolfie ponders how many debianites it takes to screw in a lightbulb
<Viiru> wolfie: Somewhere around 600? One screw's the bulb, and the rest
flame him for doing it wrong.
<part> wolfie: is the bulb free software?
<Tv> Can we vote on whether to screw it or not?
@UlrikeFischer there is a lot of German tourists around here, but I am still shy to try to say a sentence to them. :)
@DavidCarlisle Looking at the raw logs, something is not quite right ... do you think the date information is actually worth having? (Or rather, are the lines containing dates useful?)
@DavidCarlisle Now I see the date lines appearing, I'm wondering if I got this right ... as it is, there is something amiss (data being duplicated), so I'll need to adjust again :(
@JosephWright well some are, some less so, but in the raw logs the (./foo.fd lines are on separate lines from the dates in ProvidesFile, but they got merged...
@DavidCarlisle OK, so I'll fix the formatting rather than strip the lines back out
@DavidCarlisle Probably this is due to some other 'tidy up' code that has never been down this path before: I can look for File at the start of lines and preserve the space, for a start
@DavidCarlisle Thinking I could do with a dedicated development PC now I'm compiling TL sources ;)
@JosephWright yes that's what I wrote in the report. If he wants a global definition he will have to define the commands differently (but I don't see why it should be necessary. If users define the currencies inside a group they get what they deserve ...).
@JosephWright so I'm out of a job then:-) (--no-clean is a useful option to Build if you want to speed things up, and cd Work/texk/web2c; make even more so
@JosephWright yes but sometimes (depending what filedates I just pulled from you:-) it gets out of sync (or I don't trust it) so I redo a full build just in case.
@DavidCarlisle Key point is though it should be faster than Travis-CI ... sounds good, particularly for these really tricky changes (which I still don't follow: strange errors I think from C)
@DavidCarlisle That one is done: just a question of getting the final patches into the engines. We could send a .diff to Karl for pdfTeX, put in a proper pull request for (u)pTeX and ...
I have a datatool question: how do I do DTLforeach to select just a subset of the database using a string comparison? There are examples of selection based on numerical tests, but not string tests.
@Ronen as always it's best to ask a question on the question site with a complete example (I could not start to guess what you mean by the above comment:-)
@AlanMunn should work too for not to complicated comparisions. There is also e.g. \DTLisSubString. But on the whole I try to avoid another set of comparision commands and stick to expl3 if possible.
@Ronen oh unless you mean you have <blank line> \parbox{\textwidth}{... in which case the line will be overfull as the box will be indented by \parindent unless it is in some environment such as center which does not indent.
Ah no, I'm trying to create underlines on a title page. I just wrapped \noindent into the function/method that creates the signature field with typed name under it
this question didn't have much of a mwe, but i guessed correctly and my comment solved the problem. however, the problem (an unwise % in a .bib file that bibtex can't handle) is something that might bite someone else. if there's a duplicate, i'd vote for closing, but i haven't found one. does anyone know of a good duplicate, or should i answer?
@UlrikeFischer -- good find. thanks. i think i will edit that answer to say that a % is passed on directly to (la)tex and can be catastrophic there. (the % was already added as an edit, per the comments.)
I have a problem with the package tools after an update of MiKTeX 2.9.6670 64 bit. See the following MWE in which I use the package auto-pst-pdf. While compiling, I'm getting this window:
After clicking Install, the end of the log-file looks like this:
MWE (TeXnicCenter LaTeX->PDF):
\do...
@egreg it was probably there two days ago, I updated tools to fix the array issue, and used the texlive 2018 l3build (to match travis) and it seems to have dropped the .tex from the zip file (it installs it locally)
@egreg @barbarabeeton then the math font should provide the means to build such a ligature. And if the math doesn't allow this, then ok one can as a work-around escape to a similar looking text font. But the default should be to use the math font for math.
@UlrikeFischer -- the math roman font (\symup) is intended to be used for single-letter variable names, as are all letter symbols in plane 1. (at least that was the intent when i fought for it with the unicode technical committee.)
@barbarabeeton well using the chars from normal latin plane would be okay too. But it would be imho a flaw if something so well known as a math function like \sin or \lim could not be typeset correctly with a math font alone. Using a text font feels like a work-around and like the logical thing to do.
@JosephWright @egreg @UlrikeFischer I just ran l3build ctan (after hiding all the test files) using the public tl2018 l3build an .tex gets put in the zip. I guess I'll resubmit to ctan.
@DavidCarlisle, I don't understand what recourse I have. \MakeUppercase{} is removing all formatting from the commands put in to it, and functions horrifically. Is there a more robust \begin{} version?
For example, if I change \uppercase{ to \MakeUppercase{ then the centering is lost, and the simple text contained inside it is no longer uppercased.
@Ronen you shouldn't be apply \MakeUppercase to \centering just apply it to the text. `\uppercase simply isn't suitable, you can use it in simple cases but not if anyone will need an accented letter in their name for example.
I understand that I need to include \MakeUppercase{#2} to uppercase that portion, but I don't understand why \MakeUppercase{\prevDegree{a}{b}{c}} won't uppercase the arguments
Or rather, won't uppercase the output of \prevDegree{...}
@Ronen If you need this you should use a font which has uppercase letters at the places of the lowercase letters. Some open type fonts have an option to do this, see e.g. tex.stackexchange.com/questions/370799/…
@Ronen I'm confused why do you want to uppercase the output of that command, all it does is uppercase #2 and pass #1 and #3 unchanged, so if you need to uppercase all three arguments what is for?
I happened upon an article that discusses `\expandafter` which I think will solve the issue, as it's a latex compiling order problem, I think.
In the title, "Bachelor of Science" needs to be uppercase, but elsewhere in the text it might be regular case. I would assume that "B.S." would be typed in by the user as an uppercase piece of text, but I realize it might not be wise to rely on the end user for that. #3 is a year, so there's no need to consider case.
So the user would input the name of their degree in the .tex, and the .cls would parse it and present it correctly, without the user learning to read what's in a .cls
@JosephWright it worked just now but clearly the version of of tools I sent last week was missing a file (I may have picked up a locally installed l3build, can't reconstruct now:-)
@JosephWright I must have seen the checkin log at the time as it came to mind as soon as I saw the question here. Oh well. (I also just deleted all the test files so it passed, an and then sanity checked by diffing against the last release)
@UlrikeFischer ' always has such a definition, even in plain tex
@DavidCarlisle Ah I see. I had forgotten that with mathcode "8000 this definition is used. Well this means that it is a rather bad idea of polyglossia to use ' as a shorthand.
@DavidCarlisle well there is an \ifmode in the code. But unicode-math is used and when latin is the main language and one use $f'$ one gets a loop. And when latin is an other language one gets error with ' in text.
@DavidCarlisle Well I'm always in two minds if one should try to correct polyglossia. Perhaps it would be better to look if latin.ldf of babel contains something problematic for xelatex and lualatex.
I have a problem with the package tools after an update of MiKTeX 2.9.6670 64 bit. See the following MWE in which I use the package auto-pst-pdf. While compiling, I'm getting this window:
After clicking Install, the end of the log-file looks like this:
MWE (TeXnicCenter LaTeX->PDF):
\do...
