Re: unnumbered subsections in latex export

["Sébastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>]

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