From: David Masterson <dsmasterson@gmail.com>
To: William Denton <wtd@pobox.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: LaTeX tutorial (focused on what Org exports) ??
Date: Mon, 02 Jan 2023 19:25:56 -0800 [thread overview]
Message-ID: <SJ0PR03MB54556638FF1A06B523244639A2F49@SJ0PR03MB5455.namprd03.prod.outlook.com> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2301021316060.412390@shell3.miskatonic.org> (William Denton's message of "Mon, 2 Jan 2023 13:31:31 -0500 (EST)")
William Denton <wtd@pobox.com> writes:
> On 30 December 2022, Thomas S. Dye wrote:
>
>> Org's latex exporter is exceptionally capable. AFAICT, it doesn't
>> have practical limits on the LaTeX it produces, at least for my
>> academic use case. I'm able to use all of the LaTeX packages I've
>> ever wanted to use.
>
> Me too, and the more I use Org with LaTeX, the more I'm seeing how I
> can use Org as a way to organize a large publishing project: use
> literate programming and export the LaTeX piece by piece, documenting
> what I'm doing; use source blocks to run necessary code to prepare
> images or files before inclusion; and so on.
>
> Using Org (simple markup plus some +latex_header lines) and exporting
> to LaTeX is straightforward enough ... managing a project, with the
> LaTeX as code to be generated, can get a lot more complicated, but on
> the other hand, Org makes that kind of thing simpler. (Of course,
> anything involving LaTeX is bound to get complicated pretty soon.)
>
> I've learned a lot from several regulars on this mailing list,
> including Juan Manuel Macías, who does remarkable work on dictionaries
> and translations. Here's an example:
>
> https://lists.gnu.org/archive/html/emacs-orgmode/2021-06/msg00348.html
>
> Along with all the other recommendations, it's worth looking at the
> user guide for the memoir class, which is great for books:
>
> https://www.ctan.org/pkg/memoir
>
> It'll be somewhere on your system as memman.pdf. I learned a lot
> about page design and LaTeX from it.
I'll have to make time for this. Thanks.
--
David Masterson
next prev parent reply other threads:[~2023-01-03 3:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-30 21:29 LaTeX tutorial (focused on what Org exports) ?? David Masterson
2022-12-31 1:18 ` Thomas S. Dye
2022-12-31 10:32 ` Marcin Borkowski
2023-01-01 7:08 ` David Masterson
2023-01-02 18:31 ` William Denton
2023-01-03 3:25 ` David Masterson [this message]
2022-12-31 11:55 ` Fraga, Eric
2023-01-01 7:12 ` David Masterson
2023-01-01 7:19 ` Ihor Radchenko
2023-01-01 13:18 ` Fraga, Eric
2023-01-01 13:43 ` Ihor Radchenko
2023-01-02 12:30 ` Fraga, Eric
2023-01-03 3:23 ` David Masterson
2023-01-03 9:10 ` Fraga, Eric
2023-01-04 0:12 ` David Masterson
[not found] ` <87o7rgmhcs.fsf@penguin>
2023-01-03 3:28 ` David Masterson
-- strict thread matches above, loose matches on Subject: below --
2023-01-04 7:18 Pedro Andres Aranda Gutierrez
2023-01-06 6:21 ` David Masterson
2023-01-06 18:07 ` William Denton
2023-01-06 23:57 ` David Masterson
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=SJ0PR03MB54556638FF1A06B523244639A2F49@SJ0PR03MB5455.namprd03.prod.outlook.com \
--to=dsmasterson@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=wtd@pobox.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).