From: David O'Toole <dto@gnu.org>
To: Carsten Dominik <dominik@science.uva.nl>
Cc: emacs-orgmode@gnu.org
Subject: Re: [David O'Toole] Fwd: Re: org-publish future ?
Date: Tue, 06 Jun 2006 06:48:21 -0400 [thread overview]
Message-ID: <m3slmiimq2.fsf@gnu.org> (raw)
In-Reply-To: <5a66e8bc561ad58f8ec11eb9d01b2e97@science.uva.nl> (Carsten Dominik's message of "Tue, 6 Jun 2006 12:29:46 +0200")
I tend to agree... I wasn't that hot about this possibility myself,
but thought it would be prudent to ask.
Carsten Dominik <dominik@science.uva.nl> writes:
> On Jun 5, 2006, at 23:19, David O'Toole wrote:
>>
>> On a related note, Carsten are you reading? Something came up in IRC
>> discussion, about making it easier to convert org documents to other
>> formats. Although I am a bit resistant to the idea, especially since
>> it would take things in a more muse-ish direction, I remember you had
>> mentioned making a "cleaned up" publishing function that produces an
>> intermediate format (s-expressions?) that could be transformed into
>> something else. Are you still thinking about this?
>
> My interest in exporting Org-mode to more formats is quite limited. I
> am not using Org-mode to write books. And if I want to produce a
> book, moving away from the fantastic toolset for LaTeX available under
> Emacs to something that limits my possibilities to a subset of LaTeX
> is a loss, not a gain.
>
> Personally, I am not often in a situation where I need to produce many
> different output formats of a document. The only major application
> for this is documentation, for example of computer programs produce
> documentation. There are many systems that can do this, for example
> POD (developed for the perl documentation), TeXInfo, muse. I don't
> see why Org-mode needs to be able to do the same.
>
> The one thing I would be interested in is indeed to produce one very
> general format that would allow people to do with it whatever they
> want. My feeling is that such a format could be based on the current
> HTML exporter because it does a complete structural analysis of an
> Org-mode document, and the output could be some kind of semantic-only
> HTML, or XML, or whatever. I have not taken any steps toward
> implementing this, and right now I don't see it happening.
>
> - Carsten
>
>
--
Dave O'Toole
dto@gnu.org
next prev parent reply other threads:[~2006-06-06 10:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-05 21:19 [David O'Toole] Fwd: Re: org-publish future ? David O'Toole
2006-06-06 10:29 ` Carsten Dominik
2006-06-06 10:48 ` David O'Toole [this message]
2006-06-06 13:54 ` Michael Olson
2006-06-06 14:17 ` Carsten Dominik
2006-06-06 14:38 ` Michael Olson
[not found] ` <9bcdfad70606060901q52c0097fgde12d5d6ffcf83e9@mail.gmail.com>
2006-06-06 16:02 ` Fwd: " Chris wallace
2006-06-07 13:06 ` Carsten Dominik
2006-06-07 15:00 ` Chris wallace
2006-06-07 15:25 ` David O'Toole
2006-06-10 12:24 ` Bastien
2006-06-07 17:09 ` Christian Schlauer
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=m3slmiimq2.fsf@gnu.org \
--to=dto@gnu.org \
--cc=dominik@science.uva.nl \
--cc=emacs-orgmode@gnu.org \
/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).