emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: "Thomas S. Dye" <tsd@tsdye.com>
Cc: emacs-orgmode@gnu.org, Oleh Krehel <ohwoeowho@gmail.com>,
	Oleh Krehel <oleh@oremacs.com>
Subject: Re: Is it possible to keep /all/ the heading properties in one place?
Date: Mon, 29 Feb 2016 11:05:53 +0100	[thread overview]
Message-ID: <87egbvesqm.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <m24mcskd48.fsf@tsdye.com> (Thomas S. Dye's message of "Sun, 28 Feb 2016 06:34:31 -1000")

Hello,

Thomas S. Dye <tsd@tsdye.com> writes:

> I worked on a project to port the Org manual to Org about three years
> ago.  At the time, I thought the Texinfo exporter supported the project
> quite well.
>
> The project had a mixed reception and ultimately wasn't adopted, but I
> don't remember Texinfo exporter deficiencies figuring into the
> decision.

AFAIR, the problem is that Emacs developers fix spelling issues right
into the ".texi" document, so we would need to backport each of their
changes into the Org source. Duplicated efforts.

However, I still think it would be nice to have the document somewhere
in the Org tree, perhaps in contrib/ as a start, then possibly one day
in doc/.

As a side note, another interesting project would be an "info" export
back-end. Currently, producing an info file is very slow because we go
through the "texinfo" format first.


Regards,

-- 
Nicolas Goaziou

  reply	other threads:[~2016-02-29 10:03 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-25 10:59 Is it possible to keep /all/ the heading properties in one place? Oleh Krehel
2016-02-25 13:37 ` Nicolas Goaziou
2016-02-25 13:46   ` Oleh Krehel
2016-02-25 14:03     ` Nicolas Goaziou
2016-02-25 14:26       ` Oleh Krehel
2016-02-25 16:52         ` Nicolas Goaziou
2016-02-25 18:21           ` Eric S Fraga
2016-02-26 16:35             ` Rasmus
2016-02-28  9:35               ` Eric S Fraga
2016-02-28 11:32                 ` Rasmus
2016-02-28 12:44                   ` Eric S Fraga
2016-02-28 16:46                     ` Rasmus
2016-02-28 17:05                       ` Eric S Fraga
2016-02-25 19:17           ` Oleh Krehel
2016-02-25 20:16             ` Nicolas Goaziou
2016-02-26  8:18               ` Oleh Krehel
2016-02-28  8:59                 ` Nicolas Goaziou
2016-02-28 12:17                   ` Oleh Krehel
2016-02-28 16:34                     ` Thomas S. Dye
2016-02-29 10:05                       ` Nicolas Goaziou [this message]
2016-02-29 13:42                         ` Thomas S. Dye
2016-02-29 15:00                           ` Nicolas Goaziou
2016-02-29 13:53                         ` Marcin Borkowski
2016-02-29 15:05                           ` Nicolas Goaziou
2016-02-29 17:57                         ` Revisiting moving manual to Org (was: Is it possible to keep /all/ the heading properties in one place?) Kyle Meyer
2016-02-29 17:17                       ` Is it possible to keep /all/ the heading properties in one place? Achim Gratz
2016-02-29 18:01                         ` Thomas S. Dye
2016-02-29 18:47                           ` Nicolas Goaziou
2016-02-25 17:47 ` Michael Brand

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=87egbvesqm.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=ohwoeowho@gmail.com \
    --cc=oleh@oremacs.com \
    --cc=tsd@tsdye.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).