« first day (4008 days earlier)      last day (41 days later) » 

2:45 AM
hello,
Is someone able to walk me through how to script adding fractions and then turning the result into a mixed number? I have used the following answer tex.stackexchange.com/questions/28628/… to get started but I don't know how to convert the improper fraction. I am guessing employing the use of ifthen to check then an integer division with a modulo of some sort.
 
 
2 hours later…
4:38 AM
@E.Yu You cold use expl3 for that: There is the \int_mod:nn function and \int_div_truncate:nn, and for the comparison you could use \int_compare:nNnTF.
 
 
1 hour later…
6:03 AM
@Skillmon I've never used expl3 before and don't know where to start.
 
 
1 hour later…
7:05 AM
@E.Yu What's up with the answer you've linked to?
 
 
1 hour later…
 
1 hour later…
10:47 AM
 
@samcarter can I say "ooh"? ;-P (maybe @PauloCereda copyrighted it...)
 
@Rmano you could avoid license issues with "ohh" :)
 
@samcarter or óôò which is palindrome too...
 
11:04 AM
@Rmano Quick, get this copyrighted before someone else uses it :)
 
11:15 AM
@samcarter "Mine" (with the seagull's scene from Nemo)
 
@Rmano :D
 
12:06 PM
@DavidCarlisle Seen the comments on color in overleaf.com/blog/tex-live-2021-now-available?
Getting close to 750 people visiting the election page
I hope we get >1k (still a small proportion of the electorate)
 
12:41 PM
@MarcelKrüger Didn't get to the Lua color last night, will try to today
 
1:18 PM
@JosephWright "The xcolor package should always be loaded, instead of the obsolete color package; otherwise you may see some mysterious errors especially if you try to use the xcolor package options (e.g. dvipsnames, x11names) with color." Not sure what's changed there? (@yo' ?)
 
1:57 PM
@Rmano ooh
@Rmano you can use it
 
yo'
2:13 PM
@DavidCarlisle I'll ask LianTze about it
 
@PauloCereda Oohpen source interjections.
 
@AlanMunn ooh
 
2:28 PM
Can XeTeX print non-BMP characters in error messages correctly? When I compile like `$𝒖$ \errorerror
` it prints `! Undefined control sequence.
l.6 $풖$ \errorerror
` instead.
Sounds like a bug but I can't find this anywhere
On the other hand when I use tl_show it does show > \a=𝒖. correctly
 
@yo' thanks, no harm in suggesting xcolor of course but I'm surprised there is a tl2021 change
@user202729 that's a feature of your terminal not xetex, xetex is pushing out utf8 text, what your terminal does with that is not under its control
 
yo'
@DavidCarlisle could be that some template(s) seemed to break between tl2020/2021 and switching color to xcolor solved it (for whatever reason) -- we assume that if it happened in templates, it'll equally likely happen in documents too. But I'll get back to you with a clarification :)
 
@DavidCarlisle No, tl_show get it correctly
 
@user202729 yes saw that after, so "this can't happen" or "let me try before answering again" or ...
! Undefined control sequence.
l.5 $풖$ \errorerror

?
> the letter 𝒖.
l.7 \show 풖

?
@user202729 hmm blame @PhelypeOleinik might e a reasonable course of action here.
@user202729 the last one is particularly telling it gets it right in the actual meaning but messes up the context line
 
@DavidCarlisle Most likely not, but let me see
 
2:41 PM
! Undefined control sequence.
l.5 $𝒖$ \errorerror

?
> the letter 𝒖.
l.7 \show 𝒖

?
luatex ^^
 
Of course it gets the meaning correctly, the compilation output is correct (yes I use all Unicode characters in input)
 
\documentclass{article}

\begin{document}

$𝒖$ \errorerror

\show 𝒖
\end{document}
@user202729 I mean \show shows the meaning correctly in the log
@user202729 @PhelypeOleinik it is showing U+D496; instead of U+1D496 so out by hex 10000 ...
 
@DavidCarlisle I'm not at home, right now (and no permission to install a build setup for TeX Live in this machine), so I'll take a look later
 
@PhelypeOleinik you don't have to take the blame:-)
 
@DavidCarlisle I will use that statement in the future
@DavidCarlisle But I'll take a look anyway. Doesn't seem to be too hard to solve
 
2:49 PM
@PhelypeOleinik the second half of the statement I omitted but it's "you can blame @UlrikeFischer instead"
 
@DavidCarlisle I figured it would be something like that ;-)
 
@PauloCereda <3
 
@Rmano <3
 
yo'
3:09 PM
@DavidCarlisle So LianTze just confirmed that we had two templates that showed weird issues all over the place that were solved by changing color->xcolor, so she decided to document it. It probably doesn't hurt, so unless there are objections, we'll keep it that way :)
 
@DavidCarlisle I'm on windows and see only some question marks anyway so don't care much about this ;-)
@yo' well it should perhaps not speak about "the obsolete package color". If some curious template does something that needs xcolor but doesn't load it, it is the template which is to blame.
 
yo'
@UlrikeFischer point taken, we'll reconsider the wording. Thanks!
 
I think (some) Windows terminal does support Unicode characters? Can't remember
 
@UlrikeFischer I believe that the latest windows releases do have a terminal that supports unicode don't they ?
 
yo'
@UlrikeFischer a good question is: is color not obsolate?
 
3:19 PM
@yo' also dvipsnames is my option from color package not an xcolor option (well its an xcolor one as well) so if it's broken I may need to fix something (which is why I asked, really)
 
yo'
@DavidCarlisle ah ok. I'll need to check it tomorrow and might hit you with an email
 
@DavidCarlisle yes, I could change the code page, but I don't really care.
 
@UlrikeFischer we could make all math characters active and map to legacy 8 bit windows code pages so you can read the log file.
 
@DavidCarlisle that is a plan ;-)
 
@yo' its status in 2021 is same as its status in 2020 (and 2010) it's part of the required standard distribution and fully supported, but xcolor has more features and most uses should probably use that in preference. So it's surprising to see it come up in the way described for a tl2021 rollout.
 
yo'
3:26 PM
@DavidCarlisle we're further debugging seeing where this comes from. It seems to be a package interaction actually, so we might be blaming the wrong guy here :D
 
You should have blamed Ulrike
 
yo'
Well, actually after some more testing it seems that we're really mentioning non-sense in this case. We removed the paragraph about (x)color. Thanks everyone! @UlrikeFischer @DavidCarlisle @JosephWright @PauloCereda
 
@yo' <3
 
@yo' thanks (well actually I didn't mind the para, but thanks for telling me that my packages are bug free, as expected:-)
 
yo'
@DavidCarlisle no problem -- happy for you to check what we let out :-)
 
 
1 hour later…
5:02 PM
@JosephWright I am using this answer to display a solution for adding fractions but wondering about an option to convert to a mixed number if that is the case. I'm not sure how to include it. Also, I have it in an align environment but this creates problems when I'm already in an align environment.
 
 
4 hours later…
8:49 PM
Yay got to 750 people on the election page
Next milestone is 1000 people
 
9:07 PM
@JosephWright So my 749 spoofed IP addresses worked as planned.
 
@AlanMunn Must have been a lot of work to create all these accounts :) tex.stackexchange.com/help/badges/183/caucus
 
@samcarter easy for @AlanMunn he has slaves students to do as he commands
 
@DavidCarlisle :D
 
@samcarter Yes, and over a long period of time. I'm clearly playing the long game.
@DavidCarlisle Spoken by someone who's never had to get a student to do something. :) [Not really fair, as I have some great students]
 
@AlanMunn Gaining world tex domination needs careful planning :P
Looks like @JosephWright was the first user to get the caucus badge in the current election - was there insider information involved? :)
 
9:23 PM
 
@samcarter @AlanMunn @PauloCereda Wir haben Deklination! :-)
Comments are still much welcome.
 
@gusbrs Yeah!
 
@PauloCereda I guess I must have missed that memo. :-)
 
@gusbrs Nom nom nom.
user image
2
 
9:26 PM
@samcarter If you feel like it, tell me what you think of it. I did take some different paths that those of frougon. But currently the only dictionary with noum declension is German.
 
Mar 26 '12 at 19:37, by David Carlisle
@Canageek moral of the story: never read the documentation, bad things happen
 
@AlanMunn :-D I'm afraid that might happen.
 
@gusbrs I'd love to take a look. Is it on github or somewhere else?
@DavidCarlisle So writing it should be ok, only reading is the problem
 
@samcarter Yes, I thought you knew since you've starred the repo. :-) But I did make a request for comments here not long ago:
Oct 9 at 12:32, by gusbrs
Hi All! I'm preparing zref-clever for release soon(ish) at https://github.com/gusbrs/zref-clever. If anyone is interested or curious, comments at this point would be very welcome. I still have a lot to do in the area of testing, so it may be a little edgy, but I think it is a fair point for a RFC round.
 
@gusbrs apparently a memory problem - I should try a reboot :) Thanks again for the link!
 
9:34 PM
@samcarter :-)
 
Pupil: Why do I have to learn all this boring grammar? I know how to speak even without knowing the grammar behind it.
Teacher: Do you want to use \zcref when you are grown up?
Pupil: Of course! I learn all the grammar!
@gusbrs ^^^
 
9:50 PM
@samcarter Or Why do I have to write [d=A] when I can just write den. :)
 
@AlanMunn :D
 
@samcarter Also, unlike the Romance languages, wouldn't German generally use a bare plural to refer to things, like English?
 
@AlanMunn I'm definitely the wrong person to ask grammar questions :) I'd like to quote a great mind about this subject
Apr 16 '13 at 16:27, by David Carlisle
@kan Don't learn English (especially English grammar) from an Englishman, we have no idea.
 
10:07 PM
@samcarter That teacher was cheating. You do need to know grammar to use \zcref!
 
A statistical study of licences: arxiv.org/abs/2110.00361
 
@AlanMunn :D Well, you can always fall back to English as well...
 

« first day (4008 days earlier)      last day (41 days later) »