emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Sébastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: unnumbered subsections in latex export
Date: Tue, 05 Apr 2011 12:16:31 +0200	[thread overview]
Message-ID: <80mxk5t340.fsf@somewhere.org> (raw)
In-Reply-To: BANLkTimX=fFoFx3GNTQyeMsqmaZ9-rv6+Q@mail.gmail.com

Hi Aankhen,

Aankhen wrote:
> 2011/4/4 Sébastien Vauban <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>:
>> [snip]
>>
>> When discussing exporters and features, two things that come up to my mind
>> as missing as a "general Org feature":
>>
>> - bibliography :: works for LaTeX[1], not for HTML export.
>> - acronyms :: idem.
>>
>> Maybe those should be made available for general Org usage by making them
>> somehow part of the preprocessing?
>
> FWIW, acronyms wouldn’t need any preprocessing for HTML export. Or maybe
> they would: HTML has both ‘acronym’ and ‘abbr’ (abbreviation) elements, the
> distinction between them being a little hard to make. Could go the other way
> and provide both in Org and combine them where there’s no distinction, I
> suppose.
>
> Uhm, anyway. Acronyms are natively supported in HTML. That is all.

Thanks for reporting this. Wasn't aware of it. Though, that does not alter the
need (at least, what I consider so) for acronyms handling in/from Org.

Let's clarify what I'm talking about -- I know, I should have done it earlier.

I want to be able to say, in my Org file, that DNS is an acronym, for example.
I'm thinking -- brainstorming! -- at a solution _such as_ adding accolades
around the acronyms:

--8<---------------cut here---------------start------------->8---
This paper talks about {DNS} clients and {DNS} servers...
--8<---------------cut here---------------end--------------->8---

In LaTeX, this should have to be translated to:

--8<---------------cut here---------------start------------->8---
This paper talks about \acro{DNS} clients and \acro{DNS} servers...
--8<---------------cut here---------------end--------------->8---

And the effects would be that:

1. the first occurrence of the acronym would be expanded in the PDF, while
   others not -- this is customizable!

2. every occurrence would be a link to the list of acronyms, at the end of the
   document.

In HTML, I would expect internal links to a list of acronyms at the end of the
document.

I was thinking at preprocessing, because some smart things need to be done:

- expanding the first occurrence of the acronym (if wished) with its
  definition, not the following;

- in the list, at the end of the document, only list acronym definitions for
  the acronyms that have been used in the document.

For the readability of the Org buffer, and for the behavior that we could
expect, maybe a new link type would make it?

I would expect a similar treatment for the bibliography: having some built-in
representation for that in Org, and have the exporters make it to both LaTeX
and HTML (and ...).

Comments welcome!

Best regards,
  Seb

-- 
Sébastien Vauban

  reply	other threads:[~2011-04-05 10:16 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-22 12:10 unnumbered subsections in latex export Suvayu Ali
2011-03-22 12:20 ` Sébastien Vauban
2011-03-22 12:31   ` Suvayu Ali
2011-03-22 12:56     ` Sébastien Vauban
2011-03-22 14:26       ` [PATCH] Allow mixed export of numbered and unnumbered sections in LaTeX Lawrence Mitchell
2011-03-22 22:52         ` Suvayu Ali
2011-03-23 14:04         ` [Accepted] " Bastien Guerry
2011-03-23 14:17         ` [PATCH] " Bastien
2011-03-22 14:35     ` Re: unnumbered subsections in latex export Nick Dokos
2011-03-22 23:08       ` Suvayu Ali
2011-03-22 23:21         ` Nick Dokos
2011-03-23  9:38           ` [PATCH] Allow mixed export of numbered and unnumbered sections in HTML Lawrence Mitchell
2011-03-23 14:05             ` [Accepted] " Bastien Guerry
2011-03-23 14:57               ` Nick Dokos
2011-03-23 15:50                 ` Suvayu Ali
2011-03-23 14:18           ` Re: unnumbered subsections in latex export Bastien
2011-03-23 15:02             ` Nick Dokos
2011-03-23 16:25               ` Lawrence Mitchell
2011-03-23 16:42                 ` Nick Dokos
2011-03-23 18:17                   ` Jambunathan K
2011-03-23 19:00                     ` Nick Dokos
2011-03-23 19:18                       ` Jambunathan K
2011-03-23 16:29               ` Thomas S. Dye
2011-03-23 17:42           ` Jambunathan K
2011-03-24  7:59             ` Bastien
2011-03-24 18:27               ` Achim Gratz
2011-03-24 19:25               ` Nick Dokos
2011-03-25  1:06                 ` Suvayu Ali
2011-04-04 14:39                 ` Sébastien Vauban
2011-04-04 17:04                   ` Nick Dokos
2011-04-04 20:32                   ` Aankhen
2011-04-05 10:16                     ` Sébastien Vauban [this message]
2011-04-05 19:07                       ` Aankhen
2011-04-05 19:27                         ` Eric S Fraga
2011-04-05 21:25                           ` New features for the exporters? Sébastien Vauban
2011-04-05 21:45                           ` Re: unnumbered subsections in latex export Aankhen
2011-04-06 18:49                   ` Matt Lundin
2011-04-06 20:19                     ` Sébastien Vauban
2011-03-27 11:16               ` Jambunathan K
2011-03-27 11:40                 ` Bastien
2011-03-31 21:58               ` Nicolas
2011-04-01  4:34                 ` Jambunathan K
2011-04-01  4:41                   ` Jambunathan K
2011-04-01  6:29                   ` Nick Dokos
2011-04-01 15:41                   ` Eric S Fraga
2011-04-04 14:00                     ` Matt Lundin
2011-04-04 14:12                       ` Jambunathan K
2011-04-04 16:36                         ` Matt Lundin
2011-04-04 17:09                           ` Nick Dokos
2011-04-01  7:39                 ` Jambunathan K
2011-04-01 18:25                 ` Achim Gratz

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=80mxk5t340.fsf@somewhere.org \
    --to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
    --cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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).