Made the changes you suggested and a few other small tweaks. There's still one outstanding issue with this template: it produces a pdf that looks right, but is not suitable for submission (because it's not in the right format).

I think the easiest way to do this is to have two output formats: one for previewing and one for submitting. Do you think rjournal_preview() and rjournal_submit() are reasonable names for these? The main difference is that submit would create a tex file, and preview a pdf.

We also need some way of templating skeleton files - i.e. RJwrapper.tex needs some way of being updated with values from the yaml metadata. Maybe I should just hook into pre_processor?

I think those are good names for the different formats.

In terms of templating skeleton files, if you suggest a general approach to
this (e.g. based on whisker) I'd be happy to implement it.

On Tue, Apr 15, 2014 at 3:09 PM, Hadley Wickham [email protected]:

Made the changes you suggested and a few other small tweaks. There's still
one outstanding issue with this template: it produces a pdf that looks
right, but is not suitable for submission (because it's not in the right
format).

I think the easiest way to do this is to have two output formats: one for
previewing and one for submitting. Do you think rjournal_preview() and
rjournal_submit() are reasonable names for these? The main difference is
that submit would create a tex file, and preview a pdf.

We also need some way of templating skeleton files - i.e. RJwrapper.texneeds some way of being updated with values from the yaml metadata. Maybe I
should just hook into pre_processor?

Reply to this email directly or view it on GitHubhttps://github.com//pull/2#issuecomment-40521466
.