all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Myles English <mylesenglish@gmail.com>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: Emacs-orgmode <Emacs-orgmode@gnu.org>
Subject: Re: [new exporter] what is the label syntax for LaTeX export?
Date: Wed, 07 Nov 2012 22:46:16 +0000	[thread overview]
Message-ID: <87a9utxc93.fsf@gmail.com> (raw)
In-Reply-To: <87hap1sr45.fsf@gmail.com>


Nicolas Goaziou writes:

>> One problem I am having is that the exported LaTeX replaces the ":" with
>> a "-" to become \ref{tab-niceone} which precludes the use of (e.g.)
>> \autoref which would need to know that the thing being referenced was a
>> table by recognising the "tab:", no?  I am sure there is a good reason
>> for this, can you say why?
>
> This is due to one of the few functions that was brought from the old
> exporter: `org-export-solidify-link-text'.
>
> That's because targets (that is <<...>> or #+NAME: ...) have no
> limitation on the characters allowed in their value, which can lead to
> problems when translated into foreign code (i.e. an % sign in the target
> when using the latex back-end).

Thanks for the explanation.

> So, the function replaces forbidden characters with hyphens.
>
> Besides using filters, a solution might be either:

(I haven't actually made any progress on a solution using filters.  I
was expecting it to be a little convoluted though; splitting on the
first hyphen and joining on a colon.)

Not sure if you are showing me two options you are thinking of
implementing here or suggesting two things I can do myself:

> 1. to remove colons from the forbidden characters.

If no backends would mind dealing with a colon (I don't know them well
enough to be able to decide) then this would be preferable.

> 2. to limit the characters allowed in targets and remove
>    `org-export-solidify-link-text' altogether.

This option could restrict future backends, or other (future?) latex
packages.

The first option seems most appropriate because a character should only
be restricted if there is a good reason (e.g. a backend would not like
it) rather than forbidding every character and only allowing it if there
is a good reason to.

As to whether my use case is a good reason to allow colons: I have no
idea how many people use the \autoref or \nameref thing.

>
>
> Regards,

Myles

  reply	other threads:[~2012-11-07 22:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-05 22:05 [new exporter] what is the label syntax for LaTeX export? Myles English
2012-11-05 22:18 ` Nicolas Goaziou
2012-11-06  7:30   ` Carsten Dominik
2012-11-06 21:08   ` Myles English
2012-11-07  9:24     ` Nicolas Goaziou
2012-11-07 22:46       ` Myles English [this message]
2012-11-07 23:39         ` Nicolas Goaziou
2012-11-08  3:27           ` Myles English

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87a9utxc93.fsf@gmail.com \
    --to=mylesenglish@gmail.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.