@WillRobertson did you manage to send a csname in an announcement?

quack

@PauloCereda Happy quacking to you!

@UlrikeFischer The uppercase multiscript thing is fixed now. Sadly ConTeXt feature normalization does not seem to allow case-sensitive features, so table names are consistently mapped to lowercase now.

@CarLaTeX ooh another duck

@PauloCereda Hi from Prague's Regional Czech Scouting Convention :)

@yo' Yay!

@yo' It's a lot of fun!

@PauloCereda a lot of people in scout uniforms and a lot of talking

@yo' ooh

@yo' how much people are there?

> Alan Turing's Doctorate & Knighthood Medal Recovered 36 Years After Theft

@PauloCereda probably a bit under a 100. The next one I'll be at will be the National Convention in 2 months, that will be between 400 and 500 people

@yo' oh :)

[squirrel meeting]

Chief Squirrel: everyone, I suspect someone among us is an infiltrator
Owl: hoo
Chief Squirrel: (solemnly) that’s what we’re trying to find out Owen

@Rmano ^^ squirrel jokes :)

@PauloCereda :):):)

> "Documentation is a love letter that you write to your future self." - Damian Conway

@DavidCarlisle ^^ uh-oh

@PauloCereda it's OK for you, ducks have no future, they get eaten

@DavidCarlisle ducks have a future. And it lies within honey mustard.

@Skillmonlikestopanswers.xyz I'm sure @PauloCereda will be relieved to hear that.

@MarcelKrüger I saw the commit yesterday. Imho case insensitive is ok as long it is consequently done. Can the ISO tags be case insensitive too? I would find it more logical to use Beng instead of being.

@DavidCarlisle aiming for 555555?

@UlrikeFischer Done

@MarcelKrüger thanks. I think it will make the documentation clearer if I can use different notation for ISO and script tags. I will work on it in the afternoon. Regarding the AAT-ligatures. Could this happen for kerning too? I got a question by mail why a helvetica clone doesn't use kernings in lualatex but hadn't time yet to look more closely.

@UlrikeFischer yes you have to manage downvotes carefully. I managed 333333 and 444444 :-)

@DavidCarlisle how can one manage downvotes?? I never get them when I need them.

@UlrikeFischer well I had one the other day that pushed me off the 5-0 cycle so I made sure I rep capped that day, conversely just before I got 444444 I had a lucky downvote so I didn't answer any more questions that day :-)

@DavidCarlisle there's always /cough voting /cough squad /cough but I didn't say anything

@yo' I'm sure you meant to say. "I'm sure your answers are always worthy of sufficient rep to reach rep cap" ?

@DavidCarlisle or, we know which your answers we don't like and we know when midnight is :-)

@yo' the other day I spent an embarrassingly long time tracking down a bug in xurl and finally reporting a bug upstream and picked up at most a couple of votes, if I need to reach rep cap, I follow egreg's advice and just answer a few % at end of line questions. Voting patterns are weird, but fairly predictable...

@DavidCarlisle btw, you are responsible for amstex to some extent now, right?

@yo' amsmath yes, amstex is on autopilot

@yo' an amstex issue come up?

@DavidCarlisle Looks like we have a plan for biblatex, we should seriously think about \MakeUppercase

@JosephWright \let\makeUppercase\text_whatever and make textcase package a noop?

@JosephWright I pinged Frank but can you look at setspace issue 3 and confirm I'm not going mad, and the package is fundamentally broken:)

@DavidCarlisle hm perhaps the comment should read "only redefine \@setsize if not under 2e", the following comment about 2.09 packages would then make more sense.

@UlrikeFischer Yes I wondered if that's what Robin meant except that then there is no code anywhere that scales parskip or footins in 2e as far as I can see. If you use say parskip package then \doublespace, baselineskip increases but parskip doesn't which doesn't match the documentation at the top, but I dare not change it probably thousands of thesis files using such a setting

@DavidCarlisle yeah, I meant amsart actually. Have you seen msc2020.org ? I suppose once this is officially finished you'll pull it in?

@yo' no the classes are still under AMS control but it is on their radar (came up in an email thread with them the other day). I guess unlike other bug fixes they may actually distribute a public version with that since they maintain msc2020 and will presumably be telling authors to use it... If in doubt blame @barbarabeeton (retiring isn't a reason to avoid blame)

@UlrikeFischer the comments in that package are quite funny to read these days all about worrying about differences between tex2 and tex3 and between 2.09 and 2e.

Good afternoon @barbarabeeton :-)

@DavidCarlisle l3setspace?

@DavidCarlisle ok thanks. It appeared in a ticket here, so I'm just checking who's in charge. Thanks once more!

@UlrikeFischer might be considered typesetting so off limits:-)

@DavidCarlisle if you put it in the rf-tex repo ...

@yo' I just checked: the information I have that they are planning on adding msc2020 support was on an email just to me and Barbara so not anything you can really quote but it was from a reliable source at the AMS.

@DavidCarlisle ok thanks.

@yo' -- I have learned from a reliable source that the AMS document classes are being worked on. Indeed, if they don't get an updated version out, there will be serious complaints from authors. However, the report didn't say whether the public update will meet the TeX Live 2020 cutoff. (Regardless of @DavidCarlisle's contention, not my problem.)

@barbarabeeton yeah. If it's out by the TL release, but it's out by time we launch TL2020 in Overleaf, we can still implement it.

@yo' -- The necessary change for msc2020 is really trivial. The last public update put in only the msc2010 addition. So real fixes haven't been made for more than ten years. (I complained officially, but apparently to no avail. Changes are allowed to be made by only one person, and other projects have been deemed "more important".)

@UlrikeFischer Yes, for pure AAT fonts, all font features including kerning and ligatures will be ignored in LuaLaTeX. But I think this should only affect the Helvetica version shipped on Mac OS, I don't think that any other variant would rely purely on AAT.

@MarcelKrüger I will forward you the mail.

@DavidCarlisle I'll mail

@JosephWright Remember that \input{...} thing Karl mailed about? Is that still up?

@PhelypeOleinik I remember, it's hard

@JosephWright It was, indeed :-)

@PhelypeOleinik There's not really any code we can copy/paste, so it's possibly beyond my WEB skills ;)

@JosephWright After that LuaTeX issue with braces in file names I went to play with WEB a bit. I think I got it right...

@PhelypeOleinik Ah, cool!

@PhelypeOleinik I'll look forward to it: would be great if we can sort for TL'20

@JosephWright Should I write Karl directly or to the team list first?

@PhelypeOleinik Karl: it was a request to me not really to the team

@PhelypeOleinik Did you cover \openin and \openout?

@JosephWright Okay

@JosephWright Hm, yes, I changed scan_file_name, not start_input

@JosephWright Though LuaTeX seems to do otherwise

@JosephWright Wanna see it first?

@PhelypeOleinik Sure, would be good

@JosephWright Sent

@PhelypeOleinik I could build it here as well if you like

@DavidCarlisle regarding engine updates: it doesn't looks as if the \openin fix is in already. I tried with todays experimental.

@UlrikeFischer I have the luatex svn here but I'm mostly set up to build off texlive-source now so I can't easily check until it is pushed to there

@DavidCarlisle it was just commited: github.com/TeX-Live/luatex/commit/…

@UlrikeFischer oh ooo git pull ... make coming up....

@UlrikeFischer ah but not yet to github.com/TeX-Live/texlive-source

@DavidCarlisle no but I guess it will happen sooner or later now.

@UlrikeFischer yes it's usually not far behind

@UlrikeFischer I guess I should draft something for ltnews31

@DavidCarlisle Sure! I forwarded you the email

@PhelypeOleinik thanks