TeX, LaTeX and Friends

9:02 AM

@Plergux ooh

10:04 AM

@LaTeXereXeTaL sorry for writing confusing code :)

Confusing fonts, 2020 edition

@PauloCereda you are lovul as well!

@Skillmon ooh

Harald Hanche-Olsen

@PauloCereda I read it as “covid” at first (with a dotless “i” on closer examination).

3

@HaraldHanche-Olsen oh no :)

Harald Hanche-Olsen

10:11 AM

@DavidCarlisle An oceanographer killed off the dinosaurs? Shocking news.

David Carlisle

@Skillmon always blame the user

@DavidCarlisle I actually thought that that bit was the least confusing of the entire package :)

10:41 AM

@MarcelKrüger I see you merged the font loader into dev. I will add the new lualibs files so that we can test this too, and then we could upload?

Currently writing an expandable mergesort. It can already sort lists of length 0, 1, and 2 :)

David Carlisle

@Skillmon so by induction, the implementation is finished

@DavidCarlisle Not entirely sure about that :)

11:02 AM

PL3 is coming

@JosephWright with or without \keyval_parse:nnn?

@Skillmon That's l3kernel ;)

@JosephWright are the PLs only for the 2e kernel?

@Skillmon Yes

@Skillmon l3kernel just has a monotonic date-based version system

@JosephWright ahh, thought the two were parallel since the integration... My bad.

11:04 AM

@Skillmon I'm still (more or less) free to do what I like with l3kernel releases, as long as they don't break LaTeX2e

@Skillmon I've merged, will check what tidy up is needed on other stuff then likely release l3kernel and l3backend (@UlrikeFischer)

@JosephWright ahead of LL? What's going on? :)

@PauloCereda We got held up by the holiday; some urgent-ish issues that @PhelypeOleinik has fixed

@PauloCereda I need to get people to re-read all of the content so we can finalise

@JosephWright that's the least of your concern, surely. :)

@JosephWright :)

@PauloCereda See Skype

@JosephWright is latex-dev in sync?

11:10 AM

@UlrikeFischer Probably not; I'll look to merge

@UlrikeFischer Let me get the release out first ;)

@UlrikeFischer Yes, I think everything is ready.

@JosephWright ;-) Don't you want to give ctan a busy silvester?

3

@MarcelKrüger I just got a failure with luatex-ja ...

@UlrikeFischer I'm not sure we need a pre-release; all of the PL stuff is quite technical

@UlrikeFischer Testing with luatex-ja is cheating: They actually use all the crazy edge cases.

@MarcelKrüger yes, but it is a bit disturbing that it simply makes "peng" and close.

11:18 AM

@UlrikeFischer Do you have an example document?

@MarcelKrüger I did simply run the luatex-ja test in the suite. It doesn't like it, if one disables the unicode library ;-(

@UlrikeFischer Oh, does it work if you insert (before loading luatexja):

\directlua{unicode = {
  utf8 = {
    byte = utf8.codepoint,
    char = utf8.char,
  }
}}

@MarcelKrüger no it stops too. I reenabled unicode for now. We can then open an issue for luatex-ja that they should better drop it.

@MarcelKrüger did you see the question about the ft-ligature in newcomputermodern?

@UlrikeFischer Yes, I would have given the same answer you gave: Use HarfBuzz to avoid such trouble. Beyond that I blame the font: The ft ligature does neither have a sensible name nor a sensible codepoint. I recently exchanged some mails with the author, I'll notify him.

11:37 AM

@MarcelKrüger I suspected the font too--there were no names in the lua--but I wasn't sure.

@MarcelKrüger I updated the news and lualibs, so we can now see if travis is happy. But the version info in build.lua must be updated. Do you want to sent luaotfload to ctan or should I?

@UlrikeFischer Please send it to CTAN.