TeX, LaTeX and Friends

12:01 AM

@1010011010 it isn't an error it's a warning that you are not getting the box the size you asked for which if it relates to output on the page you might want to know about, but this is a fomalised idiom using a box as a storage location for multiple notes and using vsplit on forced breaks to split them up again and extract them from the box, so the extracted box will never be \maxdimen in size so the warning isn't appropriate and tex has a standard mechanism for turning it off

1010011010

@DavidCarlisle Hypothetical example: the marginpars can be stored in seperate boxes, measured in height and width, and then the values can be subtracted from \maxdimen, so that the extracted box has some altered value which would make sense to TeX? (Just thinking out loud here?)

David Carlisle

@1010011010 you could do something but why make it more complicated and less efficient just to avoid using a standard mechanism for controlling warnings?

1010011010

@DavidCarlisle Besides doing everything the "correct" way there's no point in wasting memory on it. :-)

Thanks & night everybody.

Joseph Wright

8:35 AM

Hello all

yo'

@egreg @barbara Can I have a typography question, please? How would you define the \set command? MWE follows:

\documentclass[11pt]{amsart}

\usepackage{lmodern}
\usepackage[utf8]{inputenc}
\usepackage[T1]{fontenc}
\usepackage{microtype}

\pagestyle{empty}

\usepackage{mathtools}
\DeclarePairedDelimiterX\setA[2]\lbrace\rbrace{\,#1\suchthatB#2\,}
\newcommand\suchthatA{\,\mathclose{}{:}\mathopen{}\,}
\DeclarePairedDelimiterX\setB[2]\lbrace\rbrace{\,#1\suchthatA#2\,}
\newcommand\suchthatB{\:\mathclose{}{:}\mathopen{}\:}
\DeclarePairedDelimiterX\setC[2]\lbrace\rbrace{\,#1\suchthatB#2\,}
\newcommand\suchthatC{\ \mathclose{}{:}\mathopen{}\ }

Or would you use something completely different?

@JosephWright Hello there

David Carlisle

@yo' why not simply \mathbin{:} rather than forcing the space either side, it's essentially just an infix "such that" operator here isn't it?

yo'

8:51 AM

@DavidCarlisle ah well, yes, probably. But isn't then the spacing too tight anyways?

David Carlisle

@yo' well you don't manually tweak the spacing around \in

yo'

@DavidCarlisle but you tweak the spacing around the braces here since it's a "triple operator", so I wasn't sure if the spacing around the : should be increased, too

David Carlisle

@yo' only because { is gratuitously non-symmetric around its vertical axis, but that can't be said about :

yo'

@DavidCarlisle no, not that. Note that you have $\{x_1,x_2,x_3\}$ , but $\{\,x_i \mathbin{:} i=1,2,3\,\}$

David Carlisle

@yo' if you wanted to increase space I'd just use \mathrel instead of \mathbin rather than the constructs with empty \mathopen{} where I'd have to work out what spacing it produced:-)

@yo' you might.

yo'

8:55 AM

@DavidCarlisle you always make it too simple :D

@DavidCarlisle well, it's what Donald Knuth recommends, AFAIK, but I dunno about the :, I know only about the braces.

David Carlisle

@yo' who's he?

yo'

@DavidCarlisle who knows?

Joseph Wright

1

Q: XeLaTeX renders broken text after upgrade to Ubuntu Vivid

I recently upgraded to Ubuntu Vivid, which broke the XeLaTeX rendering on my system. Only \textbf{} and \textit{} of specific fonts are affected. The character table seems to be off-by-one. I use TeXworks. For example: \documentclass{article} \usepackage{fontspec} \setmainfont[Mapping=tex-text]...