@gusbrs :D

Morning all

@DavidCarlisle I'm reading your minutes :)

@JosephWright quack

@JosephWright the "wait for Joseph to show up" items?

@DavidCarlisle Yes

@PauloCereda /quack

@PauloCereda breakfast

@JosephWright ooh

@DavidCarlisle oh no

@DavidCarlisle in the french list someone tried to handle files with mixed encodings by a bunch of \inputencoding{utf8} and \inputencoding{latin9} and ran into problems as the one does settings globally and the other locally ;-).

@UlrikeFischer :)

@UlrikeFischer Did they think they were colours? ;)

@UlrikeFischer it does? That would be wrong then, should all be local

@UlrikeFischer Que faisiez-vous sur la liste française ?

@DavidCarlisle yes utf8 contains various xdef. They added it to the toc and then got errors. Try

\documentclass{book}
\usepackage[latin9]{inputenc}

\begin{document}
\show ä
{\inputencoding{utf8}
 \inputencoding{latin9}
 \show ä
}
\show ä
\end{document}

@UlrikeFischer ööh

@UlrikeFischer Not My Fault

@egreg Probably one for you: twitter.com/zr_tex8r/status/1486627424947564549

@UlrikeFischer probably we should fix that although fixing the latin9 file to be in utf-8 is probably more useful

@JosephWright ooh

@DavidCarlisle ooh cheese

@DavidCarlisle :)

@DavidCarlisle the question started with "Bon, que ceux qui vont répondre « écris tout en UTF-8 et compile avec xelatex/lualatex » quittent la salle ..."

Je suis a cannard

/coin coin

@PauloCereda avec l'orange?

@DavidCarlisle oh no

@UlrikeFischer well that's not very friendly:-)

@DavidCarlisle there were some discussions earlier about utf8 so I took it simply as a clarification that he is aware of this option. A bit like the "I know it is ugly but I have too ..."

@UlrikeFischer in utf8.def

}
\begingroup
\catcode`\~13
\catcode`\"12
\unexpanded{\endgroup
\def\UTFviii@loop{%

then replace the \endgroup after the loops with } and use \edef not \xdef in each of the definitions?

@DavidCarlisle could probably work. But it is worth the trouble? mixed encodings aren't something that we really want to support.

@UlrikeFischer well we have always sort of claimned to support them (which is why there is an \inputencoding command) although changing them at anywhere other than file boundaries doesn't usually make sense so grouping isn't usually an issue.

@DavidCarlisle in this it was for the table of contents which builds a group. The handling of auxiliary files is typically the most challenging - one reason why luainputenc wasn't really a great idea.

@UlrikeFischer yes sure getting the right encoding in the right place is tricky but if the basic provided commands escape tex groups it's trickier than it needs to be

@DavidCarlisle ok if you want to repair, should I open an issue for it?

@UlrikeFischer if we are going to change should be an issue first I think

@DavidCarlisle ok I will open it.

@JosephWright The simplest is to try it… ;-)

ooh pythons twitter.com/edu4rdshl/status/1486619369748770821

@PauloCereda Is github.com/sveinbjornt?tab=repositories a cousin of yours? Uses nice repository names like "Platypus" or "Sloth" :)

@samcarter ooh

Fluffy is back home: newsrnd.com/tech/…

@samcarter ooh

@DavidCarlisle !!!

@UlrikeFischer Vous avez cassé la ponctuation française

@DavidCarlisle looks so. the (x)color patches seem to be the problem.

@UlrikeFischer yes got that far then thought of you, but then you showed up anyway so I didn't need to blame you

@DavidCarlisle ooh

I'm getting weird artefacts in the display of the main page now. I thought it was my user script to return to the old page format (which seems to have stopped working) but even with it disabled they remain. Anyone else seeing this?

Hmm. Turning of Greasemonkey entirely solves the problem. So it's one of my older user scripts that's causing this.

@JosephWright shouldn't this here error? \cs_generate_variant:Nn \my_test:no {no} ?

@JosephWright well it doesn't. I just created some quite nice loop by mapping an ne to ne ;-(.