From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jonathan Leech-Pepin Subject: Re: Anchors in texinfo export Date: Thu, 14 Feb 2013 11:45:36 -0500 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=089e01183198ef49aa04d5b1fcee Return-path: Received: from eggs.gnu.org ([208.118.235.92]:50734) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U61wP-0002m8-4n for emacs-orgmode@gnu.org; Thu, 14 Feb 2013 11:45:55 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1U61wH-0003Bj-Dj for emacs-orgmode@gnu.org; Thu, 14 Feb 2013 11:45:45 -0500 Received: from mail-vc0-f181.google.com ([209.85.220.181]:64023) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U61wH-0003Be-9K for emacs-orgmode@gnu.org; Thu, 14 Feb 2013 11:45:37 -0500 Received: by mail-vc0-f181.google.com with SMTP id d16so1638591vcd.12 for ; Thu, 14 Feb 2013 08:45:36 -0800 (PST) In-Reply-To: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: "Thomas S. Dye" Cc: Org-mode --089e01183198ef49aa04d5b1fcee Content-Type: text/plain; charset=UTF-8 Hello Tom, On 13 February 2013 11:31, Thomas S. Dye wrote: > Aloha all, > > Currently, the texinfo exporter translates a dedicated target in a comment: > > # <> > > to this: > > @c <> > > It shouldn't need to be within a comment to work successfully in the Texinfo exporter. @anchor{} is not visible to the reader (unless looking at the .texi source) so it won't be impacted by being outside of a comment. > I was expecting to see a texinfo anchor: > > @anchor{x-export-to-odt} > > There are a handful of these dedicated target comments cum anchors in the > Org > mode manual. I believe all of them are in places where it would be easy > to replace them with links directly to the corresponding headline/node. > > Should I edit them away? Or, are dedicated target comments/anchors > something the texinfo exporter should handle? > > Regards, Jon -- > All the best, > Tom > > -- > Thomas S. Dye > http://www.tsdye.com > > --089e01183198ef49aa04d5b1fcee Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hello Tom,

On 13 February 2013 11:31, Tho= mas S. Dye <tsd@tsdye.com> wrote:
Aloha all,

Currently, the texinfo exporter translates a dedicated target in a comment:=

# <<x-export-to-odt>>

to this:

@c <<x-export-to-odt>>

It shouldn't need to be within a comment to work = successfully in the Texinfo exporter.=C2=A0
@anchor{} is not visible to= the reader (unless looking at the .texi source) so it won't
be impa= cted by being outside of a comment.
=C2=A0
I was expecting to see a texinfo anchor:

@anchor{x-export-to-odt}

There are a handful of these dedicated target comments cum anchors in the O= rg
mode manual. I believe all of them are in places where it would be easy
to replace them with links directly to the corresponding headline/node.

Should I edit them away? Or, are dedicated target comments/anchors
something the texinfo exporter should handle?


Regards,

Jon
--
=C2=A0
All the best,
Tom

--
Thomas S. Dye
http://www.tsdye.com=


--089e01183198ef49aa04d5b1fcee--