Conversation
|
This looks good, but I'd like to do a cleanup of the Markdown (long paras should be wrapped not broken + other stuff) and implement a build script for making a PDF. I think we should go ahead with pandoc as the default, as we can embed some font and other layout info into the header of the markdown (computer modern is icky). Perhaps we can publish the html somewhere too. Once this is done we should ditch the docx, so we don't get out of sync. Rob? Thoughts? |
|
This looks cool. Happy to leave this to you guys, since I'll be focussing on the v2 release for the next few weeks. My suggestion is that you guys coordinate finishing this off, and just let me know when I'm to switch over from updating the manual in .docx to updating it in Markdown. |
|
Okay -- will do. Try and refrain from editing the manual until I give the word. Or if you do -- let me know! |
|
just made a couple of small edits, but that should be it for now... On 22 November 2016 at 16:37, Brett Calcott notifications@github.com
Rob Lanfear |
|
Andrey : how hard is it for you to regenerate this? (I'm assuming it was done using pandoc). Rob has made a few edits, but also markdown is much nicer in most editors when it is not hard-wrapped. You can use the pandoc option |
|
Sorry for the delay from my side, will do today. |
|
Hi everyone, please make a look at the current version. Besides, paragraph wrapping and some extra polishing I've added the recent PF2 paper - it seems to be the only addition in comparison to the docx version I originally took. Concerning conversions to html and pdf: the main problem seems to be the toc. pandoc uses a different strategy to generate anchors for headers with markup. So, a The github-like feel-and-look is obtained with e.g. grip (which uses github API): |
|
Thanks for doing this -- I'll check this out (probably next week now). |
|
Andrey : sorry again. Due to some issues with the k-means method, Rob has had to pull it from the 2.0 release. That meant he had to go and rapidly edit the manual (before anyone downloaded it). Can you (yet again) regenerate this (assuming it is easy to do). Don't worry about the Toc for now; I shall do that via LaTeX for the manual (in PDF). |
|
And I won't update the manual again for at least a couple of weeks -
hopefully that will give us time to make the transition to the md manual,
and I can do edits in there instead.
Rob
…On 8 December 2016 at 19:59, Brett Calcott ***@***.***> wrote:
Andrey : sorry again. Due to some issues with the k-means method, Rob has
had to pull it from the 2.0 release. That meant he had to go and rapidly
edit the manual (before anyone downloaded it). Can you (yet again)
regenerate this (assuming it is easy to do). Don't worry about the Toc for
now; I shall do that via LaTeX for the manual (in PDF).
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#120 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA2pE7s8ON2TXVS_LHlG5zre5mO2a_nWks5rF8b-gaJpZM4K3Zp7>
.
--
Rob Lanfear
Ecology, Evolution, and Genetics,
The Australian National University,
Canberra
www.robertlanfear.com
|
|
Hi guys, I'm a bit in a Zeitnot again, will have a look in a week or so. |
|
I've just synced the docx and the md versions. gitprint has been repaired, but it ignores any links. |
|
Apologies -- I've dropped the ball on this. Both Rob and I are a bit swamped. It is not forgotten though. I'll chat with Rob soon about merging this in. |
Addresses #113