Post release updates

[cysouw]

I read the book and found all kinds of small errors, which I have corrected here. Please have a look and when acceptable, let's make this version 2.0.2 :-).

Should we also push an update to langsci?

Michael

[bambooforest]

@cysouw - but not Unix -> Linux at the end of the paragraph?

[bambooforest]

@cysouw there's an opening <}> here, which stops main.tex from compiling.

[bambooforest]

@cysouw - no British English spelling ("behaviour") -- it took me a long time to get the book consistently American English spelling :)

[bambooforest]

@cysouw -> canonically equivalent

[bambooforest]

@cysouw -> canonically equivalent

[bambooforest]

@cysouw -- looks good! a few small comments in my review. please fix.

[cysouw]

All fixed; Xelatex/Knitr compilation successful. I let you do the merge and the version change :-).

How does it work now to push these changes to the language science press?

[bambooforest]

@cysouw looks good. I also update the PDF in the main directory and then push a new version tag and a new Zenodo release. I'm not sure about LSP -- we'll have to ask Nordhoff, who is on holiday at the moment.

[bambooforest]

@cysouw -- I'm still not getting the latex to compile without error, specifically anywhere you use this type of construction (Undefined control sequence error):

\hlstd{}\hlslc{#\ get\ the\ paths\ to\ the\ R\ executables\ in\ bash}\hspace*{\fill}\

[cysouw]

hmmm, I don't use that, it is knitr who is producing those sequences :-(.

Does it stop compilation at your side? because at my side it just completed compilation (though I didn't check all errors in the latex-log....). It also looks good in the resulting PDF here.

I used the TexLive-2018 version for Xelatex-compilation

[bambooforest]

it knits fine, just fails to compile main.tex without being forced to in xelatex in TexShop using this installation.

http://www.tug.org/mactex/

i'll look into it, but also look at page 107 where one of the errors is occurring:

the alignment of the code is off:

get the paths to the R executables in bash

pathT=Rscript -e 'cat(system.file("exec/tokenize", package="qlcData"))'
pathW=Rscript -e 'cat(system.file("exec/writeprofile", package="qlcData"))'

make softlinks to the R executables in /usr/local/bin

you will have to enter your user's password!

sudo ln -is $pathT $pathW /usr/local/bin

could you please try to fix the alignment? not sure if the two issues are intertwined.

[cysouw]

fixed the alignment.

I now see the errors in latex as well: however: the end result is exactly what I expected, so I would simply ignore the errors :-). It is probably related to how knitr deals with bash-code.

[bambooforest]

@cysouw -- just a clarification please. where this fails to compile, these commands are meant for the user to run them (once) on the command line, or? e.g.

# get the paths to the R executables in bash
   pathT=`Rscript -e 'cat(system.file("exec/tokenize", package="qlcData"))'`
   pathW=`Rscript -e 'cat(system.file("exec/writeprofile", package="qlcData"))'`

in that sense isn't a bit weird to have a comment before them? that would suggest, at least to me, that these codes chunks are meant in a bash script, instead of commands that should be fired off from the terminal. if that's the case, we can just incorporate the command line comments into the text -- and have no problems with knitr and latex :) (sorry -- i really want this thing to compile without error.)

[cysouw]

OK, try it again.

[bambooforest]

Done. Thanks!