Just one day before the final paper deadline - does anyone have a good
suggestion on how to control the size of images in the output?
Currently the images are made as wide as the page is, resulting right now
in my paper with two pictures taking up a page each in the pdf output. The
html output seems to take the images at a reasonable size (how large the
images actually are).
sincerely,
Marije
On Fri, Dec 12, 2014 at 8:43 PM, alex <alex_at_slab.org> wrote:
> Hi all,
>
> Thanks for the feedback. I decided that championing markdown too much
> might put off some people less familiar with commandline tools, so I
> think I will keep with a word document as a first option, and a
> markdown template for the adventurous. We can still have HTML online
> for markdown users, but make a bit less of it, at least for this first
> year.
>
> Pandoc needs LaTeX installed in order to make PDFs, I'll make that
> clear in the template, but there are instructions here:
> http://johnmacfarlane.net/pandoc/installing.html
>
> By the way I toyed with a two column layout, which looks much better,
> but doesn't work well for code examples.
>
> I've been ill for a couple of days, but hope to have all this
> finalised ASAP.. Sorry for the delay!
>
> alex
>
> On 10 December 2014 at 19:58, David Ogborn <ogbornd_at_mcmaster.ca> wrote:
> > Hi Alex,
> >
> > Thanks for doing this - I think it's a good idea.
> >
> > It might be worth adding these OSX installation instructions to help new
> people on that platform:
> > install homebrew: ruby -e "$(curl -fsSL
> https://raw.githubusercontent.com/Homebrew/install/master/install)"
> > use homebrew to install pandoc and pandoc-citeproc: brew install pandoc
> pandoc-citeproc
> > install MacTeX from http://www.tug.org/mactex
> > make sure pdflatex can be found: echo "export PATH=/usr/texbin:$PATH" >>
> ~/.bash_profile
> >
> > Other than that, seems straightforward to me!
> >
> > Yours truly,
> > David
> >
> > On 2014-12-09, at 6:27 PM, alex wrote:
> >> Hi all,
> >>
> >> I got some enthusiastic responses to the idea of providing markdown
> templates for the live coding conference. This would make it
> straightforward to produce the proceedings in a form designed for the web,
> as well as print, which is a major plus.
> >>
> >> However, so far I've had less enthusiasm for testing out the templates
> I've now made. Maybe I'm asking the wrong questions.. But I need some help!
> >>
> >> Here's what I have so far:
> >> https://github.com/livecodenetwork/iclc/tree/master/templates
> >>
> >> You can download as a zip here:
> >> https://github.com/livecodenetwork/iclc/archive/master.zip
> >>
> >> Please consider them alpha, I'm not confident on releasing them as they
> are.
> >>
> >> If you can spare some time trying out the markdown template and letting
> me know:
> >>
> >> - If you're new to markdown, does this make sense? What's unclear and
> what would help to make it clearer?
> >>
> >> - If you're experienced with markdown, how does this fit with your
> expectations? What editor / workflow etc would you recommend a beginner?
> Any websites that helped you learn?
> >>
> >> If there's less interest than I thought, I'll revert to the usual PDF
> only approach via the usual conference Word and LaTeX templates that get
> passed around. If you'd actually prefer that, let me know as well.
> >>
> >> Cheers
> >>
> >> alex
> >>
> >> --
> >>
> >> Read the whole topic here: livecode:
> >> http://lurk.org/r/topic/3sihU8SYCFMndRf3gUp9SK
> >>
> >> To leave livecode, email livecode_at_group.lurk.org with the following
> email subject: unsubscribe
> >
> >
> --------------------------------------------------------------------------
> > Dr. David Ogborn, Associate Professor, Multimedia
> > Acting Chair, M.A. in Communication & New Media
> > McMaster University, Hamilton, Ontario, Canada
> > +1-905-525-9140 ext 27603 http://www.d0kt0r0.net
> >
> >
> > --
> >
> > Read the whole topic here: livecode:
> > http://lurk.org/r/topic/4JAQ4gvSTGATNBSOzQWogA
> >
> > To leave livecode, email livecode_at_group.lurk.org with the following
> email subject: unsubscribe
>
>
>
> --
> http://yaxu.org/
>
> --
>
> Read the whole topic here: livecode:
> http://lurk.org/r/topic/G34vTgCYXTbVUjF6x5pIL
>
> To leave livecode, email livecode_at_group.lurk.org with the following email
> subject: unsubscribe
>
--
Read the whole topic here: livecode:
http://lurk.org/r/topic/4yLaFyYH92xKqVnBsQhbfN
To leave livecode, email livecode_at_group.lurk.org with the following email subject: unsubscribe
Received on Sat May 09 2015 - 17:51:16 BST