From: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
To: seb@k-7.ch, Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: Managing acronyms in an Org-mode document
Date: Mon, 27 May 2024 07:26:41 +0200 [thread overview]
Message-ID: <CAO48Bk9imk0O+j_qpKjpL6nMO5_FmYF2r+VoL5r_oJPyJyR_cQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1279 bytes --]
Sébastien writes:
> Hello,
Hi, answers inline
> Is there a way to manage acronyms in an Org-mode document ?
Currently I'm using acronyms in Documents which I handle with *TeX as my
background processor. So, it's basically embedding the LaTeX \ac* commands
in the org-file. But I'm thinking of a module to do this in org-native
mode.
> For example:
>
> 1. I write a list of acronyms and their definition inside a "List of
> acronyms" heading
>
> 2. In my document, when I simply write the acronyms in my text
>
> 3. When I export my Org-mode document, the first time that an acronym is
> written, it appear in full version and all the other times it appear
> in acronym version
Most of what you say is already there in e.g. the acronyms package in LaTeX
and I have an ancient attempt at this written in C which made it's way to
the venerable latex2rtf program. It could make a nice summer project. I
could share the notes I have taken until now with basic ideas.
Best, /PA
--
Fragen sind nicht da, um beantwortet zu werden,
Fragen sind da um gestellt zu werden
Georg Kreisler
Headaches with a Juju log:
unit-basic-16: 09:17:36 WARNING juju.worker.uniter.operation we should run
a leader-deposed hook here, but we can't yet
[-- Attachment #2: Type: text/html, Size: 1734 bytes --]
next reply other threads:[~2024-05-27 9:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-27 5:26 Pedro Andres Aranda Gutierrez [this message]
2024-05-28 11:34 ` Managing acronyms in an Org-mode document John Kitchin
2024-05-28 16:00 ` Pedro Andres Aranda Gutierrez
-- strict thread matches above, loose matches on Subject: below --
2024-05-25 23:26 Sébastien Gendre
2024-05-26 13:02 ` Ihor Radchenko
2024-05-27 3:16 ` Sébastien Gendre
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=CAO48Bk9imk0O+j_qpKjpL6nMO5_FmYF2r+VoL5r_oJPyJyR_cQ@mail.gmail.com \
--to=paaguti@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=seb@k-7.ch \
/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).