@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 ;-).
@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 ..."
@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 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
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.
