From mboxrd@z Thu Jan 1 00:00:00 1970 From: Juan Reyero Subject: Re: Writing your book with orgmode and publishing it on Leanpub Date: Mon, 24 Feb 2014 09:33:54 +0100 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:40094) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WHqz7-0001l4-Nk for emacs-orgmode@gnu.org; Mon, 24 Feb 2014 03:33:58 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WHqz5-0005Fb-PK for emacs-orgmode@gnu.org; Mon, 24 Feb 2014 03:33:57 -0500 Received: from mail-qc0-x22e.google.com ([2607:f8b0:400d:c01::22e]:38607) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WHqz5-0005FW-Kz for emacs-orgmode@gnu.org; Mon, 24 Feb 2014 03:33:55 -0500 Received: by mail-qc0-f174.google.com with SMTP id e16so1637222qcx.33 for ; Mon, 24 Feb 2014 00:33:55 -0800 (PST) In-Reply-To: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Waldemar Quevedo Cc: org-mode Mailing List On Mon, Feb 24, 2014 at 8:39 AM, Waldemar Quevedo wrote: >> It is rather annoying that github understands the org syntax but not >> quite, so the sources appear almost but not quite right. > I maintain the parser that is being by Github => > https://github.com/wallyqs/org-ruby > If you let me now the issues I can try to fix them, (or PRs are also > welcome).... Sorry I sounded dismissive. You are doing an awesome job, it's amazing how much it did get right. My problem is that I am trying to share my sources as code, not as documentation. I would like my .org files to be treated as you would treat Python code, shown as they are and syntax-highlighted. If you parse them you will inevitably miss the context I am relying upon to render them properly (like when you ---rightly--- assume that html should be left standing, but what I wrote expects a jekyll post-process). People visiting the repository will most likely be interested in what I actually wrote, not in its rendering as a document. Close to what you get when you select Raw, but syntax-highlighted. This is what I want the repository for; the document is somewhere else. That said, the one place where the translation fails is when the source code of babel snippets should not be exported. Again, probably due to the tension between the need to show the file's content and the desire to render it as a document. > I have this example > where you can use `#+layout:` instead of YAML. > https://github.com/wallyqs/yet-another-jekyll-org-template > https://github.com/eggcaker/jekyll-org/blob/master/convert.rb#L30 Thank you for the pointer. Best, jm > On Mon, Feb 24, 2014 at 4:24 AM, Juan Reyero wrote: >> >> Greetings, >> >> I've solved a couple of bugs in the Leanpub[1] markdown exporter[2] >> (cross-links within the book using ids were not working, and footnotes >> containing a colon neither). As far as I can tell using Orgmode and >> Leanpub to publish books is now quite feasible, and produces rather >> nice results. >> >> I have also published the sources for my book, The Hacker Ways[3], at >> >> https://github.com/juanre/hacker-ways >> >> It is rather annoying that github understands the org syntax but not >> quite, so the sources appear almost but not quite right. Clone and >> open in Emacs to see what's going on. >> >> Best regards, >> >> jm >> -- >> http://greaterskies.com >> http://juanreyero.com >> >> [1] Leanpub.com is a very nice self-publishing platform. I am not >> associated with them, and they are not responsible for my code. >> >> [2] http://juanreyero.com/open/ox-leanpub/ >> >> [3] https://leanpub.com/hackerways/ >> > -- http://greaterskies.com http://juanreyero.com