emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: David Masterson <dsmasterson@gmail.com>
Cc: Stefan Nobis <stefan-ml@snobis.de>, emacs-orgmode@gnu.org
Subject: [PATCH] org-manual: Add references to LaTeX docs (was: New Orgmode LaTex Document Class ?)
Date: Thu, 03 Aug 2023 07:58:02 +0000	[thread overview]
Message-ID: <87tttg1rsl.fsf@localhost> (raw)
In-Reply-To: <SJ0PR03MB5455B2712FA85BA945DFF441A20BA@SJ0PR03MB5455.namprd03.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 368 bytes --]

David Masterson <dsmasterson@gmail.com> writes:

> I think begin.html is a good starting point.  Mentioning 'texdoc latex'
> is also simple (and more LaTeX specific) and most likely to work.  You
> could include a parenthetical note that, if it doesn't work, try the
> URL.  After that, new users can dig through the documentation.

See the attached tentative patch.


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-doc-org-manual.org-Refer-to-LaTeX-docs-for-general-t.patch --]
[-- Type: text/x-patch, Size: 2196 bytes --]

From 659d79484fcd280b0ec8d57282588386aa626b21 Mon Sep 17 00:00:00 2001
Message-ID: <659d79484fcd280b0ec8d57282588386aa626b21.1691049428.git.yantar92@posteo.net>
From: Ihor Radchenko <yantar92@posteo.net>
Date: Thu, 3 Aug 2023 10:56:07 +0300
Subject: [PATCH] doc/org-manual.org: Refer to LaTeX docs for general
 terminology

* doc/org-manual.org (LaTeX Export): Add links to online and offline
LaTeX docs.
(Quoting LaTeX code): Clarify that direct LaTeX can be used for
fine-tuning.

Link: https://orgmode.org/list/SJ0PR03MB5455B2712FA85BA945DFF441A20BA@SJ0PR03MB5455.namprd03.prod.outlook.com
---
 doc/org-manual.org | 14 +++++++++++---
 1 file changed, 11 insertions(+), 3 deletions(-)

diff --git a/doc/org-manual.org b/doc/org-manual.org
index 16fbb268f..c3a4e47bc 100644
--- a/doc/org-manual.org
+++ b/doc/org-manual.org
@@ -13703,6 +13703,13 @@ ** LaTeX Export
 blank lines in the Org document.  That's because LaTeX itself depends
 on blank lines to tell apart syntactical elements, such as paragraphs.
 
+The following sections expect users to be familiar with common LaTeX
+terminology.  You may refer to https://tug.org/begin.html to get
+familiar with LaTeX basics.  Users with LaTeX installed may also run
+=texinfo latex= from terminal to open LaTeX introduction [fn:: The
+command will open PDF file, which is also available for download from
+http://mirrors.ctan.org/info/latex-doc-ptr/latex-doc-ptr.pdf]
+
 *** LaTeX/PDF export commands
 :PROPERTIES:
 :DESCRIPTION: For producing @LaTeX{} and PDF documents.
@@ -13979,9 +13986,10 @@ *** Quoting LaTeX code
 :DESCRIPTION: Incorporating literal @LaTeX{} code.
 :END:
 
-The LaTeX export backend can insert any arbitrary LaTeX code, see
-[[*Embedded LaTeX]].  There are three ways to embed such code in the Org
-file and they all use different quoting syntax.
+When the available LaTeX export customizations are not sufficient to
+fine-tune the desired output, it is possible to insert any arbitrary
+LaTeX code (see [[*Embedded LaTeX]]).  There are three ways to embed such
+code in the Org file and they all use different quoting syntax.
 
 #+cindex: inline, in @LaTeX{} export
 Inserting in-line quoted with @ symbols:
-- 
2.41.0


[-- Attachment #3: Type: text/plain, Size: 224 bytes --]


-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>

  reply	other threads:[~2023-08-03  7:58 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-28  6:47 New Orgmode LaTex Document Class ? David Masterson
2023-07-28  7:23 ` Ihor Radchenko
2023-07-28  7:57 ` Stefan Nobis
2023-07-29 22:58   ` David Masterson
2023-07-30  4:27     ` Ihor Radchenko
2023-07-30  5:02       ` David Masterson
2023-07-30  6:42         ` Ihor Radchenko
2023-07-30 20:34           ` David Masterson
2023-07-31  7:05             ` Ihor Radchenko
2023-07-31  7:40               ` Stefan Nobis
2023-07-31 10:23                 ` Ihor Radchenko
2023-07-31 22:41                   ` David Masterson
2023-08-01  8:11                     ` Ihor Radchenko
2023-08-02  6:28                       ` David Masterson
2023-08-02  6:52                         ` Ihor Radchenko
2023-08-02  6:59                         ` Ihor Radchenko
2023-08-02 17:14                           ` David Masterson
2023-08-03  7:58                             ` Ihor Radchenko [this message]
2023-08-06  3:35                               ` [PATCH] org-manual: Add references to LaTeX docs David Masterson
2023-08-06  8:04                                 ` Ihor Radchenko
2023-08-02  7:49                         ` New Orgmode LaTex Document Class ? tomas
2023-08-02 16:53                           ` David Masterson
2023-08-02 17:29                             ` tomas

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=87tttg1rsl.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=dsmasterson@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=stefan-ml@snobis.de \
    /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).