Answers by this user could do with delete votes unless there's a moderator around. @DavidCarlisle @egreg @PauloCereda

@egreg oh

I know it's early in the morning, but I want Pringles...

@DavidCarlisle ^^ sounds suspiciously familiar

@PauloCereda early in Brazil, I just had lunch! So maybe it's ok for you to have some pringles... ;D

@GuilhermeZ.Santos :)

@PauloCereda I wouldn't know (my code is bug free)

@DavidCarlisle Mine too. :)

Ducks are good at coding. :)

@PauloCereda and we know there are no typos in your thesis

@DavidCarlisle <3

@DavidCarlisle See Skype!

@DavidCarlisle -- you mention that podcasts from the spqr event will be available later. if you could send me mail as well as posting that information here, i'd much appreciate it.

@barbarabeeton will do

@DavidCarlisle -- thanks.

Why doesn't this work? It doesn't seem to recognize the space before the opening paren. If you remove the space the document compiles.

% !TEX TS-program = xelatex
\documentclass{article}
\usepackage{xcolor}
\usepackage{fontspec}
\setmainfont{Linux Libertine O}
\newfontfamily\parenfont{Linux Biolinum O}
\XeTeXinterchartokenstate=1
\chardef\CharNormal=0
\chardef\CharBound=255
\newXeTeXintercharclass\CharParens
\XeTeXcharclass`(=\CharParens
\XeTeXcharclass`)=\CharParens
\newtoks\TokSetfont
\TokSetfont={\begingroup\parenfont\textcolor{red}}
\XeTeXinterchartoks\CharNormal\CharParens=\TokSetfont
\XeTeXinterchartoks\CharBound\CharParens=\TokSetfont

@AlanMunn not run it but 255 isn't the boundary class in recent xetex

\ifdim\the\XeTeXversion\XeTeXrevision\p@>0.99993\p@
  \chardef\e@alloc@intercharclass@top=4095
\else
  \chardef\e@alloc@intercharclass@top=255
\fi

@DavidCarlisle Ok so time to fix the docs...

@AlanMunn from latex.ltx ^^^

@DavidCarlisle But changing it to 4095 doesn't work either.

@DavidCarlisle I could have answered...

@AlanMunn @egreg can sort it out, I'm off line for a bit (driving:-)

@AlanMunn Don't you want \color{red} here?

@JosephWright That's just for debugging, so I don't care. :) The issue is that it doesn't seem to recognize the boundary char class.

@JosephWright Hmm. But it makes a difference. Why?

@AlanMunn Yes, but if you use \color and fix the boundary position (255/4095) it works

@JosephWright Yes, why does that cause an error when \textcolor is used?

% !TEX TS-program = xelatex
\documentclass{article}
\usepackage{xcolor}
\usepackage{fontspec}
\setmainfont{Linux Libertine O}
\newfontfamily\parenfont{Linux Biolinum O}
\XeTeXinterchartokenstate=1
\chardef\CharNormal=0
\makeatletter
\chardef\CharBound=\e@alloc@intercharclass@top
\makeatother
\newXeTeXintercharclass\CharParens
\XeTeXcharclass`(=\CharParens
\XeTeXcharclass`)=\CharParens
\newtoks\TokSetfont
\TokSetfont={\begingroup\parenfont\color{red}}
\XeTeXinterchartoks\CharNormal\CharParens=\TokSetfont

@AlanMunn Definition of \textcolor needs an opening brace:

> \textcolor=macro:
#1{->\@textcolor {#1}{.

@JosephWright Yes, that's the main issue; I also fixed the boundary class

@egreg Oops, aimed at wrong person: let me fix!

@egreg Yes, an abstraction is much better (leave such things to the kernel team!)

@egreg Yes, the XeTeX documentation doesn't reflect the change to 4095.

@AlanMunn Probably true: it's rather out-of-date

@JosephWright And \e@alloc@intercharclass@top certainly wins the prize for a very transparently named macro... :)

@AlanMunn For defensive coding, you can add a test about \e@alloc@intercharclass@top being undefined and set it to 255 in this case (assuming the kernel is not the short lived one that hadn't \e@alloc@intercharclass@top)

@AlanMunn Blame @DavidCarlisle, of course

@AlanMunn Comes from \@alloc (DEK) and some history ...

@JosephWright Kind of like why the past tense of 'go' is 'went'. :)

@AlanMunn :)

@AlanMunn I'm sure you can explain that!

@JosephWright fero, tuli, latum, ferre Also Latin had its quirks. ;-)

@egreg Everything requires conjugation. :)

@JosephWright @AlanMunn And Italian has (io) vado and (noi) andiamo (I go, we go)

@JosephWright The explanation is the same (minus DEK): "A bit of history".

@AlanMunn I've driven home and eaten and your problem solved:-)

^^^ Yay!

@HenriMenke :)

@JosephWright should we talk to such heretics?

@egreg confusing the visitors again I see

@DavidCarlisle You've not an exclusive in language weirdness

@egreg I meant the %%% +1

@DavidCarlisle :)

@DavidCarlisle ^^^

@DavidCarlisle Another one where one set of proper drivers would be nice :)

@JosephWright meanwhile any chance of getting trimclip updated?

quack!

@JosephWright And also texdef, if you're going to poke Martin

@egreg and standalone

and arara certain packages.

@DavidCarlisle I'll ask Martin

@MartinScharrer Some package updates for you :)

@JosephWright The problem with texdef are just a couple of braces that should be escaped for keeping newer versions of Perl happy.

@egreg I'm sure

@egreg Change needed to trimclip is some code I cooked up anyway, I think

> The Wall Street Journal reports Samsung is now looking into consumer complaints that its replacement phones are overheating. People who properly replaced their phones have been reporting that the new Galaxy Note 7's are still too hot to handle during a phone call. In a handful of cases, Samsung has even had to replace the replacement phones.

Oh boy.

@JosephWright: can we invite Brian Blessed to our user meeting?

@PauloCereda Good for cooking some code. ;-)

Off topic?

@egreg Seems unrelated to the site.

LaTeX grammar sometimes seems unnecessary complicated. Is there a good alternative that transpiles code to LaTeX from another "language"? I obviously want do be able to do everything with that language which I can do with LaTeX too.