Skip to content

Manual in md#120

Open
alephreish wants to merge 4 commits intobrettc:masterfrom
alephreish:master
Open

Manual in md#120
alephreish wants to merge 4 commits intobrettc:masterfrom
alephreish:master

Conversation

@alephreish
Copy link
Copy Markdown

Addresses #113

@brettc
Copy link
Copy Markdown
Owner

brettc commented Nov 20, 2016

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?

@roblanf
Copy link
Copy Markdown
Collaborator

roblanf commented Nov 22, 2016

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.

@brettc
Copy link
Copy Markdown
Owner

brettc commented Nov 22, 2016

Okay -- will do. Try and refrain from editing the manual until I give the word. Or if you do -- let me know!

@roblanf
Copy link
Copy Markdown
Collaborator

roblanf commented Nov 22, 2016

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
wrote:

Okay -- will do. Try and refrain from editing the manual until I give the
word. Or if you do -- let me know!


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/AA2pE_h0C4wmHWEiP-y9xZNnl6rQmml5ks5rAn-YgaJpZM4K3Zp7
.

Rob Lanfear
Ecology, Evolution, and Genetics,
The Australian National University,
Canberra

www.robertlanfear.com

@brettc
Copy link
Copy Markdown
Owner

brettc commented Nov 25, 2016

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 --wrap=none to do this I think. There are some odd remaining links in the code to, references to OLE objects...

@alephreish
Copy link
Copy Markdown
Author

Sorry for the delay from my side, will do today.

@alephreish
Copy link
Copy Markdown
Author

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 pandoc MANUAL.md -o MANUAL.pdf -f markdown_github generates a nice pdf, but with some toc entries unclickable.

The github-like feel-and-look is obtained with e.g. grip (which uses github API): grip MANUAL.md --export MANUAL.html. The html version might then serve as the basis for a pdf version, but I have failed to find a converter which would be able preserve the toc (wkhtmltopdf and html-pdf do not support internal links, pandoc fails with an unrelated error [maybe repairable though]). gitprint produces a truncated pdf: https://gitprint.com/har-wradim/partitionfinder/blob/master/docs/MANUAL.md (see adamburmister/gitprint.com#53).

@brettc
Copy link
Copy Markdown
Owner

brettc commented Nov 28, 2016

Thanks for doing this -- I'll check this out (probably next week now).

@brettc
Copy link
Copy Markdown
Owner

brettc commented Dec 8, 2016

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).

@roblanf
Copy link
Copy Markdown
Collaborator

roblanf commented Dec 8, 2016 via email

@alephreish
Copy link
Copy Markdown
Author

Hi guys, I'm a bit in a Zeitnot again, will have a look in a week or so.

@alephreish
Copy link
Copy Markdown
Author

I've just synced the docx and the md versions. gitprint has been repaired, but it ignores any links.

@brettc
Copy link
Copy Markdown
Owner

brettc commented Feb 7, 2017

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants