From: tsd@tsdye.com (Thomas S. Dye)
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: Org-mode <emacs-orgmode@gnu.org>
Subject: Re: New LaTeX exporter, link to \ref
Date: Sun, 16 Sep 2012 08:05:28 -1000 [thread overview]
Message-ID: <m17grtlu6v.fsf@tsdye.com> (raw)
In-Reply-To: <87sjaih0um.fsf@gmail.com> (Nicolas Goaziou's message of "Sun, 16 Sep 2012 09:40:33 +0200")
Aloha Nicolas,
Nicolas Goaziou <n.goaziou@gmail.com> writes:
> Hello,
>
> tsd@tsdye.com (Thomas S. Dye) writes:
>
>> This in the org file:
>>
>> (fig. [[fig:old-wood]])
>>
>> exports to this in the latex file:
>>
>> (fig. \ref{fig-old-wood})
>>
>> I think the exporter is replacing the colon with a hyphen, which breaks
>> the reference.
>
> Correct. It's done by the function `org-export-solidify-link-text'. The
> problem is that it isn't used consistently across the back-end. It
> should be fixed now.
Yes, link text is consistently changed so cross references work. Thanks.
>> Also, is there some way to toggle a non-breaking space, e.g.,
>> (fig.~\ref{fig:old-wood})? I thought to use \tilde{}, but this wouldn't
>> work with other back ends.
>
> You may use \nbsp{} entity.
>
> My keyboard layout allows for easy access to non-breaking spaces. So
> I use the following instead (_ character stands for the non-breaking
> space):
>
> #+begin_src emacs-lisp
> (defun ngz-latex-filter-nobreaks (text backend info)
> "Ensure \"_\" are properly handled in Beamer/LaTeX export."
> (when (memq backend '(e-beamer e-latex))
> (replace-regexp-in-string "_" "~" text)))
> (add-to-list 'org-export-filter-plain-text-functions
> 'ngz-latex-filter-nobreaks)
> #+end_src
Thanks very much for the filter, which makes for an aesthetically
pleasing org buffer. I changed the underscore to a non-breaking
space character in the call to replace-regexp-in-string and now get
tildes in my LaTeX export.
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
next prev parent reply other threads:[~2012-09-16 18:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-16 1:02 New LaTeX exporter, link to \ref Thomas S. Dye
2012-09-16 7:40 ` Nicolas Goaziou
2012-09-16 18:05 ` Thomas S. Dye [this message]
2012-09-16 20:42 ` Sebastien Vauban
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=m17grtlu6v.fsf@tsdye.com \
--to=tsd@tsdye.com \
--cc=emacs-orgmode@gnu.org \
--cc=n.goaziou@gmail.com \
/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).