emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: Changed behaviours of LaTeX exporter in version 8.0+
Date: Mon, 29 Sep 2014 10:53:40 +0200	[thread overview]
Message-ID: <87eguug63v.fsf@gmx.us> (raw)
In-Reply-To: CACsgZ=pDCtMV_F+5s6geBikwjx2d5eBru9BBJ8ghktnH7PiGgQ@mail.gmail.com

Hi,

"Kyeong Soo (Joseph) Kim" <kyeongsoo.kim@gmail.com> writes:

> On Mon, Sep 29, 2014 at 3:07 PM, Nicolas Goaziou <mail@nicolasgoaziou.fr>
> wrote:
>
>> Hello,
>>
>> "Kyeong Soo (Joseph) Kim" <kyeongsoo.kim@gmail.com> writes:
>>
>> > The real problem is that, except for using the custom id, the current
>> > export engine cannot refer to the correct label (e.g., "\label{se-1}")
>> > which is automatically generated during the export process.
>> >
>> > See the case of section title with only one word in the ECM (e.g., "
>> > \hyperref[sec-1]{OneWord}"), where the export engine still cannot
>> properly
>> > refer to the automatically generated label. This has nothing to do with
>> the
>> > URL-encoding.
>>
>> Could you elaborate about what is wrong with
>> "\hyperref[sec-1]{OneWord}"?
>>
>> AFAICT, it is the desired output.
>>
>>
>> Regards,
>>
>> --
>> Nicolas Goaziou
>>
>
> Now I see the point in your suggestion.
>
> It seems that you suggest using filter to change
>
> \hyperref[sec-1]{OneWord}
>
> to
>
> \ref{sec-1}
>
> Am I right?

If you don't want to use hyperref (i) make sure your sections are
numbered (e.g. #+OPTIONS: num:5) and (ii) make sure that you are not
giving links a description.  Here's an example:

* test my heading
:PROPERTIES:
:CUSTOM_ID: t
:END:
[[*test my heading][my funky label]]
[[*test my heading]]
[[#t]]

→ 

\section{test my heading}
\label{sec-1}
\hyperref[sec-1]{my funky label}
\ref{sec-1}
\ref{sec-1}

—Rasmus

-- 
May the Force be with you

  reply	other threads:[~2014-09-29  8:54 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-18  4:50 Changed behaviours of LaTeX exporter in version 8.0+ Kyeong Soo (Joseph) Kim
2014-09-18  7:07 ` Kyeong Soo (Joseph) Kim
2014-09-18  7:32   ` Kyeong Soo (Joseph) Kim
2014-09-18 16:10     ` Richard Lawrence
     [not found]       ` <CACsgZ=r1vzPQg1KB3N7j6Mn+nyu=PUrxJCeRr5ebqmpywsQ0bg@mail.gmail.com>
2014-09-19 15:49         ` Richard Lawrence
2014-09-20 15:32           ` Kyeong Soo (Joseph) Kim
2014-09-22 16:00             ` Nicolas Goaziou
2014-09-23  3:03               ` Kyeong Soo (Joseph) Kim
2014-09-27 22:01                 ` Nicolas Goaziou
2014-09-29  4:51                   ` Kyeong Soo (Joseph) Kim
2014-09-29  7:07                     ` Nicolas Goaziou
2014-09-29  7:57                       ` Kyeong Soo (Joseph) Kim
2014-09-29  8:53                         ` Rasmus [this message]
2014-09-29  9:59                           ` Kyeong Soo (Joseph) Kim
2014-09-29 10:09                             ` Rasmus
2014-09-29 12:18                               ` Kyeong Soo (Joseph) Kim
2014-09-29 14:18                                 ` Rasmus
2014-09-29 14:18                                 ` Rasmus
2014-10-01  9:39                                   ` Kyeong Soo (Joseph) Kim
2014-09-18 15:47   ` Richard Lawrence
  -- strict thread matches above, loose matches on Subject: below --
2014-09-17 14:54 Kyeong Soo (Joseph) Kim
2014-09-17 19:01 ` Nicolas Goaziou

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=87eguug63v.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).