I want to make context and context-mkiv tags as synonyms. I created the synonym at tex.stackexchange.com/tags/context/synonyms Could a few of you please upvote the suggestion?
@yo' for some reason they can not spell "jam" correctly. Jelly is gelatinous desert made off (allegedly) fruit juice, usually eaten with cream or ice cream.
@PauloCereda The duck has just arrived in Milan, photo album is coming soon! I haven't seen it yet, because I'm at work and I asked my mother to go to my house and wait for the postman. She's just told me it has arrived and is very funny!
To everybody: how could I call it? 30 reputation points to who will find a funny name! :):):)
@JosephWright pdftex takes resolution into account so ends up with print size as specified, luatex does not, so ends up 20% bigger (and so clip coordinates are wrong)
@JosephWright so now I suppose I have to read the luatex manual to see if it is reporting the size incorrectly or if the macros are not picking up the resolution. luatex.def does same (wrong) thing as pdftex.def if you enable that with luatex85.sty so it isn't just that change that broke things
without an actual example, here's how i interpret what you want.
and here is the input:
\documentclass{article}
\usepackage{mathtools}
\begin{document}
This example shows \verb|aligned| equations within
an \verb|align| environment.
\begin{align}
\phantom{i + j + k}
&\begin{aligned}
\m...
^^^ my attention was called to this answer, and looking at it, i noticed that the end-of-line backslashes in the display code had been "singled" and the following eol collapsed to put two input lines on one line. i've now edited it to be what i am sure i really input in the first place. it's a few years old; i think the system corrupted it, and i'm pretty sure i would have noticed it at the time, so i suspect something has happened in the interim. has anyone else seen this?
Not the first time it happens on the site, so it's time to raise the problem in Meta.
It is similar, but distinct from ‘double backslash + newline’ collapses to ‘single backslash’ when I hit ‘edit’; what happens is that code with lines ending with \\ gets randomly transformed, without any interv...
@egreg -- yup. good on you. i'd already made the correction, but in the edit reason, i said "suspected corruption by system". this is the same wretched problem that bedevils me when updating some web pages at ams, so if a reason is found, maybe i can get the maintainers of the miserable update system here to do something useful about it.
@yo' -- oh, don't be concerned. i'm still catching up, have also got a nasty cold, and am still on "outer mongolian time". i'll probably be pretty useless for a few more days. but thanks for the heads up.
Good afternoon. How are you? I would, if you allow, ask for help. This should be a working mini example, but it does not work. It works when I leave out babel. But could it be that babel+french and fancyref don't work together, please?
@Gudrun it is a character that is defined to have a definition like a command without \ . The example in the format is ~ to make a non breakable space but french babel makes most punctuation active so it can add space before as required by French typographic style
@Gudrun as far as I understand the French style is to have a thin space before : so there is no convenient way without that abc: adds no space and abc : adds too much space and allows a line break before the colon and noone wants to type abc\nolinebreak\hspace{.2em}: every time
@Gudrun so the maintainers of the French latex support made : active and defined to be a command that essentially removes space before the colon and then adds a non breaking thin space so input of abc: or abc : both produce abc\nolinebreak\hspace{.2em}:
@Gudrun which is fine in text but less fine if you go \label{fig:abc} :-)
@DavidCarlisle Sorry. Okay I see your point. But if one writes: \label{fig:abc} The colon is inside another command. Why should this cause a problem, please? Sorry, I am just curious. Could one not say to ignore all colons within latex commands?
@Gudrun That's not how latex works (same reason that you can not make \verb work inside a command.) babel does have commands to turn this off (\shorthandsoff) so if doing this by hand you can make : safe do whatever then switch it back to "french punctuation" but if a package is inserting colons automatically not expecting this things can go wrong. (If it had been expecting it it could arrange slightly more complicated internals to make sure that it always used a "safe" character.
@egreg Sorry, I expressed myself badly. In theoretical physics I learned how to use math to solve my problems. The explanations in theoretical physics concerning the math part were better than in math.
@egreg Agreed, the theoretical physics teacher was able to explain better maths. But I hope you enjoy your studies. But cool that you know already so much about LaTeX, I just started it in my third term.
@egreg Yes I agree but I meant more on the balance of different use cases and any other solution approaches. (If one can be sure of all possible verbatim environments it's possible to track things, but that's pretty tricky.)
@DavidCarlisle First one was that tabs got gobbled inside listings, second one was that fixing it then meant that \end{frame} can't be indented: fixing that means you can't 'hide' a verbatim \end{frame} by simply indenting ...
@JosephWright Imho it is the same problem that one have with nesting quotes in programming. You either need a way to escape the inner quote (difficult in your case) or you need two "quote symbols". So i would suggest to add a "fragileframe" environment.
@JosephWright What would you think about going back to bitbucket.org/rivanvx/beamer/commits/… but add a document class option to switch this on/off easily for the whole document (depending what the default would be)?
@samcarter BTW, I'm hoping that Vedran will at some stage remove the BitBucket page: ideally I'd like the 'correct' place to report things to be clear :)
@JosephWright yes I'm suggesting a fragileframe environment so that someone who wants to document frame can use it. I don't see a point to put a lot of effort in getting nested fragile frames working.
@egreg -- hmmmph. they weren't usually baked. but sometimes a building containing a store of tablets caught fire, which did have the effect of making them permanent. go to tug.org/TUGboat/Contents/contents33-1.html and click on "title page" for a critique regarding permanence.