From: Bastien <bzg@altern.org>
To: emacs-orgmode@gnu.org
Subject: Re: Re: [David O'Toole] Fwd: Re: org-publish future ?
Date: Sat, 10 Jun 2006 13:24:27 +0100 [thread overview]
Message-ID: <87zmglp5ac.fsf@tallis.ilo.ucl.ac.uk> (raw)
In-Reply-To: <87k67utklm.fsf@tuxtanker.mwolson.org> (Michael Olson's message of "Tue, 06 Jun 2006 10:38:45 -0400")
Michael Olson <mwolson@gnu.org> writes:
> Carsten Dominik <dominik@science.uva.nl> writes:
>
>> Yes, this is certainly true. ascii-to-xxx converters can certainly
>> help you to write your first LaTeX document. However, they don't
>> encourage to grow into that language at all, so to some extend they
>> are a dead end.
>
> I disagree. It would give people an excellent foundation that they
> can build upon, since they can examine the output from that publishing
> routine to learn LaTeX. When they come across limitations of the
> current LaTeX publishing implementation, they will search for
> supplemental information.
>
> Don't get me wrong: I'm not proposing that anyone actually implement
> this for Org, I'm just defending the hypothetical existence of such a
> publisher.
I also think ascii-to-xxx converter can be useful as long as they stay
as simple as ascii and provided they don't require anything new to
learn. Otherwise there is no point in learning a new ascii syntax
instead of directly learning LaTeX.
Regards,
--
Bastien
next prev parent reply other threads:[~2006-06-10 12:24 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
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 [this message]
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=87zmglp5ac.fsf@tallis.ilo.ucl.ac.uk \
--to=bzg@altern.org \
--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).