Which is the best country to live?

@LoveGrover CNN says Norway. Must be true. edition.cnn.com/2015/12/16/travel/undp-most-liveable-country

(Had the wrong link there for a second, fixed now.)

@LoveGrover Best according to what parameters?

@Alenanno For example: How much a foreigner can have freedom? If there is any racism? How much it is good for natives? Basic Facilities must be there with natural heritage. etc.

@TorbjørnT. Does the criterion take average temperature into consideration? ;-)

@LoveGrover Oh I see. Where are you from? If I may ask (you don't have to answer if you don't want to).

@JosephWright: ^^

Sorry, I couldn't resist. :)

@PauloCereda Indeed

@egreg yes

And they put an alligator wearing a brassiere. That's disturbing. :)

@PauloCereda :D

@egreg Wouldn't think so.

:)

I heard about Himalayas. What are your opinions?

@TorbjørnT. Just to make you envious, I can remember when, for St. Agatha's feast in Catania, I went downtown in the evening with my scooter, wearing no gloves. FYI, St. Agatha's feast is on February 5. ;-)

@egreg Yeah, well. I like skiing.

@TorbjørnT. And you surely have good gloves!

@egreg I have ridden my bicycle downhill to uni mid-winter in Central Norway (-20 °C) without gloves, resulting in loss of the ability to brake. Would not recommend glove-less riding here! ;-)

@hooy Or having a pizza around midnight, end of October, sitting outside in front of the sea? :)

@hooy You can spot the tables of the pizzeria.

@hooy MINUS TWENTY DEGREES?!

You guys gotta be kidding me.

I freeze to death with 13C.

:)

@PauloCereda lol. Btw, had snow last week again in Prague :)

@yo' yaaaay! Speaking of which, I am aiming at a conference in Prague. :)

@PauloCereda which one?

@yo' stringology.org/event

@PauloCereda I thought so :) I shall be at home then :)

@yo' Stringology is the study of stringolos. :)

@PauloCereda no :)

> Please, do not forget to say \usepackage{pscproc2.sty} at the beginning of your contribution LaTeX source file, right after \documentclass[envcountsame]{llncs}.

I think a mail is needed.

@egreg I went to Milan in December/January, and was pleasantly surprised by the temperatures at that time of year – I walked around in just my t-shirt the first day, when I believe it was around 8 °C (and yes, quite a few people looked funny at me) :)

@PauloCereda btw, I used to walk in only shorts and T-shirt up to -5C, as long as the humidity was low.

@yo' HE'S A WITCH

:)

@Alenanno Pakistan

@PauloCereda Well, I've always been a winter-type person, so I enjoy -20 °C. I just decided I wouldn't need my gloves for the 10 min bike ride :)

@hooy o.O

@hooy No Italian would go around in a T-shirt with less than 20°C :)

@hooy one of my worst (best) cycling experiences: down la rue La Fayette with 5 cm of snow on the bike path, being almost the only cyclist in the entire city :)

@hooy But it happened something similar to me when I lived in Sicily: local people were freezing, I wasn't.

@yo' Studded tyres?

@JosephWright if studded means with pins, then no. It was the heavy, womby and slippery "city bike" :) (also, IIRC, the brakes we as operational as always)

@yo' Ah

@yo' I've not got studdeds at the mo but have a friend who does: he strongly recommends them

@JosephWright well, I have no bike now :) only car (with winter tyres, but not studded; that's illegal here except for the emergency)

@yo' Sure, cars are different (bike studs are not the same as car studs)

@JosephWright I know. Still, no bike means no studs :)

@yo' :-)

Now I gotta go as the meal I wanna take will be out soon (can you say "out" in this context? maybe "over" is better?)

hi, can I have two side by side minipage boxes with borders around?

@EnthusiasticStudent \noindent\fbox{\begin{minipage}{0.45\linewidth}BLA\end{minipage}} \fbox{\begin{minipage}{0.45\linewidth}BLO\end{minipage}} but I doubt this is what you meant...

@yo' I mainly want to omit margin and have exactly two side by side minipages that cover the whole paper width length. The problem here is that first minipage starts from side of margin...

@EnthusiasticStudent ah, well, you want absolute positioning on the page then?

@yo' probably. I want to make my cv, on the top part I want to put my name and address and my photo. on the main document I want to use both the margin part and text width part

@EnthusiasticStudent maybe it's not a goal for minipages at all then. What will be put in the margin -- standalone text, or comments to the main part?

@yo' the dates of my papers or some tags. nothing special...

@EnthusiasticStudent \marginpar then? :)

Or what I do for my CV

Do you know about any system of downloading code written in some|all any user answers? I still have some of my answers in my computer, but I would like to keep and collect all. Do you thins it's possible?

@yo' yes I exactly use this syntax. However, I have problem with my title page which I want to decorate my name, photo and addresses. I want those two boxes to have them typed in.

Then you omit the margin?

A MWE please :))

@EnthusiasticStudent It's not a margin (I don't use margin pars)

@yo' But the margins white space is still there, I think

@EnthusiasticStudent where?

@EnthusiasticStudent you always have a margin. Do you know how ugly are documents without margins? Also, how many printers do not print closer than 0.5in from the paper boundary?

do you have an email address?

@yo' yes you are right

probably I have to minimize my margins by editing my geometry package

@yo' yes I proudly have :))

@EnthusiasticStudent I can send you the CV sourcecode, but not here

@EnthusiasticStudent ok

I love Deedy template for cv too

github.com/deedy/Deedy-Resume

@EnthusiasticStudent Hmm

@EnthusiasticStudent Too much information going on. :)

@DavidCarlisle: ^^

@PauloCereda :)

@Ignasi \rotatebox{180}{!}Hola!

I don't know how to add an upside down exclamation point, sorry. :)

@PauloCereda !`

@yo' I will use an i, nobody will notice, except Apple. :)

@Ignasi: iHola!

^^ ooooh it worked

@yo' <3

Someone is a coffee here. Hello, coffee! Salut, @omisson! Ça va?

Bonjour!

Das Kaffee!

@PauloCereda Ça va? Oui, káva!

@yo' errr... Je ne parle pas Français. :)

@PauloCereda (lowercase f for the adjective) The last word is the Czech word for coffee, whose pronounciation is as if you omitted the cedille in cava :)

@yo' ooh

@PauloCereda You're there! ^^

@yo' Oh my! <3

@PauloCereda :)

@yo': but I still need to write the paper and hope for the best. :)

@PauloCereda and then negotiate couple extra days for free accommodation with your PI :)

@yo' awwww <3

@PauloCereda Hi Paulo! Are you still here?

@Ignasi ducks are omnipresent

@yo' :)

@Ignasi Yep. :)

@PauloCereda I know some time ago you wrote a "pretty printer"(?) for TeX.SX so I understand you know how this place works. Do you know if it's possible to easily collect certain answers or part of them?

@Ignasi Parts of a thread would be quite complex and possibly not doable, but select certain answers would be doable. The only problem is that would require a major rewriting of my tool. :)

@PauloCereda Ok! My question was more curiosity than a real need.

@Ignasi ;)

@Ignasi: I need to rewrite the tool anyway, so it's in my TODO list now. :)

@PauloCereda Then, let me know when you scratch this item from your TODO list. ;)

@Ignasi Sure! It might take a while though. :) I still have arara and my thesis... :)

@PauloCereda No problem. It's just procrastination, you know :)

@Ignasi :)

@JosephWright Is this change in conditional name something that was necessary? It seems that it was mainly for making the code more semantic. But it clearly breaks some biblatex styles. tex.stackexchange.com/a/298403/2693

@AlanMunn See earlier discussion, primarily with @UlrikeFischer: this was never a public interface and the intention has never been that styles to 'back end detection' (I was not involved in the change)

@AlanMunn I'm working on re-integrating the two code paths so the BibTeX 'fall back' is a lot smoother

@JosephWright Just read through it. I see. So we just hope that the various biblatex style maintainers are still actively maintaining.

@AlanMunn Indeed: I've very quickly fixed all of my styles, and if I can get my revisions to the core done and working might well take a bit more active interest (I'll discuss with PLK)

@AlanMunn Plan to do a lot of work in github.com/josephwright/biblatex, and if it all works out some of these issues should be fixed (by having a proper mechanism for falling back from Biber to BibTeX)

@AlanMunn I have already seen updates in the CTAN announcement. But I think that for all people involved in "biblatex help" the next week will be quite interesting ;-).

@UlrikeFischer @JosephWright It seems so. Will all the problems arise from styles that use some form of version check, or are there other things lurking too?

@AlanMunn There are some other things too

@UlrikeFischer Indeed

@UlrikeFischer Like I say, I'm working on a long-term solution here for keeping support in-line (I think it's quite doable)

@AlanMunn Imho the version/backend check will only lead to minor problems. The more interesting area is the change in nameformat: github.com/plk/biblatex/issues/372

@JosephWright I'm not in panic ;-). Such things happens from time to time. In miktex I would say we are in a "critical update phase".

@UlrikeFischer :-)

@UlrikeFischer Indeed

@UlrikeFischer I do think though it's worth me putting the effort in to re-combined the two code paths so the variations between backend are only by necessity not as we have two files to update!

@UlrikeFischer Eek. Yes, this will surely cause lots of grief in the short term.

So should I come up with an biber-like duck-related program? :)

@PauloCereda Or a duck-based regex engine. You could call it pato-matcher :)

@PauloCereda Because it matches patterns (need an British accent for this pun to work, though (no 'r' in "pattern" )).

@AlanMunn OHMYGOD

@AlanMunn DUDE THAT'S THE BEST NAME EVER

@PauloCereda :)

@PauloCereda And the CFG engine can be marreco-matcher, because, of course, marreco is not a regular duck... :)

@PauloCereda So many layers to that one, you're the only person who could possibly get it, I think. :D

@AlanMunn Alan, seriously. You are ruining my thesis with these awesome names. <3

@Alan: Payback will come in August. :)

@PauloCereda :)

@JosephWright (or anyone) could you try this with lualatex?

\documentclass{article}

\usepackage{amsmath}

\begin{document}

\[
\binom{n}{l}
\]

\end{document}

@DavidCarlisle It works.

@PauloCereda not for me, I get:

@DavidCarlisle Same here with v0.89.3

@DavidCarlisle wow!

[paulo@cambridge documento] $ lualatex --version
This is LuaTeX, Version beta-0.80.0 (TeX Live 2015) (rev 5238)

Hans broke latex again

@DavidCarlisle Can check with v0.80 if you like ...

@JosephWright i did wonder last night why some of my luatex diffs looked a bit odd.

@JosephWright please (I don't trust @PauloCereda:-)

@JosephWright It works.

@DavidCarlisle /sob

@barbarabeeton ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^‌​^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^6

@barbarabeeton: David is being mean to me. <3

@JosephWright I guess I need to make a plain tex version.

@DavidCarlisle Fine with v0.80, same TeX system just swapping luatex.dll

@DavidCarlisle -- yeah, i noticed. but i can't do anything for another half hour at least -- the system i mostly work on has had an "emergency": "currently unavailable. The IT department is working to solve the problem. We will send an update at 1 PM."

@DavidCarlisle Guess so

@PauloCereda -- at least he didn't blame you for changes to luatex.

@barbarabeeton nothing you can do really anyway, looks like luatex 0.98.3 isn't usable (probably it's @PauloCereda's doing)

@DavidCarlisle -- why blame @PauloCereda? after all, he's working on his thesis.

@DavidCarlisle Easy:

$$
n \atopwithdelims () l
$$
\bye

@barbarabeeton please insert "should be"

@JosephWright I had

@JosephWright I feel another luatex list email coming

@barbarabeeton <3

@DavidCarlisle oy

@DavidCarlisle Yes

:)

@PauloCereda: Thanks ;-)

@PauloCereda Have your Pringles ready?

@egreg Yep. :)

@JosephWright .89.4 built from texlive svn but \choose still broken

@DavidCarlisle Grabbing now

@DavidCarlisle Am currently sorting out \tracingfonts in expl3 (it is now a native primitive name as well as being used by the 2e kernel)

@JosephWright should probably ping Frank about changing tracefnt ?

@DavidCarlisle It's OK: the kernel uses \def so the primitive just gets zapped

@DavidCarlisle \directlua { tex.enableprimitives("@@", {"tracingfonts"}) } to the rescue

@JosephWright def? \newcount but yes but is that the right thing to do if it is (now) a primitive? (or should we alias the primitive to a new name first)

@JosephWright :-)

@DavidCarlisle Kernel does \def\tracingfonts... so there's no actual issue: anyone who really wants the engine version can get it back. In any case, expl3 is going to save it as \@@tracingfonts as well as \pdftex_tracingfonts:D so it's there for anyone loading fontspec

@DavidCarlisle Question: who is using this primitive :-)

This is LuaTeX, Version beta-0.89.4 (TeX Live 2016/W32TeX)

base/tracefnt.sty:\newcount\tracingfonts ??

He jests at scars who never felt a wound.

@DavidCarlisle Same thing: doesn't use \newcommand or whatever, so not an issue

@JosephWright yes agreed,

@DavidCarlisle I did wonder about adding \@@tracingfonts to the kernel, but didn't really think it was worth it

@JosephWright think we can conclude no one is using the newer luatex builds yet.

@JosephWright yes agreed tex.enableprimitives means you can always get it back unlike over-writiing a primitive in classic tex

@DavidCarlisle Yes, user base is select

@JosephWright user base is annoyed

@DavidCarlisle Exactly, or you can \primitive\tracingfonts

@DavidCarlisle :-)

@DavidCarlisle: do you accept postdoc students?

@PauloCereda do you mean do I accept that they exist?

@DavidCarlisle No, they don't

@DavidCarlisle I meant as you being their mentor.

@JosephWright boo

@PauloCereda one or two a year usually but always on numerical subjects: nag.co.uk/collaboration/studentpartnerships

@PauloCereda Post-docs are staff, not students, and are thus not registered as such

@DavidCarlisle I know math... sort of.

@JosephWright I know. :(

> Pole-vaulting methods for ordinary differential equations

Is it close to pole dancing?

@DavidCarlisle: ^^

@PauloCereda no watch the Olympics in the summer

@DavidCarlisle oh snap

@DavidCarlisle In Rio this year? No thanks. :)

@Joseph, @David: please tell your fellow countrymen to not come to Rio.

@PauloCereda I have a colleague who goes regularly to Brazil, but only via Rio so that's OK

@JosephWright :)

@barbarabeeton I imagine you know in a technical sense the answer to your question (tex.stackexchange.com/questions/298550/…) :-)

@JosephWright -- no, not really, which is why i asked it.

@PauloCereda yes.... too much indeed... but fonts and colours are so eye catching to me

@JosephWright Hmm?

@EnthusiasticStudent Wouldn't be my model: quite apart from the visual stuff, I think it's a bad sign when there are two classes which vary in font choice but nothing else (as in any case for this use the font is something the user should be setting in their doc)

@EnthusiasticStudent I'm not a fan of CV-related document classes: they are one-off docs so better done using article + adjustments

@EnthusiasticStudent Other reason for me to dislike it. :)

@JosephWright -- yes, we do have the preflight tools. and they require individual attention for each figure. we have a tool that reads dvi files, accesses each graphics insertion in turn, does a series of checks on the elements i mentioned, and highlights the (usually few) that do need special attention. so probably 80+% of graphics don't actually need to be looked at. (the greatest call for attention is for non-embedded fonts. not for the other problems.)

@barbarabeeton You obviously care a lot more than the people I deal with: basically for us it's 'authors issue' if the graphics are no good

@barbarabeeton We still get asked for TIFFs (from vector graphics), though I tend to ignore this and send the original and PDFs

@JosephWright -- we got rather tired of complaints about figures that were unintelligible.

@barbarabeeton Like I say, 'not your problem' :-)

@JosephWright me too, even me who am a basic user of latex made my own style of cv document by mean of document class type...

@barbarabeeton I'm guessing you don't get composites made in PowerPoint from vector/bitmap originals and copied into Word, ... (that said, I've just done exactly that for a graphics abstract entry: don't have a copy of Illustrator and I'm not good enough with InkScape)

@JosephWright -- we do ask for vector graphics (where possible; photos aren't possible as vector graphics). if we get pdf files that came from vector graphics, we back-process them into ps and then send them through the checking routine.

@barbarabeeton do you require hyperlinks in the latex/dvips route?

@JosephWright -- matter of policy. ams does care that graphics are informative and intelligible. and sending things back to the author usually causes an unacceptable delay/increase in cost of production.

@DavidCarlisle -- we require correct \ref{...} and \eqref{...} resolution, but not real hyperlinks. but we do require matching line and page breaks across the two versions.

@DavidCarlisle -- i suppose you noticed that this question is properly uppercased. it's official.

@barbarabeeton well that simplifies things as dvips has problems making links over a line break so in some cases hyperref boxes link text, but if you weren't making hyperlinks then the problem goes away

@barbarabeeton NO :-)

@DavidCarlisle: ^^

And upvoted, of course. :)

@DavidCarlisle -- no, problem doesn't go away. we still are unable to get the proper result for \ref on a label to a theorem, because \begin{enumerate} screws up the relationship. take a look at the ugly workaround we've been living with: ams.org/tools/faq?faq_id=206

@barbarabeeton if it works with pdftex you should make it work with latex, the line breaking logic is the same

@barbarabeeton: it is so beautiful to see you writing in uppercase, it is the Aurora Borealis of TeX. :)

@DavidCarlisle -- yes, one would think so. but we haven't been able to figure out how to do it, and need help.

@barbarabeeton post an example that gives the right behaviour with pdftex?

@PauloCereda -- you read tugboat. you know i'm capable of uppercase. just not on-line. (when we finally meet, face to face, ask me the reason. it's a long story.)

@barbarabeeton I know. :) But it's always amazing. :) And we will have so much to talk, I will add to the list. :)

@DavidCarlisle -- the example in heiko's answer -- linked from the question -- is such an example.

@barbarabeeton OK will look in a bit

@DavidCarlisle -- oh -- that also works with xetex. but not with just "latex", although it's processed with pdftex and goes the dvi route. if you come up with a good answer, i'll award a big fat bounty. this has been bugging us for years.

@barbarabeeton OK I'm not at home, sorting out parents but may get chance to look later.

@JosephWright muskip :(

@barbarabeeton @yo' Well, what should i say? en.wikibooks.org/w/index.php?title=LaTeX/…

@Johannes_B "GTFO"

@yo' :-)

@Johannes_B -- first, i admit that my direct experience using color is quite limited. one thing i notice is that neither the "original" or your edited version say anything about the difference between color on the screen and color in print. (getting a good match is beastly hard.) i'm inclined to think that maybe you did take out more than necessary. if i had been writing it, i would have arranged it (the original) differently, with the color chart as an appendix, arranged by color, not by name.

not knowing who wrote the original, i have no way of knowing their level of latex competence. it's not evident that this is written with a great level of experience; i could have done as much borrowing from other sources.

@barbarabeeton Package xcolor defines a lot of colors. Putting limited subset of them on a wikibook page is ... well, i think either none, or all. Meaning almost 1000 (can't remember the real number). I won't code that knowing that the full set of colors including a color example can be found in the manual. But the difference of on-screen and on-paper color is a good point. Putting aside the table, the changes aren't that drastic.

Agreed, my version was not as detailed, but a book that is aimed at starters, i think introducing the different color models is a bit too much (even if just a subset is mentiones).

@Johannes_B -- i guess what i'm getting at is that not everything has to be on one page. a good basic page, with links to more detailed topics, would be a reasonable goal. writing for print is different from writing for on-line consumption.

@barbarabeeton Agreed, splitting things off to appendix pages seems to be reasonable.

@barbarabeeton I don't have much experience with print vs. screen stuff. Do you have an expert at hand?

@Johannes_B Again, the question is, do you need 5000 wikibook chapters for 5000 packages?! I mean c'mon, let's teach people how to fish by showing them texdoc or ctan or any other way how to open the manuals.

@Johannes_B -- yes, but he's left for the weekend (although he just posted a question on the main tex.sx site).

@PauloCereda :)

@yo' Certainly not. In the bibliography segment is a \huge (i cannot view it on my screen) matrix showing which fields are available with which type in biblatex. In my POV, this is scaring people. Giving a list of ~1000 predefined colors ... ridiculous i think. Having a If you want to know the full list, click link thing does not blow up the page and the matrix/list can stay.

I won't mind such a page, but i will not write it up.

@JosephWright I can't remember which cv class I use but I do like the extra typesetting structure it provides. It's more ad hoc than a table in typesetting terms and more capable than the standard lists.

@JosephWright Longer term I want to generate cv plus online academic profile from the same data ... I guess I'll need to learn latexml

@WillRobertson Well, my experience with CVs is that they can be either nicely looking or automated.