« first day (4252 days earlier)      last day (690 days later) » 

5:36 AM
@UlrikeFischer I hope you like my review essay!
 
6:12 AM
@JosephWright ;-) I'm not sure about the mag and zero tests. I assume David added them for a reason and being conservative sounds safer. I'm not sure what you mean regarding the kernel hooks, I need to check what I did for dvips (it was some time ago but I tested which hook dvips needs)
 
@UlrikeFischer On the kernel hook, for dvips, I mean do we need \@kernel@before@begindocument { \__kernel_backend_first_shipout:n { ... } } - wouldn't just \__kernel_backend_first_shipout:n { ... } work
@UlrikeFischer If we do want to test \mag/0pt, I'd put it in common code in l3pdf and issue an error if they are wrong - it's unsupported and likely to give an erroneous PDF
@UlrikeFischer There's a reason I wrote a comment rather than pushing any code :)
 
6:50 AM
@JosephWright i will have to check but I think I wanted to be behind some code from the pdfmanagement.
@JosephWright I think one of the presentation classes (powerdot? ) use mag.
 
7:06 AM
@UlrikeFischer Ah, right: we should document that :)
@UlrikeFischer I'll look round
@UlrikeFischer My plan is to push a separate branch commit with a suggestion: as it's quite a modification of your PR, that seems the best way to go initially - we can cherry-pick if the plan looks good
 
7:21 AM
@JosephWright I'm happy with everything that gives me a \pdf_set_pagesize: for hyperref to use ...
 
@UlrikeFischer :)
 
@JosephWright but I should really check it that was the reason, perhaps I simply was overcautious in delaying.
 
7:33 AM
@UlrikeFischer @JosephWright the don't do anything if \mag is set translates to don't break platex By the time I tried to normalize this over the different back ends, the Japanese setup already had a lot of infrastructure around scaling and horizontal and vertical directions and we couldn't get anything to work in a compatible way other than bailing out and not doing anything in graphics and letting the platex macros handle it.
 
@UlrikeFischer Would be good to have a clear idea
@DavidCarlisle Ah, right: I guess I should look at that and see if they are still doing that
@DavidCarlisle There are all sorts of rubblings in the Japanese user community, but I think we will want to find a way to address this. I'll add to my to-do list
@DavidCarlisle We should be checking the engine then I guess, really
@DavidCarlisle If we can't fix the underlying issue, we should at least put the engine wrapper in such that it applies 'up front'
@DavidCarlisle, @UlrikeFischer I'll work on some code later - I think I can provide a plan :)
 
@JosephWright yes (like the \stockwidth test) it's clearly "wrong" but allowed me to get signoff on all the drivers (including a change to dvips) and from the platex maintainers, so everything worked same way, but with more central control and expl3 being loaded in the format simplifying timing issues, we don't necessarily need to make the same choices now.
 
@DavidCarlisle Indeed - what we do want I think is clear notes in the code and an idea of what is 'expected' of third parties
LaTeX2e <2022-06-01> patch level 2
 
@JosephWright same here
 
@DavidCarlisle :)
@DavidCarlisle I suspect the issue with pLaTeX comes from github.com/texjporg/jsclasses/blob/…: Google Translate gives me:
% In the standard document class, there was an option to specify the number of points in the body, but the number of points was only 10, 11 and 12, and different class option files were read for each. What's more, it wasn't very convenient because the fonts could be a little out of balance except for the standard 10 points. Here, 9 points, 21, 25, 30, 36, using the hand of increasing the font size to make the page smaller and expanding it overall with the | \ mag | primitive of \ TeX,
% 43 points, 12Q, 14Q can be specified.
@DavidCarlisle The way they do it is to set the real paper dimensions, then apply the \mag, but then they reset \papersize to the 'apparent' size. I'm pretty sure I can set up to handle the \mag correctly ...
 
7:53 AM
@JosephWright sounds good (I didn't have google translate so was relying on my natural abilities at reading Japanse:-)
 
@DavidCarlisle :)
@DavidCarlisle I'm going to do some tests, work out what is actually being put in the dvi, then make sure I can get to the right values from the data available
\documentclass[uplatex,papersize]{kiyou}
\makeatletter
\show\jsc@papersize@special
\showthe\paperwidth
\showthe\mag
@DavidCarlisle ^^^ A place to start
@DavidCarlisle I guess you were writing the code pre-eTeX? We can use e.g. \dimexpr\paperwidth/1000*\mag\relax (or probably the FPU) here
 
@JosephWright etex2 came out about the same time as 2e (how I came to write etex.sty) but we didn't use it for another decade, as lots of people ran old engines, and lots of tex sysems eg y&y never supported it
 
@DavidCarlisle Indeed - what I mean is that doing the 'reverse the \mag' work is easy with e-TeX but more tricky without it
 
@JosephWright well yes but that's not why it's not there, I did have the division implemented, but I broke platex and took it out....
 
@DavidCarlisle, @UlrikeFischer Think I have a few ideas that deserve a mail - need to do some day-job work, but expect something later (incl. \stock..., etc.)
@DavidCarlisle Hmm OK, clearly going to need a bit of work but I think I can recruit some Twitter followers for that :)
@DavidCarlisle, @UlrikeFischer I notice that there's no consideration of landscape ...
 
8:07 AM
@JosephWright landscape just swaps height/width after you know what size you want so doesn't affect this, I think
 
@DavidCarlisle Depends how you think things should look in a PDF: should landscape pages be rotated by the viewer or not
 
@JosephWright for (pdf)lscape I see that but for overall document size I don't think rotation comes in to it you are just setting the media box, "landscape" just means width>height
@JosephWright meanwhile: texlive.net/run?%5Cshowthelog
 
@DavidCarlisle Ah, cool - something we should likely ensure then :)
@DavidCarlisle :)
@DavidCarlisle So no more option clashes for us
 
8:25 AM
I think I had a hallucination ... that \documentclass[12pt]{article} spat an unused option warning from yesterday to today morning... I should sleep more. (Now it's all ok).
 
@Rmano If you were loading e.g. siunitx you'd have seen that - a bug we've now fixed in the new option handling
 
@JosephWright Ah, yes, siunitx is in my standard preamble ;-).
 
@JosephWright I added a summary of the above to gh
 
8:49 AM
@barbarabeeton I'm not so worried about my typing, I think it's more my style choices that are going to be a stumbling block if anything. 😅
 
9:02 AM
@barbarabeeton And for me as a "visual" person most of the time the diagrams and graphics are for my own benefit rather than the readers to make sure that I am saying the right thing. :þ
 
@JosephWright the mediabox of should reflect the real page size, so have a larger width in landscape. It should not try to fake it with some rotation. I just managed to stop dvips to do this. It breaks the orientation of annotations.
 
9:19 AM
@JosephWright Nice! The new output is now consistent with \ang
Talking about this ... is it by design that `angle-symbol-over-decimal` only works with `\ang` and not `\qty`?
\documentclass{article}
\usepackage{siunitx}

\begin{document}

\qty[angle-symbol-over-decimal]{10.7}{\arcsecond}
\ang[angle-symbol-over-decimal]{;;10.7}

\end{document}
 
 
1 hour later…
10:29 AM
@daleif regarding nameref and memoir: this looks quite messy. memfixh seems to test for the wrong command (\NR@sectm@m instead of \NRorg@M@sect) and other stuff looks quite odd too. Imho this should cleaned up. Side remark: if you define \NR@nopatch@sectioning nameref will no longer patch the sectioning commands and memoir could setup \@currentlabelname directly.
 
@UlrikeFischer Hmm, so why is that not required to be 'known' to the backend code?
@samcarter Er, broadly: it's really for arc-style angles used in astronomy (it used to be called astroang in v1)
@DavidCarlisle Thanks
 
@JosephWright sorry what should be known?
 
@UlrikeFischer Because there are two ways one might want a landscape page: to show in a viewer as portrait-with-content-rotated, or with the entire page rotated in the view
@UlrikeFischer One approach 'really' swaps the width and height, the other doesn't
@UlrikeFischer I'm surprised that the backend doesn't have to know the landscape setting to interchange \pageheight and \pagewidth if required
 
@JosephWright woops, used the wrong GH-account on your issue (that's my work-account)
 
@Skillmon Want me to zap?
 
10:41 AM
@JosephWright if you set up a landscape layout (for all pages) then the mediabox should reflect that. You simply set width=27cm and height = 20cm. There is no rotation involved, it is only a different layout. What dvips made instead was to setup a portrait mediabox, to rotate the content and to tell the pdf viewer to rotate in the other direction.
That was perhaps needed to be able to print, but today printer driver can handle such layouts and one should make it more complicated than needed in the pdf.
 
@JosephWright yes, probably better. Should I then readd the comments under my "reall" account?
(which I could do later today when I'm back home)
 
@Skillmon Done
 
@JosephWright thanks
 
@JosephWright yes, but in astronomy, arcs are basically used like a length unit, so it would be nice to use \qty{10.7}{\arcsecond} instead of having to count empty ; in \arc
 
@samcarter I'll check, but I think v1 and v2 only ever applied this to to arc format as it's basically a 'feature' of arcs
 
10:51 AM
@JosephWright yes, it never worked for \SI, but is there are reason to not make it work with \qty?
 
@samcarter Arc angles have special implementation to allow astronomy-style formatting, which doesn't apply to general \qty ones - I'd have to allow it to apply to all units, there would be an performance impact and some complex coding - really feels borderline to me as this is something that only applies to arcs
 
@JosephWright ah, ok. Thanks for the explanations!
 
@UlrikeFischer Thanks - I'd misunderstood some code in a Japanese class
 
@JosephWright perhaps they have some old code too. But you can check this issue which shows why "cheating" with rotation is a problem: github.com/latex3/pdfresources/issues/24
 
12:02 PM
Hi all,
I have a problem with in-text citations using biblatex. I want the in-text citations to show all authors when the number of authors are two or less, otherwise show the first author and use `et. al.
From the biblatex user manual , I assume the options are `mincitenames=2` and `maxcitenames=21, but it doesn't seem to work. There's this [post](https://tex.stackexchange.com/questions/121625/biblatex-modify-maxcitenames-to-work-in-three-cases) that advises to use only `maxcitenames=2`, but that doesn't work either.
My options are
\usepackage[
style=authoryear-comp,
maxcitenames=2, mincitenames=1,
sorting=nyt, terseinits=true,
isbn=false, dashed=false]{biblatex}
This answer shows the output I want.
 
@RogUE "that doesn't work" is not sensible a problem description. You should always make a complete example. Typically, if biblatex shows more authors than you want it is due to the uniquelist setting. So check if you have another entry with the same or similar authors.
2
 
@UlrikeFischer That must be it. I have added uniquelist=false and it is working as expected. Thanks @UlrikeFischer
 
 
1 hour later…
1:20 PM
user image
2
Nearing Magdeburg ...
 
@UlrikeFischer If you happen to come by a Sparkasse, have a look at their Geldottomaten
 
1:34 PM
@UlrikeFischer And when talking to a local keep in mind that "a" in Magdeburg is pronounced (very) short.
 
^^^ this kerning hurts!
 
yo'
@samcarter ooh keming!
 
@yo' :)
 
 
1 hour later…
3:02 PM
@DavidCarlisle regarding the coloneq issue, what exactly was the haft fix in newtxmath? Currently I have the list in mathtools generate the same symbols as newtxmath but it seemed that also had and error?
ohh, we're missing -: (then strange that :- does not exist)
 
@daleif I sent an email to Michael sharp asking about change to coloneq (but not Coloneq) between txfonts and newtx. No reply yet. I think correct version is coloneq is :=Coloneqis ::=` (same as unicode-math) then define qq versions as same thing for legacy compatibility but that is not what newtxmath does for Coloneq just coloneq
 
Do -: and :- really mean something?
 
@mickep EXCESS
 
@DavidCarlisle Ohhh
 
@DavidCarlisle but isn't -: completely missing?
 
3:10 PM
@daleif :- you mean, yes that is not in Unicode
 
@DavidCarlisle no, you mentioned -: (U+2239) in github.com/wspr/unicode-math/issues/590, that does not seem to be implemented in newtxmath (it was just for completeness)
Perhaps I should get ready to go hear some German noise....
 
@DavidCarlisle And :: means "two colons". :)
 
@daleif ah Ok yes, but despite my bold comment above I have no idea what -: is used for, so it being missing isn't much of a loss
 
And so basically switch \Coloneqq and \Coloneq such that qq indicates two colons. That would make more sense. Hmm, then we probably need and option to restore. Is there any way to list the macro name mappings that unicode-math uses?
Ahh, no that is not the naming convention, capital letter means :: the qq are just legacy
Are ::- in unicode?
 
@daleif there is the tex file in unicode-math but I use github.com/w3c/xml-entities/blob/gh-pages/unicode.xml look for <mathlatex set="unicode-math">\dotsminusdots</mathlatex>
@daleif no
@daleif exactly
 
3:23 PM
Thanks. So there is dashcolon, but no colondash. How unsymmetric. I wonder if dashcolon is used in logic?
Might be an idea then to list: these are defined in unicode and named as such. These are additional symbols with no unicode equivalent ...
 
3:53 PM
@daleif The example here access.uoa.gr/mathbraille/index.php/en/math-symbols2/… looks strange to me.
(I sometimes wonder where all these odd symbols come from. I never see them in the articles I read.)
Then all of a sudden some binary symbol is used as an index... tex.stackexchange.com/q/648571/52406. Well well.
 
4:51 PM
Oddly enough, TeX didn't make it on the list of languages used by those "Learning to Code". :) survey.stackoverflow.co/2022/…
 
5:28 PM
@AlanMunn :)
 
@AlanMunn But lua is there.
 
@mickep So it is, if you hunt
 
 
1 hour later…
6:40 PM
@Plergux -- Well I always value visual examples to aid clarity and understanding. Both prose and visual backup are necessary, really. Can lead to instant recognition of a problem if something is out of kilter.
 
@AlanMunn That's clearly the selection bias from showing the banner only on SO and not on the other sites of the network. So of course a language with its own site will be under represented :P
 
@samcarter x:)
 
@JosephWright ! LaTeX3 Error: No property given in definition of key 'toplevel'. ?
 
@DavidCarlisle ???
 
@JosephWright you want a mwe? I thought my question was clear:-)
\documentclass{article}

\usepackage[noprint,hyperref=false,multicol]{doc}
\newcommand\tst[1]{\typeout{\string#1: \meaning#1}}
\begin{document}

\makeatletter
\typeout{===}
\tst\ifdoc@noprint
\tst\ifdoc@hyperref
\tst\ifdoc@multicol
\tst\ifdoc@debugshow
\tst\doc@idxtype

\DeclareKeys[doc]{toplevel=true,idxtype=abc,debugshow}
\typeout{===}
\tst\ifdoc@noprint
\tst\ifdoc@hyperref
\tst\ifdoc@multicol
\tst\ifdoc@debugshow
\tst\doc@idxtype

\end{document}
 
6:47 PM
@yo' -- That's not kerning; that's a collision.
 
@JosephWright ah you fixed it
@JosephWright clearly explaining to a duck helps debugging
 
@barbarabeeton Very true. And if you can make a point with a little bit of humour it helps all the better. :þ ualberta.ca/arts/faculty-news/2019/october/…
 
@DavidCarlisle/@barbarabeeton: There is in unicode lowercase greek sansserif bold and lowercase greek sansserif bold italic, but not lowercase greek sansserif or lowercase greek sansserif italic. Do you happen to know why?
 
@mickep ITS NOT MY FAULT I know:-)
 
@DavidCarlisle Hehe
 
6:57 PM
@mickep hang on, link coming up....
 
(Not that I long after them, given how the existing sans alphabets often look.)
 
@daleif -- eqq in other contexts means a "two-line equal"; as in \eqqplus \pluseqq, approxeqq, etc. And the uppercase letter (first seen in DEK naming) doubles that component of a symbol. I'd prefer to stick to that interpretation. But it does leave a problem with "dash-colon" and "colon-dash", for which I don't know a meaning.
 
@barbarabeeton There is an example on access.uoa.gr/mathbraille/index.php/en/math-symbols2/…. Something something with arithmetic sequences. But I don't know if it is "for real".
 
@mickep we have been pleading for this for 20 years....
 
@Plergux -- Oh, that's lovely!!! I've got quite a list of people who need to see it!
 
7:05 PM
I blame @barbarabeeton
 
@DavidCarlisle Funny coincidence: I browsed Courant-Hilbert the other day and noticed the sans serif Gamma. Well, it seems difficult. And still a bit funny that the bold versions are there.
 
@mickep -- I really don't know. They were trying hard to restrict the "math alphanumerics" to two plane-1 blocks, so they left out things that weren't explicitly requested, and those weren't on the STIX list. But they also left out things that were explicitly requested, including callligraphic separate from script. I no longer have access to the paper documentation I used to compile the STIX list, but the origins of what's in the list are in an accessible table.
 
@barbarabeeton Yes, stixtwo is one of the few that has both calligraphic and script variants. Cambria and Lucida also have them. I wonder if there were more.
 
@mickep -- Thanks. I wasn't aware of that, and am not enough of a mathematician to know independently what it might mean. (I had to take it on faith that what the other STIPub organizations requested were legit. That was my remit, and there are a couple of items that I really do know are questionable, but I had to include them anyhow.)
@DavidCarlisle -- Well, Murray Sargent, I believe, is still the UTC rep from Microsoft, so twist his arm.
 
@barbarabeeton It is added as sstyXX (of course different numbers in different fonts, and also different version added as special in different fonts... _)
 
7:18 PM
@mickep -- I was able to find a published document where script and calligraphic were both used, with clearly defined different meanings. It still took years for Unicode to accept the concept.
 
It is not that sans greek is really needed, but given that they add all kind of emojis and so makes me wonder a bit...
@barbarabeeton Hehe, amazing.
 
@mickep -- There was a document promulgated by the U.S. National Bureau of Standards (or its successor, NIST) on proper scientific typography that specified a sans cap Theta for something. So one letter, UTC included the whole alphabet. Unfortunately, that NIST document has been superseded, and I can't find the original, which I did use for the STIX compilation.
 
@barbarabeeton Thanks, always interesting to hear about how things went.
 
@mickep -- Cambria and Lucida were both significantly influenced by the STIX collection. (I was supposed to consult on the development of Cambria, but unfortunately, became ill and was out of commission as far as that project was concerned for the duration.)
 
@barbarabeeton I made quite a few of these small comics when they shared the data with me :þ
 
8:04 PM
@DavidCarlisle Er, you know you are trying to set keys in the defining phase ...
@DavidCarlisle Did you mean \SetKeys?
 
8:57 PM
@JosephWright yes, but I noticed as soon as I pasted it here:-)
 
@DavidCarlisle :)
0
Q: Using \Makelowercase in includegraphics

Dylan RussellI feel like this should be very simple to do but even using multiple other SE solutions I have not been able to figure it out. I would like to pass an argument like Evans1963 to a command that I have defined: \newcommand{\placefigure}[1]{ \begin{wrapfigure}{O}{0.47\textwidth} \centeri...

Looks like a job for ... expl3 ...
 
9:14 PM
@JosephWright \lowercase{includegraphics[width=0.45\textwidth]{#1_results}} :-)
 
9:39 PM
@JosephWright grr I must have misread it, I thought it showed passing tests but ! LaTeX Error: File multicol.sty' not found.` I guess I should use mulicol=false...
 

« first day (4252 days earlier)      last day (690 days later) »