TeX, LaTeX and Friends - 2016-09-07

« first day (2138 days earlier) ← previous day next day → last day (2778 days later) »

5:20 AM

Related to:

15

Q: source of chronic serial upvoting that affects (afflicts!?) some highly-rated contributors

There are some distinguished answer contributors to this site who used to write lots of excellent answers (for which they deservedly got many upvotes and accepts) but who are no longer as active as they used to be. Slowing down a bit and focusing one's energy and attention somewhere else are of c...

discussion up-votes serial-voting

user image

Geez!

user image

That's been the highest reversal to date... perhaps on the entire network?

"Voting corrected" sounds so polite...

5:49 AM

@Werner Wow!

6:15 AM

@Werner Unaccepts as well? Those can only be done by the OP, no bot, right?

@Johannes_B I don't understand those exactly. My guess is they were removed automatically because they met some pattern. But that's bizarre.

It won't be removed by the OP, as they're all done at exactly the same time.

@Werner Do you know if this was all upvotes/accepts from a special timeperiod, i.e. all from x to today?

@Johannes_B No idea. That amount of reputation would span easily a year.

I'm guessing the removal of accepts is actually a mistake (unfortunately).

@Werner I am here for almost three years, and i have just 16k. :-)

@Johannes_B Ha! Exactly... it's a HuGe amount. Epically huge...!

6:22 AM

@Werner :-)

@Werner Maybe @Joseph can ping the SE stuff, if nobody else has already.

@Johannes_B I'm going to ask a question on Meta Stack Exchange, suggesting it's a bug in the design of the serial voting reversal algorithm...

I'm sure there may be the odd case where sock-puppets ask a question which is then answered an accepted by another sock puppet, but I don't think this is the case here.

...let me check...

Two of the posts were from the same user (which is suspicious), but one is from a completely different user, and doesn't seem suspicious.

@Werner I hope it is a bug.

@Werner I think I know what they've done, but obviously I can't say

@JosephWright Sure. Do you think it's a bug in the reversal design?

@Werner No

6:32 AM

@JosephWright Okay.

@JosephWright The suspense of not knowing almost feels like this: giphy.com/gifs/crash-truck-TfUFeB7B5ltKw

6:53 AM

Hello.

I'd like to ask for a bit of help regarding this post:

4

Q: Recursively import sub-document at arbitrary level

Consider the following subimportlevel macro: packages.tex \usepackage{import} \usepackage{coseoul} \newcommand{\subimportlevel}[3]{ \setcounter{currentlevel}{#3} \subimport*{#1}{#2} \setcounter{currentlevel}{#3} } The purpose of the macro is to import a modular piece of a document while gett...

sectioning import

My goal is described in the comments below the accepted answer.

However, here I'd like to ask for a bit of help understanding how the macro given in that answer works.

Here's the macro:

\makeatletter
\newcounter{currentimportdepth}
\setcounter{currentimportdepth}{0}
\newcommand{\subimportlevel}[2]{
  \expandafter\edef\csname @currentlevel\thecurrentimportdepth\endcsname{\thecurrentlevel}
  \addtocounter{currentimportdepth}{1}
  \subimport*{#1}{#2}
  \addtocounter{currentimportdepth}{-1}
  \setcounter{currentlevel}{\csname  @currentlevel\thecurrentimportdepth\endcsname}
}
\makeatother

(hmmm, formatting fail)

Anyway, I'd like to understand the fifth line:

\expandafter\edef\csname @currentlevel\thecurrentimportdepth\endcsname{\thecurrentlevel}

@DanielSank remove the backticks and use the fixed font button on the right (which indents by 4 spaces, and works:-)

@DavidCarlisle nice

@DanielSank it saves the value of the current level:-)

@DavidCarlisle ok ok, I'm dumb. Let's go slow.

So, how does it save that value? :)

@DanielSank one step at a time, hang on....

6:58 AM

What does "save" mean here? I understand regular programming languages, but not LaTeX.

\csname @currentlevel\thecurrentimportdepth\endcsname if expanded once is \@currentlevel3 (if import level is 3) which isn't normally a legal command name

\expandafter expands teh csname once before doing the \edef so your construct is

\edef\@currentlevel3{\thecurrentlevel} (if import depth was 3, and 3 was a legal letter in a command name)

My understanding of \csname is that it allows multicharacter control sequences.

\edef expands the replacement text at the time of the definition so if \thecurrentlevel is 6 this is

...and nonalphabet characters in control sequences.

\def\@currentlevel3{6}

7:02 AM

ok

What is the @ doing?

@DanielSank yes but I was writing \csname abc3\endcsname as \abc3 to highlight that the csname has been expanded so it is now a single token (with a weird name) not a construct that generates

@DanielSank nothing different from the c or the u @ is a letter in package code.

Yeah, hence the \makeatletter

@DanielSank which is implicit in packages.

I'm reading your step-by-step again to make sure I understand.

One moment.

Is @currentlevel3{6} a command name now? In particular, does the {6} mean anything other than a string of characters that comprise part of the name?

@DanielSank if you know c tex is a macro processor, so \def (\newcommand) are more like #define than a function definition.

7:06 AM

@DavidCarlisle I know that much, but I'm not handy on how to reason through \edef and \expandafter. Learning...

@DanielSank no \@currentlevel3 is the command and 6 is its definition. \def\@currentlevel3{6} is \newcommand{\@currentlevel3}{6} (if you assume @ and 3 are letters)

@DavidCarlisle Eurika!

@DanielSank so end result is that it stores the current level in a command generated with a name unique to the current import level

got to go...

Thank you.

1 hour later…

8:26 AM

@barbarabeeton (@JosephWright) I updated code here (you may recognise the extended test example:-)

3

A: Wrong parentheses size in \binom with xelatex and unicode-math in displaystyle

An updated version more closely matching the tighter spacing and larger minimum spce of generalised fraction brackets is given by the following, which may be run with pdftex or xetex, to compare using lm fonts. \documentclass[fleqn,a4paper]{article} \addtolength\textwidth{40pt} \usepackage{am...

@DavidCarlisle :)

@JosephWright got to keep @barbarabeeton happy

8:38 AM

@DavidCarlisle I see we are in agreement about keyvals :-)

@JosephWright I thought you'd like the <> suggestion:-)

@DavidCarlisle I'd go with integrating keyval but if we are going to say 'some things must change', I'd put the brace stripping fix back in and say the problematic packages have to change

@DavidCarlisle Oh yes

@JosephWright incidentally would you use l3keys or keyval or an updated fixed renamed keyval without the compatibility constraints on the current one?

@JosephWright oh you answered the question I was writing.

@DavidCarlisle If we want to go with 'new' code I'd take the l3keys code and decide which bits we want and use that (the base of l3keys has been re-written to be as fast as possible, but it's slower than keyval due to babel safety and 'firmer' space stripping)

@JosephWright in l3 form or back convert to 2e?

babel safety would be good

8:43 AM

@DavidCarlisle I'm working at the mo on the 'higher level' part: aiming to get to about no slower than twice as slow as options (which is clever but not quite what we want)

@DavidCarlisle Unless we are going for something very radical, in 2e (it's largely low-level anyway)

@JosephWright sounds like a plan to me....

@DavidCarlisle The low-level of l3keys is basically keyval but using e-TeX, babel safe, detokenizing key names, stripping all spaces at the ends and always stripping exactly one set of braces [all of this is tested :-)]

@JosephWright ooh testing. It'll never catch on.

@DavidCarlisle Not for some of the people we know

@DavidCarlisle Yes: need to see what Frank thinks (it's quite a policy change)

@DavidCarlisle figured out what we were discussing earlier.

I believe I have accomplished something rather neat.

Demo here: github.com/DanielSank/TeXtricks/tree/master/modularity-demo

What is the best way for me to share this work? The new macro (which I mostly got from here), pulls in functionality from two existing packages coseoul and import. Should I try to get one of those packages to adopt the macro or release an independent one with the other two as dependencies?

8:58 AM

Anybody wanting to upvote the answer at tex.stackexchange.com/questions/199867/… ? The answer is correct but got downvoted for reasons I can't understand. I had already upvoted.

> my question is exactly the same as [blah blah] but the answer there did not solve my problem.

Over at Physics Stack Exchange we'd have closed that immediately.

hmmm, maybe I spoke too soon.

@DanielSank Well, the OP's statement is false; the real issue is that the OP is using the wrong way for making the code to work.

@DanielSank And the self-answer to the linked question is rubbish

Yes I spoke too soon in any case.

No takers on the modularity macro, eh?

::crickets::

9:48 AM

@DanielSank either way works, no harm in asking the maintainers of the original code first.

10:17 AM

@DavidCarlisle I'm a bit new to this. On github I would file an issue or a pull request. On CTAN there doesn't seem to be any way to contact package maintainers. Am I missing something?

@DanielSank Have a look in the documentation of the package, email addresses are often listed there.

@TorbjørnT. Ah. coseoul didn't have one, but import does.

@DanielSank no you need to look into the package documentation, normally there are some contact details, sometimes those details are from this century and still work.

Before I bug this person, is it reasonable to propose adding a macro to package A if that macro depends on package B, while A doesn't normally depend on B?

I have no idea how package managment/dependencies work in TeX. This is my first rodeo.

@DanielSank There's none. :)

10:22 AM

@DanielSank it's reasonable to propose anything (but it's also reasonable for the propsal to be rejected on those grounds)

@PauloCereda Oi texlive team would be offended by that:-)

@DavidCarlisle Alright, well if I could do anything I'd put my macro in coseoul, but the author thereof has a common name and no contact details provided.

@DavidCarlisle oh I meant the language, not the underlying system. <3

@DanielSank I see that the author of coseoul is a user at the site, Tom Bombadil. (See meta.tex.stackexchange.com/questions/1721/…)

@PauloCereda Thanks for the vote! I guess it was yours.

@DanielSank I'd never heard of that package but just looked, it's 39 lines long (and could be much shorter) probably less charaters needed just to incorporate the logic in your code than to mail the original author and ask for an update.

10:25 AM

@DanielSank It originated from tex.stackexchange.com/questions/26181/…

@egreg hmmm I am lost now. :) What did I do?

@TorbjørnT. cool!

@PauloCereda prime suspect when it comes to upvotes

@PauloCereda Oh, I guessed wrong.

@egreg what happened? :)

10:26 AM

@DavidCarlisle Well yes, I can solve the problem for myself just fine. I am more interested in disseminating useful code, however.

@egreg The one you asked for earlier? Guilty.

@TorbjørnT. Thanks! Another question off the unanswered list

@egreg ooh now that @TorbjørnT. mentioned it, I upvoted it too! <3

@PauloCereda I miss Harish and Gonzalo

@egreg Me too. :(

10:29 AM

@DanielSank I meant in code you distribute, you are free to just include modified version of the existing package code rather than have a dependency on another package. (it's LPPL licenced)

@DavidCarlisle Ah. Yes that would be a solution, although I'd rather not violate the DRY principle. I have left a tex.SE comment such that the package author should get a ping. Thanks for the info @TorbjørnT.

@DanielSank yep I wrote that before you'd located the author:-)

@DavidCarlisle Thanks again for the help understanding the macro. I made a small tweak and now all my problems are solved. Modular documents for everyone!

@DanielSank if only @PauloCereda's thesis had some text he could modularise it:-)

@DavidCarlisle Oh, is someone here nearing a PhD graduation?

That's exciting.

10:39 AM

Jan 12 at 12:15, by David Carlisle

@PauloCereda finished your thesis?

@PauloCereda Advice on writing a dissertation: you will never finish it. You will, at some point, abandon it.

Simply decide as soon as possible when you will abandon it, and then just work until that time.

@DavidCarlisle oy

@DanielSank There's no end for research, actually. :)

@PauloCereda Indeed not, but one can be fooled into thinking a PhD dissertation does have a sort of satisfying end.

@DanielSank My plan is to survive it. :)

@PauloCereda Yes. Very good.

10:44 AM

@DanielSank It involves procrastination. :)

@PauloCereda Subject?

@DanielSank Abstractions, macro expansions, self-modifiying code, context-dependent grammars. :)

@PauloCereda So, programming languages, to put it broadly?

@DanielSank A little more general. :)

@PauloCereda ah.

10:49 AM

@DanielSank :)

11:05 AM

Yay it's holiday today!

11:24 AM

\makeatletter
\protected\long\def\Ksetkeys#1#2{%
  \def\KV@prefix{KV@#1@}%
  \def\@tempa{#2}%
  \def\@tempc{}%
  \KKV@sanitise@equals
  \KKV@sanitise@comma
  \expandafter\KKV@loop\expandafter\q@mark\@tempa,\relax,%
}
\begingroup
  \catcode`\, = \active
  \catcode`\= = \active
  \protected\long\gdef\KKV@sanitise@equals{%
    \expandafter\KKV@sanitise@equals@\@tempa\q@mark=\@nil=%
    \expandafter\KKV@sanitise@\@tempa
  }
  \protected\long\gdef\KKV@sanitise@equals@#1={%
    \edef\@tempa{\unexpanded{#1}}%

@DavidCarlisle ^^^

@DavidCarlisle If we go for this, I'd be tempted to keep \trimspaces of some sort as expl3 and use the 'know the internals' trick I do in l3keys for speed

@DavidCarlisle Above code is basically l3keys/keyval merge: hard-coded place for the keys, and assuming we share the keys themselves. I might have the default value bit wrong ...

1 hour later…

12:38 PM

@JosephWright other issue of course is if we care about non-etex, I think currently the format still builds with tex2, certainly it tries with \ifx\@undefined\language \newcount\language \fi It would probably be OK though to say if you don't build on etex you can't use the optional argument

@DavidCarlisle You can probably guess my view here

@DavidCarlisle Note that some of the hyphenation patterns do assume e-TeX: realistically it's extremely unlikely anyone has a format that is kept up-to-date but which doesn't have the extensions

@JosephWright similar to third starred comment on the right?

@DavidCarlisle I think the team said e-TeX was assumed before I started using LaTeX

@DavidCarlisle Really, all of that should go

@DavidCarlisle Yup

@JosephWright tex2 support could probably go, but even the new allocation code added last year checks for etex and keeps below 255 in classic tex...

@DavidCarlisle As I've said to Frank, if we don't want to find ourselves strangled by 'stability' we have to ask some people to change some stuff

@DavidCarlisle Yes, I know

@DavidCarlisle But try actually building a format outside of the testing sandbox

12:49 PM

@JosephWright yes I know it dies in hyphenation (I tried a while back:-)

@DavidCarlisle My point being how many users do we really have who might get "LaTeX2e 2017" but don't have e-TeX

@DavidCarlisle Anyway, first we have to agree a plan more generally

@JosephWright oh none, most likely.

@DavidCarlisle Only one way to really find out ...

@DavidCarlisle Frank probably regrets asking me to join the team, sometimes :-)

@JosephWright probably:-)

@DavidCarlisle Other issue is do we simply superset keyval or use a separate set of keys or ...? I'd favour not making even more packages!

@DavidCarlisle :)

@DavidCarlisle Everyone else probably wonders what we are on about!

1:04 PM

@JosephWright Planning for a better future, I suppose.

@JosephWright Fixing stuff? :)

Stuff that @DavidCarlisle broke.

1:19 PM

@JosephWright just tell them it's cricket, they won't know the difference

@PauloCereda no planning to break stuff

@DavidCarlisle oh

1 hour later…

2:41 PM

@DavidCarlisle I see no cricket bat, so it can't be.

@egreg look at the image to the left of the previous comment: the duck has the bat.

3:13 PM

@DavidCarlisle :)

3:24 PM

I suddenly can't compile xelatex in TexWorks? xelatex.logcontains FATAL xelatex - Source: libraries\miktex\texandfriends\include\miktex\c4p\C4P.h. an update did not help

3:38 PM

@cfr I deleted most of my side of our cross chat under the X question, probably confusing for the OP:-)

@egreg see you put Bruno out of his misery. I wonder what he was trying to do:-)

@DavidCarlisle Trying to break LaTeX, undoubtedly

@egreg quite successfully:-)

@egreg I even voted for you

@DavidCarlisle It's fixing a missing %, in some sense

@egreg well naturally, as you could answer it.

@DavidCarlisle :P

4:02 PM

Holiday!

@PauloCereda not for students, they have to work on their thesis, even on national holidays

@DavidCarlisle oh no

@PauloCereda it's either that or go to Rio to support team GB in the para-olympics

@DavidCarlisle Yay GB!

That makes me a Englishduck? :)

Jul 20 '12 at 12:26, by Paulo Cereda

I want to be German.

4:11 PM

@DavidCarlisle Oh

Do you have those links on an emacs buffer? :)

user image

@PauloCereda I do now

@DavidCarlisle oh my

@PauloCereda the things you make me do, lynx in emacs terminal in X in cygwin running with windows as the X window manager...

2

@DavidCarlisle Oh my!

@PauloCereda it does work though:-)

4:19 PM

@DavidCarlisle Surprisingly. :)

4:44 PM

@DavidCarlisle Windows is getting BASH so soon you'll be able to drop Cygwin at least.

So, my boss wants me to switch from micromoles to millimoles. I'm wondering if it is possible to abuse siunitx to do that conversion automatically.

Also if I should instead covert everything to hogsheads and butts as a joke

@Canageek I suppose not, but it's not so difficult to at least find all occurences when you use siunitx

@yo' by searching for every 'mole' yes

@yo' I use "\SI" 200 times in this document

@Canageek that's not so much, about an hour or two of work.

@yo' I'm currently taking the "pretend I forgot to make that change and see if he notices" approach

@Canageek :)

4:58 PM

Right now I'm changing all mentions of "To a solution of \nau\ (\SI{3}{\milli\litre}, \SI{50}{\milli\gram}, \SI{100}{\micro\mole})" to "To a \SI{3}{\milli\litre} solution of \nau\ (\SI{50}{\milli\gram}, \SI{100}{\micro\mole})"

5:09 PM

@Canageek I doubt it (although we'll see) I need rather more than just bash, X for example.

@DavidCarlisle I'm betting someone will compile it against windows soon

@Canageek Surely there's something wrong here!

@JosephWright Oh? What am I missing?

@JosephWright Oh, I should have a solvent in there

@Canageek oh no

(I have no idea of what that means, I just want to join the conversation)

@JosephWright Ok, checked the text, it is inthere in the actual version

5:44 PM

@Canageek The values must change if the unit prefixes do: 100 mmol = 100000 um

@JosephWright Yes. Here I wasn't changing the values or prefixes, just moving from "To a solution of X (Y mL, W mg, Z umol)" to "To a Y mL solution of X (W mg, Z umol)"

6:28 PM

@PauloCereda spacemacs.org

@PauloCereda Perhaps you and @DavidCarlisle can finally agree on an editor ;)

user image

@HenriMenke I have it here. :) But I use vim. :)

@PauloCereda I actually use both. Emacs for TeX and Lua, Vim for C++ and general editing on the command line.

Efff

Trying to figure out how ACS wants this thing cited is a pain.

@HenriMenke Cool. :) Once in a while, I edit a paper in TeX using spacemacs. :)

I like the vim key bindings. :)

Trying to figure out how to cite link.springer.com/chapter/10.1007%2F3-540-11454-8_4 if anyone has a moment to help

6:32 PM

@PauloCereda You can also have Vim binding with normal Emacs by installing evil mode.

@HenriMenke No thanks. :)

@Canageek Why not click »Export Citation«?

I thought it would be as "incollection" but that gives the "Booktitle" and Series, but not the actual title

@Canageek I use inbook, I guess.

@PauloCereda Well, evil mode is what's being used behind the scenes in Spacemacs.

6:33 PM

@HenriMenke plus space. :)

@PauloCereda That doesn't give the imporant title (Uranyl Photophysics). It is identical to "incollection"

It gives the Booktitle (Top. Inorg. Phys. Chem.) which is nondescriptive. and the series title (Structure and Bonding)

@Canageek Sorry, it was just a guess. I always get the correct output. So the only thing I can think of is that the style you are using is the one to blame.

But not the title of the chapter (Uranyl Photophysics)

@PauloCereda Blame @JosephWright who wrote the style, got it ;)

@Canageek :)

@PauloCereda I'll make a question about it, since I think this is wrong. I think this counts as "Series publication cited as a book"

6:52 PM

@Canageek It's @inbook or @incollection, doesn't quite make a difference

and actually, the default export makes sense:

@Inbook{Jorgensen1982,
author = "J{\o}rgensen, Christian K. and Reisfeld, Renata",
title = "Uranyl photophysics",
booktitle = "Topics in Inorganic and Physical Chemistry",
year = "1982",
publisher = "Springer Berlin Heidelberg",
address = "Berlin, Heidelberg",
pages = "121--171",
isbn = "978-3-540-39082-4",
doi = "10.1007/3-540-11454-8_4",
url = "http://dx.doi.org/10.1007/3-540-11454-8_4"
}

Of course, it's wrong to list both Berlin and Heidelberg, but ...

If it turns out wrong in some particular style, you can tweak things easily, depending on what's wrong

7:07 PM

@Canageek Top. Inorg. Phys. Chem. is a journal

@JosephWright It claims to be a book series

@JosephWright no, according to Springer

@Canageek Yes, but things like Annual Reviews also get cited as journals

@yo' Not their call ;-)

@JosephWright sorry, but with my copy editor hat on, it is their call.

@JosephWright I think the problem is that I am using title and should be using something specific for chapter title

7:10 PM

@JosephWright individual books have ISBN and the series hasn't got an ISSN, this is not a journal by any standard, sorry.

@yo' I want a hat too

user image

@yo' Org. Synth. certainly used to like a book but has always been cited as a journal

@yo' oooooooooh

@JosephWright Org Synth has a specific exception in the ACS Style Guide

@JosephWright Posted Q with MWE and everything

0

Q: Use of incollection style with achemso citation style

I'm trying to cite a chapter in a book, in a series. Specifically, Uranyl Photophysics by Jørgensen and Reisfeld Based on Chapter 14 of the ACS style guide (pg 242, 306 "Series publication cited as a book", see "As for any book, you may cite specific chapters") I think this should be cited as: ...

7:12 PM

@Canageek Probably

Have to go to lunch before my better half murders me >.>

@Canageek If you are citing as a book you shouldn't abbreviate the title :-)

@JosephWright Ok, I can fix that.

@Canageek Other than journals, it's actually pretty hard to be sure what the editorial office will do with anything :)

@JosephWright But I need the chapter title to make it obvious why I'm citing it to my boss ;)

7:14 PM

@Canageek I've had an update for achemso today: I've never had anything from the ACS about the BibTeX styles other than adding article titles/DOIs (both increasingly common)

@Canageek Ah, that's an issue: 'in' entries don't have the chapter title in ACS style

It says you can. Page 306, chapter 14. "As with any book you may include chapter titles"

@PauloCereda I have a hat for you:

@Canageek Might well do, but I've worked from what they actually do on average

It has an example and everything

user image

7:16 PM

@DavidCarlisle LOL

@Canageek Yes, I know: the style guide leaves various things open, but that's hard to cover in a BibTeX style (and the aim for achemso is primarily matching publications)

@Canageek For the biblatex style, I have an option to have chapter titles present

Can I submit that for publication?

@Canageek No

@Canageek Or rather it's not officially supported!

Well that isn't very helpful

@Canageek The ACS don't really care as such: they work from the PDFs

@Canageek For publication they'll take the chapter titles out: they don't actually use them (which is why achemso doesn't include them)

7:20 PM

Why do they even have a style guide then?

@Canageek Well it's a guide, like it says :-) It applies to all sorts of chemistry, not just publication via the ACS

@Canageek The editorial offices are something of a law unto themselves

Man, if I were an editor I'd probably have great fun rewriting the style manual to match my tastes

@Canageek Please don't

@Canageek As it is there are changes ongoing: Inorg. Chem. apparently want article titles and DOIs for all entries (email today)

They tweeted that a while ago, didn't they?

It was added to their style manual about 6 weeks ago

(has a talk with my boss about that yesterday)

@Canageek Possibly

7:27 PM

If I had that much power the ACS would switch to the RSC citation order ;)

@Canageek I work from published papers, so such things don't tend to feature unless the ACS tip me off

@Canageek Oddly, so would I

@Canageek RSC have much more a single approach across journals

Engineers got it right- one standard for all publications advertised publishers

To bad it is a bad one

@JosephWright So how do you establish a large enough corpus of the weirder citations like inbook?

7:43 PM

@DavidCarlisle Do you have the link?

@JosephWright I prefer their italics and name order

@JosephWright Nope. If I were in charge all journal names would be in ISO 4 format, no exceptions. I'm looking at you CrystEngComm. glare

@JosephWright Ok, solution: I'll add an addendum to my boss with the chapter title. Achemso supports that, right

@JosephWright Wait, this doesn't even have an "in" before the book title. I'm SURE I've seen that in ACS journals.

@DavidCarlisle OK. Never mind. I found it again. But why would the X get into that position if it was replacing the summation sign?

0

Q: Sum-sign and minus-sign not showing correctly

I am having trouble with the sum sign. It just shows as an X. Also the minus sign is missing. See picture below. This is my code: \documentclass{article} \begin{document} \begin{equation}\label{eq8.1} NPV = \sum_{t=1}^{T} \frac{C_t}{(1 + r)^t} - C_0 \end{equation} \end{document} Can anyo...

8:01 PM

@JosephWright There, I added examples from an ACS journal. Now looking for ones specific to Cryst. Growth. Des.

@Canageek I guess!

@Canageek Take a look for example at the biblatex-chem ones for Houben-Weyl

@JosephWright ?

@Canageek How many times do people cite Houben-Weyl? (Now called 'Science of Synthesis' but I know the older, German, volumes better)

@JosephWright Ug, it seems IC and Cryst Growth Des do it totally diffrently

@Canageek Probably: Cryst Growth Des is I think one of the more awkward ones for me

8:14 PM

@JosephWright HAH!

Found an ACS with a chapter title

@JosephWright "Balzani, V.; Credi, A.; Venturi, M. Molecular Devices and Machines. Concepts and Perspectives for the Nanoworld, 2nd ed.; Wiley: Hoboken, NJ, 2008" They don't use the 'In" for some reason though. (Citation was in JACS)

@JosephWright Both IC and CGD put an "In" before the booktitle though, which achemso does not though.

@Canageek When in doubt, JACS is the model

@JosephWright That has the chapter title.

@Canageek As far as I know, none of this is automated so it is actually pot-luck

@cfr well the summation is a mathop so shifted to be vertically centred the X is a different font and a different size but probably shifted by the same amount, so just random breakage really

@JosephWright I also found an IC with a chapter title, but it is from 196

8:19 PM

@DavidCarlisle Oh, random breakage. OK. I can understand that ;).

@JosephWright So I've found 3 styles, but none of them match the output of achemso, so, not sure what that means

@JosephWright Is there a way to make my addendum show up? (For example, when citing the CSD database I need to specify what version)

@Canageek That would be a misc entry so done entirely by hand

@JosephWright They have a paper you are supposed to cite though.

@Canageek What I mean is that other than journals (where things are broadly consistent), one can probably find pretty much any formatting that vaguely matches the style guide. So I had to pick something.

@Canageek Yes, but normally the citation would be for using the database and a ref. to the version would go with 'X hits' or whatever, i.e. two separate references

@JosephWright Ah. They seem pretty consistent on there should be an "In" before the book name though, which would at least make it clear I'm citing a chapter.

@JosephWright OH. OK, I can do that.

8:28 PM

@Canageek This may have changed a bit of course over the past few years

C-C-C-C-C-COMBO BREAKER!

@Canageek Broadly, I have agreement with the ACS that I don't change achemso unless they ask

@JosephWright Damn.

@Canageek Not a hard-and-fast rule, mind

@JosephWright To bad we didn't talk yesterday so you could have slipped it in with today's entry.

8:30 PM

@Canageek OOh, now I remember: there is an option for chapter titles :-)

@JosephWright !!!

So would the CSD citation be just "@misc{CSD,
addendum = {CSD Version 5.37 (November 2015) + November 2015, Febuary 2016, and May 1016 Updates}
}"

@Canageek I think the field is note, but other than that looks about right to me

@JosephWright Do you recall what it is?

@Canageek chaptertitle

@JosephWright Thank you.

8:33 PM

@JosephWright inbook has it!

That's what I use.

@JosephWright Doesn't work.

Is there a diffrence between inbook and incollection?

@Canageek Ah, there might be

@Canageek I'm off to bed in a sec but I'll look again at this tomorrow

@JosephWright I've tried both. OK, thanks.

@JosephWright ooh timezones

9:12 PM

@Canageek texdoc tamethebeast, go to the bottom of page 14

@Canageek The main difference is that an @incollection item has its own title, whereas an @inbook item doesn't.

9:45 PM

Effff

For some reason now I have to remove the \setkeys{acs}{articletitle = true,doi=true} or my document won't compile. *Glares at @JosephWright *

« first day (2138 days earlier) ← previous day next day → last day (2778 days later) »

Transcript for

Sep '167

$TeX - LaTeX$ TeX, LaTeX and Friends

\begin{chat}

join this room
about this room

00:00

06:00

12:00

18:00

all times are UTC

$TeX - LaTeX$

site design / logo © 2024 Stack Exchange Inc; legal

mobile