From mboxrd@z Thu Jan 1 00:00:00 1970 From: Subhan Tindall Subject: Re: pxref in texinfo export Date: Mon, 25 Feb 2013 10:40:55 -0800 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([208.118.235.92]:55870) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UA2z0-0006B0-MU for emacs-orgmode@gnu.org; Mon, 25 Feb 2013 13:41:06 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UA2yw-0006BJ-I5 for emacs-orgmode@gnu.org; Mon, 25 Feb 2013 13:41:02 -0500 Received: from mail-la0-x22c.google.com ([2a00:1450:4010:c03::22c]:48662) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UA2yw-0006An-54 for emacs-orgmode@gnu.org; Mon, 25 Feb 2013 13:40:58 -0500 Received: by mail-la0-f44.google.com with SMTP id eb20so3046578lab.17 for ; Mon, 25 Feb 2013 10:40:55 -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: Jonathan Leech-Pepin Cc: Org-mode , "Thomas S. Dye" There are 4 different ref commands, all with slightly syntactic requirements and outputs when compiled using makeinfo. I for one use @pxref{} a lot, and it has different requirements for placement than @ref or @xref (namely those two MUST have a . or , following the end of the ref) 8.1 Different Cross Reference Commands There are four different cross reference commands: @xref Used to start a sentence in the printed manual saying =91See . . . =92 or an Info cross-reference saying =91*Note name : node.=92. @ref Used within or, more often, at the end of a sentence; same as @xref for Info; produces just the reference in the printed manual without a preceding = =91See=92. @pxref Used within parentheses to make a reference that suits both an Info file and a printed book. Starts with a lower case =91see=92 within the printed manual. (=91p=92 is for =91parenthesis=92.) @inforef Used to make a reference to an Info file for which there is no printed manual. (from the Texinfo manual) On Mon, Feb 25, 2013 at 10:32 AM, Jonathan Leech-Pepin wrote: > Hello Tom, > > On 25 February 2013 12:52, Thomas S. Dye wrote: >> >> Aloha all, >> >> IIUC, there is currently no support for @pxref{} in the texinfo >> exporter. This is a texinfo @-command that does one thing in the info >> output and another in the LaTeX output. > > > Ultimately there is actually no real difference between "see @ref{}" > and "@pxref{}". I just checked using the first @pxref{} in org.texi > (Under Activation). > > In org.texi it is shown as (@pxref{Conflicts}), in org.html it > becomes: (see Conflicts) while in the info > file (org) it is shown as (*note Conflicts::). > > Opening the info file in Info (C-u C-h i ), *node > Conflicts:: becomes "see Conflicts". Adding "see" manually > before *note does not change the output. The same is the case for > @xref{}. @xref{} adds "See" before the link in html/LaTeX, and > uses *Note in the info document; "See [[link]]" produces the same See in > html/LaTeX, and creates "See *note" in the info file (which is > inserted as "See " in Emacs Info. > > Yes the output is different if looking at the info file directly, > however when viewing it withing Emacs the text is consistent. > > I didn't implement support for @xref{} or @pxref{} in the texinfo > exporter, because I could not find a way to reliably determine the > context so as to use the right type of link in the texi file. > > Using occur there were already 47 cases in org.texi where "[Ss]ee > @ref" was used rather than the stylistically appropriate @pxref/@xref. > > Regards, > > Jon > >> >> My idea is to create a custom link type, something like this: >> >> (org-add-link-type >> "pxref" nil >> (lambda (path desc format) >> (cond >> ((eq format 'html) >> (format "%s" path)) >> ((eq format 'latex) >> (format "\\ref{%s}" path)) >> ((eq format 'texinfo) >> (format "@pxref{%s,%s}" path desc))))) >> >> I haven't tested this, but it should export approximately correctly and >> I'm confident I can get the export part working. >> >> What I can't figure out is how to have Org recognize that a link like >> this: >> >> [[pxref:Internal link]] >> >> is really an internal link, rather than an external link. I'd like to >> be able to click on this and end up at <> in the Org >> buffer. >> >> Is this possible? If so, can you point me to a solution? >> >> >> All the best, >> Tom >> >> -- >> T.S. Dye & Colleagues, Archaeologists >> 735 Bishop St, Suite 315, Honolulu, HI 96813 >> Tel: 808-529-0866, Fax: 808-529-0884 >> http://www.tsdye.com >> > --=20 Subhan Michael Tindall | Software Developer | smt@rentrakmail.com RENTRAK | www.rentrak.com | NASDAQ: RENT