emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Sebastien Vauban <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: *text* in headlines and export to latex
Date: Thu, 15 May 2014 14:45:25 +0200	[thread overview]
Message-ID: <868uq3tdlm.fsf@somewhere.org> (raw)
In-Reply-To: CAMF4YiMAXBbQgvcMPuVb4F9_kVQc4wH351FEEqogxq8+0-1u0g@mail.gmail.com

Seb Frank wrote:
> On Wed, May 14, 2014 at 7:19 PM, Eric S Fraga <e.fraga-hclig2XLE9Zaa/9Udqfwiw@public.gmane.org> wrote:
>> On Wednesday, 14 May 2014 at 18:00, Seb Frank wrote:
>>> Latex export converts *text* to \textbf -- this doesn't work well
>>> for headlines that get turned into section titles as these appear to
>>> be bold by default. Is there a way to change this to \emph in
>>> headlines that get converted to (sub)sections?
>>
>> Silly question but: can you not simply use /text/ instead in the
>> headlines?  Mind you, I think that bold + emph is not pretty... but
>> that's a personal taste issue!
>
> Yes -- but that changes it to emph (instead of alert) in beamer export.

As a side note, as both \alert and \textbf do exist in Beamer, I do
think *text* should never be translated to \alert.

That's because of that different translation between the two backends
that you see that problem only in one backend.

Best regards,
  Seb

-- 
Sebastien Vauban

  parent reply	other threads:[~2014-05-15 12:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-14 17:00 *text* in headlines and export to latex Seb Frank
2014-05-14 18:19 ` Eric S Fraga
2014-05-14 18:28   ` Seb Frank
2014-05-15  7:00     ` Eric S Fraga
2014-05-15 12:45     ` Sebastien Vauban [this message]
2014-05-15 22:34       ` Seb Frank

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=868uq3tdlm.fsf@somewhere.org \
    --to=sva-news-d0wtavr13harg/idocfnwg@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).