More Support and Templates in SciFlow

SciFlow is an online editor for academics. They have recently updated and expanded the documentation, so should you ever get stuck, here’s how to. That said, the interface is pretty intuitive, so I’m not sure you’ll ever need to navigate to the support pages for basic editing.

There are some useful hints, though, like using zbib (Zotero) with Sciflow (instructions here). This gets pretty close to Authorea’s citation feature, and is also useful for collaborative texts (and doesn’t suffer from the slowness of direct Zotero/Mendeley connections if you have a large database of references).

The SciFlow team have also recently updated the Templates feature:

There are many journal styles to choose from. It’s not quite (yet) like typeset.io, but the social sciences are not well covered by typeset anyway. SciFlow offers some useful templates, but in most cases, it’s necessary to do some finishing before submitting to a journal. On the other hand, there’s a template for minutes — that’s useful for anyone working in a team, and who isn’t?

In most cases the generic templates will do, including the SciFlow templates which support many common citation styles.

R-Forge: File ‘/pkg/DESCRIPTION’ is out of date

I came across a puzzling “File ‘/pkg/DESCRIPTION’ is out of date” error when updating an R-package of mine on R-Forge today. I was pretty sure the version number and date were correct. I couldn’t figure out any other issue, so I made a copy of my documents, checked out the code again, and copied the modified files back. All worked. I’m still a bit puzzled as I only use one machine for this, but who cares if the code is working…

pandoc-citeproc: “stdin” (line 31, column 2): unexpected “b”

Today I came across the following error in pandox (pandoc-citeproc) that was a bit cryptic to me:

pandoc-citeproc: "stdin" (line 31, column 2): unexpected "b"
expecting "c", "C", "p", "P", "s" or "S"
[...]

When I also got this on an empty text (markdown) file with just a reference in it, I realized that the markdown document was not the problem. Indeed, I had inadvertedly deleted a trailing comma in the bibtex document.

@article{lee
title = {Racial [...]

doesn’t work; it should be:

@article{lee,
title = {Racial [...]

Livecode: write document on Android

Android does not allow apps to write just anywhere as a matter of safety. That’s probably generally a useful feature, but this time I wanted to save data to a text file that is accessible to the user (me). The official guide wasn’t really helpful in this case, because there are ways to save data on Android that are not accessible by the users — e.g. for settings.

Apparently the ‘easiest’ way is to save like this:

set the defaultFolder to specialFolderPath("external documents")
put field "write" into URL ("file:test.txt")

The other (common) special folders (“documents”, “desktop”, “engine”) don’t seem to work on Android.

OK, but where is this file we created? Here:
Local/internal storage/Android/data/com.yourcompany.yourapp/files/test.txt

Not the most intuitive place to me, but whatever, I can access this file from the Android device.