From mboxrd@z Thu Jan 1 00:00:00 1970 From: Waldemar Quevedo Subject: Re: Writing your book with orgmode and publishing it on Leanpub Date: Mon, 24 Feb 2014 21:08:16 +0900 Message-ID: References: <86wqgkhnjj.fsf@somewhere.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=e89a8ff25042d6016a04f325d495 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:54591) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WHuKt-0005x0-9m for emacs-orgmode@gnu.org; Mon, 24 Feb 2014 07:08:40 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WHuKs-0006wk-47 for emacs-orgmode@gnu.org; Mon, 24 Feb 2014 07:08:39 -0500 Received: from mail-ob0-x22d.google.com ([2607:f8b0:4003:c01::22d]:62387) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WHuKr-0006wc-TJ for emacs-orgmode@gnu.org; Mon, 24 Feb 2014 07:08:38 -0500 Received: by mail-ob0-f173.google.com with SMTP id wp18so383326obc.18 for ; Mon, 24 Feb 2014 04:08:37 -0800 (PST) In-Reply-To: <86wqgkhnjj.fsf@somewhere.org> 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: Sebastien Vauban Cc: emacs-orgmode --e89a8ff25042d6016a04f325d495 Content-Type: text/plain; charset=ISO-8859-1 Sebastien, > For me, an annoying problem is that the Org #+TITLE is treated as > a simple text, and not outputted as an headline. > So, if we want an headline on GitHub, we need to create a unique level-1 > heading, which will be shown as the most important section, hence the > "title". Then, under that, we can have many level-2 sections. Ok, I will revisit this part of the output from the parser and change it in the next release so that Github can also pick it up (issue here: https://github.com/wallyqs/org-ruby/issues/3) Thanks, - Wally On Mon, Feb 24, 2014 at 6:23 PM, Sebastien Vauban wrote: > Hello Waldemar, > > 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).... > > For me, an annoying problem is that the Org #+TITLE is treated as > a simple text, and not outputted as an headline. > > So, if we want an headline on GitHub, we need to create a unique level-1 > heading, which will be shown as the most important section, hence the > "title". Then, under that, we can have many level-2 sections. > > That feature makes it impossible to get the same design for Org > documents both as PDF, HTML or GitHub presentation page. > > Best regards, > Seb > > -- > Sebastien Vauban > > > --e89a8ff25042d6016a04f325d495 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Sebastien,

> For me, an annoying pr= oblem is that the Org #+TITLE is treated as
> a simple text, and not outputted as an headline.
> So, if we= want an headline on GitHub, we need to create a unique level-1
> heading, which will be shown as the most important section, hence the=
> "title". Then, under that, we can have many level-2 section= s.

Ok, I will revisit this part of the output from the pars= er and change it in the next release=A0
so that Github ca= n also pick it up (issue here:=A0https://github.com/wallyqs/org-ruby/issues/3)

Thanks,

- Wally=A0




On Mon, Feb 2= 4, 2014 at 6:23 PM, Sebastien Vauban <sva-news@mygooglest.com>= ; wrote:
Hello Waldemar,

Waldemar Quevedo wrote:
>> It is rather annoying that github understands the org syntax but n= ot
>> quite, so the sources appear almost but not quite right.
>
> I maintain the parser that is being by Github =3D>
> http= s://github.com/wallyqs/org-ruby
> If you let me now the issues I can try to fix them, (or PRs are also > welcome)....

For me, an annoying problem is that the Org #+TITLE is treated as
a simple text, and not outputted as an headline.

So, if we want an headline on GitHub, we need to create a unique level-1 heading, which will be shown as the most important section, hence the
"title". Then, under that, we can have many level-2 sections.

That feature makes it impossible to get the same design for Org
documents both as PDF, HTML or GitHub presentation page.

Best regards,
=A0 Seb

--
Sebastien Vauban



--e89a8ff25042d6016a04f325d495--