From: "Juan Manuel Macías" <maciaschain@posteo.net>
To: Marcin Borkowski <mbork@mbork.pl>
Cc: orgmode <emacs-orgmode@gnu.org>
Subject: Re: Org to ConTeXt exporter?
Date: Tue, 29 Dec 2020 17:05:17 +0100 [thread overview]
Message-ID: <87eej838ea.fsf@posteo.net> (raw)
In-Reply-To: <87zh1xya3i.fsf@mbork.pl> (Marcin Borkowski's message of "Mon, 28 Dec 2020 21:03:53 +0100")
Hello, Marcin,
Marcin Borkowski <mbork@mbork.pl> writes:
> Here's the thing. Some time ago, I have dedicated about 20 minutes per
> day (sometimes less, sometimes more, but the average over the past 6
> years is about 17 minutes now) to what I call "creative writing" -
> mainly the book I was working on for the past 5 years with two more
> people (and that book is now complete) and my blog. I will try to use
> some of that time to start that tutorial, and maybe I will then publish
> it on my blog or somewhere. (I also want to get back to the book on
> Elisp I started a long time ago, but that can wait a few more weeks.)
As I said, I think a tutorial on writing an Org exporter from scratch
would be very interesting and useful. If, finally, you can find time for
it, I could do a translation to publish it on my blog in Spanish
(https://gnutas.juanmanuelmacias.com/). With my translation of Homer's
Odyssey (work in progress) and other projects, I don't have a lot of free
time, but I can always find a moment.
> But here's the thing: I'll need help. I know LaTeX very well - I've
> been using plain TeX for about 25 years now and LaTeX for about 20
> years, including writing quite a few packages and classes - but I don't
> know ConTeXt that well. (I did use it a bit, but not very extensively.)
(In my case) I have not used much ConTeXt. Really, I prefer LaTeX. It's
a personal opinion and a matter of taste, but I find ConTeXt too
"monolithic". One of the main problems it has is (I think) its huge lack
of documentation (compared to LaTeX). I suppose, in part, because his
community is smaller. However, I also think that ConTeXt has interesting
features (grid typesetting, xml integration, etc.), and it would not be
a bad idea to have an alternative to LaTeX in Org. But I don't know if
it would be something feasible in the short term, beyond the concept...
Regards,
Juan Manuel
next prev parent reply other threads:[~2020-12-29 16:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-28 13:38 Org to ConTeXt exporter? Juan Manuel Macías
2020-12-28 15:04 ` Marcin Borkowski
2020-12-28 15:38 ` Juan Manuel Macías
2020-12-28 16:09 ` Jonathan McHugh
2020-12-28 17:54 ` Juan Manuel Macías
2020-12-28 19:06 ` Jonathan McHugh
2020-12-29 21:51 ` Jonathan McHugh
2021-01-04 9:41 ` Ludovic Courtès
2020-12-28 16:23 ` Diego Zamboni
2020-12-28 18:03 ` Juan Manuel Macías
2020-12-28 19:23 ` Diego Zamboni
2020-12-28 20:03 ` Marcin Borkowski
2020-12-29 16:05 ` Juan Manuel Macías [this message]
2021-01-08 2:37 ` Jason Ross
2021-01-09 17:42 ` Juan Manuel Macías
2021-01-13 1:16 ` Jason Ross
2021-01-08 3:52 ` Jason Ross
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=87eej838ea.fsf@posteo.net \
--to=maciaschain@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=mbork@mbork.pl \
/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).