@StefanKottwitz Getting a general error visiting LC: Illegal use of $_COOKIE. You must use the request class or request_var() to access input data. Found in /usr/local/www/lc/forum/includes/hooks/index.php on line 1. This error message was generated by deactivated_super_global.
@UlrikeFischer yes but it doesn't work and Will said last night he was planning to switch to using the formats \UndeclareTextCommand or something wrapping that, I'll ping you if there is anything to test
@Kurzd it's a generic word, you see the same in "package managers" for texlive and miktex or linux distributions, for all of those "package" is a collection of files that are distributed together even though it may contain several (or no) latex packages.
@Kurzd ctan is older than latex2e (which introduced the word package to latex, previously, in latex 2.09, .sty files were called style files hence the sty extension)
@DavidCarlisle good, it is usefull some times. But naturally doesn't solve the problem that with unicode fonts the definitions don't depend only on the encoding but on the font.
Good morning. I hope you don't mind to ask me a question again. I get an error if I write \SI{10^{-1}}{\nano\meter^{-1}} for the power in the number value. (Of course \SI{0.001}{\nano\meter^{-1}} works).
@Gudrun siunitx can handle units in two ways. The first is that you type in something to typeset and that's what you get: I call that 'literal' mode, something like \si{nm^{-1}. The alternative is to use symbolic markup: \si{\per\nm}, which might come out as /nm or nm^{-1} or \frac{1}{nm}, depending on your settings
@PauloCereda Typical pompous technical jargon: apart from “Goals” which should be “Obiettivi”, one can remove at least ten words from that paragraph, making it clearer and smoother.
But I think I was not completely right about it yesterday. I thought I had seen this in children's' text somewhere but I could not find it anywhere. The t+caron and d+caron variants might not be used in children's texts after all.
@wilx I tried sending the following message and, apparently, it went through, because I received the copy back in my mailbox
While claiming complete support for Central European languages, the Andika New Basic font lacks U+0165 (LATIN SMALL LETTER T WITH CARON) and U+010F (LATIN SMALL LETTER D WITH CARON).
Both are present in the old version.
It would be even nicer if the font provided a stylistic set for choosing between the form of the caron: as far as I know, primary school textbooks in the Czech Republic use the ˇ form also for these glyphs.
How in their right mind would directly email class maintainers for help with stuff completely unrelated to the class the person maintains. I'm just why....
@JosephWright and I immediately remembered a minor issue that I'd liked to have looked at (if a note is long, and the font size is, say, tiny, then the line spacing is not even). Though this might be an artifact from marginnotes
@PauloCereda An Italian comedian performed a character who was some kind of freak preacher and always ended with “the answer is within you, but it's wrong”.
@Kurzd it's only a name:-) historically they are first of a month, although have usually been exceptions "date of release" is a bit arbitrary and hard to fix in advance, it could mean "date we freeze the code internally for testing and packaging" or "date we push to ctan" or "date texlive pulls from ctan and pushes to users" these can easily be a week or so apart, and it's easier to remember first of year, if you need to roll back a document with \RequirePackage[2017/01/01]{latexrelease}
@Kurzd I've been using LaTeX2e <2017/01/01> since November (according to that change log)
@DavidCarlisle Actually, 2016-09-15 David Carlisle <latex-bugs@latex-project.org>. I also saw re-instate the old 2014 version of fixltx2e.sty protected by \IncludeInRelease guards in the changelog for this version. I thought distros from 2015 onward didn't need the user to load that package on every document.
@Kurzd they don't but currently if you (or say a preprint archive) wants to process a document as if it was 2014 you can add \RequirePackage[2014/01/01]{latexrelease} to the document then latex will undo all its changes, but if the document has \usepackage{fixltx2e} in 2014 it would have loaded fixes but in 2016 latex fixltx2e package does nothing, in 2017 fixltx2e detects this and does the fixes it used to do
