emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Waldemar Quevedo <waldemar.quevedo@gmail.com>
To: Sebastien Vauban <sva-news@mygooglest.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Writing your book with orgmode and publishing it on Leanpub
Date: Mon, 24 Feb 2014 21:08:16 +0900	[thread overview]
Message-ID: <CALzn4yiDQj+bdyVn2FnkMuMXnvL=jV2PtpHstJS_Jc+M1A_k1g@mail.gmail.com> (raw)
In-Reply-To: <86wqgkhnjj.fsf@somewhere.org>

[-- Attachment #1: Type: text/plain, Size: 1523 bytes --]

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
<sva-news@mygooglest.com>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
>
>
>

[-- Attachment #2: Type: text/html, Size: 3401 bytes --]

      reply	other threads:[~2014-02-24 12:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-23 19:24 Writing your book with orgmode and publishing it on Leanpub Juan Reyero
2014-02-24  7:39 ` Waldemar Quevedo
2014-02-24  8:33   ` Juan Reyero
2014-02-24 12:26     ` Waldemar Quevedo
2014-02-24  9:23   ` Sebastien Vauban
2014-02-24 12:08     ` Waldemar Quevedo [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CALzn4yiDQj+bdyVn2FnkMuMXnvL=jV2PtpHstJS_Jc+M1A_k1g@mail.gmail.com' \
    --to=waldemar.quevedo@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=sva-news@mygooglest.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).