From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: [ox, patch] Add #+SUBTITLE
Date: Sun, 22 Mar 2015 23:43:09 +0100 [thread overview]
Message-ID: <87384w7iwy.fsf@gmx.us> (raw)
In-Reply-To: 87oanku5d0.fsf@wmi.amu.edu.pl
Marcin Borkowski <mbork@wmi.amu.edu.pl> writes:
> [TL;DR: imho, the right way to do LaTeX export is to prepare a dedicated
> package for Org-mode generated files (easy/medium), arrange for it to be
> included in all major TeX distros (easy) and simplify the LaTeX exporter
> to comply with it (easy). This could greatly enhance the quality of
> PDFs produced by Org-mode and make modifying their look easier on the
> Org side. I could do the LaTeX side of the work. Now the question is:
> does the community /want/ it.]
I have a couple of initial concerns that you could address if your
spin-off thread if you like.
- Sat you can envision better code for a particular piece of org syntax.
Why is a better to have it in an external latex-package than directly in
the org files? If it lives somewhere else, I have to bug you when I
want to change something. What if you get bored of this?
- What happens when you cannot maintain it any longer? Note also that the
scope is somewhat different as a typical latex package solves a problem
like "provide good tables" or "enhance itemize 2e" (ei2e). Such
packages are fairly easy to replace (e.g. sugfigure → subcaption).
- I don't want latex code generated by org to a "special flavor" like with
LyX.
- Why can the issues you have in mind not be solved by a specialized
derived backend? Such as ox-beamer or ox-koma-letter.
Thanks,
Rasmus
--
Enough with the bla bla!
next prev parent reply other threads:[~2015-03-22 22:43 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-20 23:23 [ox, patch] Add #+SUBTITLE Rasmus
2015-03-21 2:26 ` Marcin Borkowski
2015-03-21 2:32 ` Melanie Bacou
2015-03-22 14:02 ` Nicolas Goaziou
2015-03-22 15:29 ` Rasmus
2015-03-22 20:47 ` Marcin Borkowski
2015-03-22 21:21 ` Thomas S. Dye
2015-03-22 21:23 ` John Williams
2015-03-22 22:43 ` Rasmus [this message]
2015-03-22 23:19 ` Marcin Borkowski
2015-03-23 0:05 ` Rasmus
2015-03-23 8:32 ` Marcin Borkowski
2015-03-23 9:00 ` Sebastien Vauban
2015-03-24 9:05 ` Nicolas Goaziou
2015-03-24 9:37 ` Rasmus
2015-03-28 15:17 ` Nicolas Goaziou
2015-03-26 2:36 ` Melanie Bacou
2015-03-26 2:38 ` Melanie Bacou
2015-03-26 10:10 ` Rasmus
2015-03-22 14:34 ` Eric Abrahamsen
2015-03-22 15:32 ` Rasmus
2015-03-23 1:17 ` Eric Abrahamsen
2015-03-26 2:47 ` Melanie Bacou
2015-03-26 9:52 ` Rasmus
2015-03-26 10:42 ` Rasmus
2015-03-28 8:26 ` Melanie Bacou
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=87384w7iwy.fsf@gmx.us \
--to=rasmus@gmx.us \
--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).