emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: Bug: \uline produced inside \section in latex export [8.2.5h (8.2.5h-30-gdd810b-elpa @ /home/user/.emacs.d/elpa/org-20140303/)]
Date: Sat, 22 Mar 2014 21:06:33 +0100	[thread overview]
Message-ID: <87y502roae.fsf@gmx.us> (raw)
In-Reply-To: 874n2qcgcx.fsf@yahoo.fr

Nicolas Richard <theonewiththeevillook@yahoo.fr> writes:

> Nicolas Goaziou <n.goaziou@gmail.com> writes:
>> It is technically possible to use \underline (hard-coded) in sections
>> and \uline (or whatever is defined in`org-latex-text-markup-alist')
>> everywhere else.
>>
>> Is there any downside to this proposal?
>
> Disclaimer : While I do use LaTeX, I rarely use the exporter, and never
> underline in sections.
>
> (The shed should be green, obviously.)
>
> I don't know why \uline doesn't work, but while \underline works, it
> does so with many warnings. I think the reason is that hyperref tries to
> add the text to the PDF TOC (usually a pane in the pdf viewer), and that
> supports very little to no formatting.
>
> Rasmus' suggestion seemed good, i.e.
> \texorpdfstring{\uline{SECTION}}{SECTION}
>
> I'd go even a little further : assuming it makes sense to underline
> within a section header, does it also make sense to propagate that
> formatting to the toc and/or header of the document ? If not, I suggest
> exporting as:
> \section[not-so-plain text]{\uline{not-so-plain} \textbf{text}}

This we cannot know before hand and for all cases.  I cannot think of
any case where you would use any kind of styling—other than math—in
section titles.  Yet others might and I think this suggestion is too
strong of an "assumption".

Perhaps it could be provided as an option. 

> Also I don't know why there was underlining in the first place. If we're
> asking to underline all section titles, then it might make sense to
> redefine e.g. \section to do so (packages titlesec might help).

Yeah, that would be a better approach if the underlines are not
one-off. . .

Rasmus

-- 
C is for Cookie

  reply	other threads:[~2014-03-22 20:04 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-21 16:30 Bug: \uline produced inside \section in latex export [8.2.5h (8.2.5h-30-gdd810b-elpa @ /home/user/.emacs.d/elpa/org-20140303/)] Konstantin Kliakhandler
2014-03-21 23:32 ` Bastien
2014-03-22  8:01   ` Konstantin Kliakhandler
2014-03-22  8:02   ` Nicolas Goaziou
2014-03-22  8:27     ` Bastien
2014-03-22 11:19       ` Nicolas Goaziou
2014-03-22 11:38         ` Rasmus
2014-03-22 11:45         ` Konstantin Kliakhandler
2014-03-22 12:38           ` Nicolas Goaziou
2014-03-22 13:03             ` Bastien
2014-03-22 13:37               ` Nicolas Goaziou
2014-03-22 14:09                 ` Bastien
2014-03-22 14:18                   ` Nicolas Goaziou
2014-03-22 17:06             ` Nicolas Richard
2014-03-22 20:06               ` Rasmus [this message]
2014-03-22 21:04               ` Konstantin Kliakhandler

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=87y502roae.fsf@gmx.us \
    --to=rasmus@gmx.us \
    --cc=emacs-orgmode@gnu.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).