From: "Kyeong Soo (Joseph) Kim" <kyeongsoo.kim@gmail.com>
To: "Kyeong Soo (Joseph) Kim" <kyeongsoo.kim@gmail.com>,
Richard Lawrence <richard.lawrence@berkeley.edu>,
emacs-orgmode@gnu.org
Subject: Re: Changed behaviours of LaTeX exporter in version 8.0+
Date: Mon, 29 Sep 2014 12:51:42 +0800 [thread overview]
Message-ID: <CACsgZ=rxqNH1Vh9sEek6HXsY6ShV-bQxxbWjDqCW5f=u-H5JmQ@mail.gmail.com> (raw)
In-Reply-To: <87ppegrae5.fsf@nicolasgoaziou.fr>
[-- Attachment #1: Type: text/plain, Size: 1192 bytes --]
Hi Nicolas,
On Sun, Sep 28, 2014 at 6:01 AM, Nicolas Goaziou <mail@nicolasgoaziou.fr>
wrote:
>
>
> You can use a link filter. Also, `org-export-latex-hyperref-format'
> doesn't exist in Org 8.0+.
>
> > - By name (using C-c l & C-c C-l): Sec. [[*Two%20Words][Two Words]]
>
> [...]
>
> > [[*With%20&%20in%20the%20Title][With & in the Title]]
>
> This is the problem. The path isn't expected to be url-encoded. AFAICT,
> "C-c l" doesn't encoded headlines. I don't know how yours generates such
> a link.
>
>
> Regards,
>
> --
> Nicolas Goaziou
>
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.
Note that the issue of URL-encoding has gone once I cleared up my org-mode
configurations (i.e., commented all out for testing). Still, however, the
issue of wrong cross-referencing is there.
Regards,
Joseph
[-- Attachment #2: Type: text/html, Size: 2057 bytes --]
next prev parent reply other threads:[~2014-09-29 4:51 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 [this message]
2014-09-29 7:07 ` Nicolas Goaziou
2014-09-29 7:57 ` Kyeong Soo (Joseph) Kim
2014-09-29 8:53 ` Rasmus
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='CACsgZ=rxqNH1Vh9sEek6HXsY6ShV-bQxxbWjDqCW5f=u-H5JmQ@mail.gmail.com' \
--to=kyeongsoo.kim@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=richard.lawrence@berkeley.edu \
/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).