From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jonathan Leech-Pepin Subject: Re: pxref in texinfo export Date: Mon, 25 Feb 2013 17:06:03 -0500 Message-ID: References: <87hal0dqgn.fsf@gmail.com> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=20cf307f3b623f442e04d693bf16 Return-path: Received: from eggs.gnu.org ([208.118.235.92]:40490) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UA6BT-0002Xr-N0 for emacs-orgmode@gnu.org; Mon, 25 Feb 2013 17:06:09 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UA6BR-0003rD-3o for emacs-orgmode@gnu.org; Mon, 25 Feb 2013 17:06:07 -0500 Received: from mail-vc0-f174.google.com ([209.85.220.174]:52635) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UA6BQ-0003qw-VI for emacs-orgmode@gnu.org; Mon, 25 Feb 2013 17:06:05 -0500 Received: by mail-vc0-f174.google.com with SMTP id n11so2058244vch.33 for ; Mon, 25 Feb 2013 14:06:04 -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: Subhan Tindall Cc: Org-mode , Nicolas Goaziou --20cf307f3b623f442e04d693bf16 Content-Type: text/plain; charset=UTF-8 Hello On 25 February 2013 16:48, Subhan Tindall wrote: > I don't think there is a specific context that can clearly separate > them. The differences are largely semantic, not syntactic. What is > needed is some sort of marker on the tag in the original file telling > it what kind of link is to be used. > Agreed, although there is a semi-syntactic method potentially. > > On Mon, Feb 25, 2013 at 1:38 PM, Nicolas Goaziou > wrote: > > Hello, > > > > Jonathan Leech-Pepin writes: > > > >> I had to compare these possible outcomes when working on the texinfo > >> exporter. Since links are parsed before being included in their > >> paragraphs, I did not have a way to obtain context and therefore > >> attempt to guess (and be successful) at which type of reference was > >> intended by a link in Org. > > > > What kind of context would you need to know? The string that will be > > exported just before the current ref link? > > For @xref{} I would need to know if it was at the start of a sentence and followed by a comma or period. For @pxref{} I would need to determine if it was at end of sentence, mid sentence followed by a comma or within parentheses, and not preceeded by "see" or "see". Although even this would not suffice, since there are contexts where @ref{} is the better choice. Allowing for attributes on the links would allow for differentiating, however the alternative (which is the current behaviour) is just to create them all as @ref{} and then include the semantic context (See, see or nil) as appropriate for export. Regards, Jon > > Regards, > > > > -- > > Nicolas Goaziou > > > > -- > Subhan Michael Tindall | Software Developer > | smt@rentrakmail.com > RENTRAK | www.rentrak.com | NASDAQ: RENT > --20cf307f3b623f442e04d693bf16 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hello

On 25 February 2013 16:48, Subhan T= indall <subhan.tindall@rentrakmail.com> wrote:<= br>
I don't think there is a specific context that can clearly separate
them. The differences are largely semantic, not syntactic. What is
needed is some sort of marker on the tag in the original file telling
= =C2=A0it what kind of link is to be used.

Agreed, although there is a semi-syntactic method potentially.
=C2=A0

On Mon, Feb 25, 2013 at 1:38 PM, Nicolas Goaziou <n.goaziou@gmail.com> wrote:
> Hello,
>
> Jonathan Leech-Pepin <jonathan.leechpepin@gmail.com> writes:
>
>> I had to compare these possible outcomes when working on the texin= fo
>> exporter. =C2=A0Since links are parsed before being included in th= eir
>> paragraphs, I did not have a way to obtain context and therefore >> attempt to guess (and be successful) at which type of reference wa= s
>> intended by a link in Org.
>
> What kind of context would you need to know? The string that will be > exported just before the current ref link?
>
=C2=A0For @xref{} I would need to know if it was at the start = of a sentence and followed
by a comma or period.
For @p= xref{} I would need to determine if it was at end of sentence,=C2=A0
mid sentence followed by a comma or within parentheses, and not precee= ded by
"see" or "see". =C2=A0Although even th= is would not suffice, since there are contexts where
@ref{} is th= e better choice.

Allowing for attributes on the links would allow for di= fferentiating, however the
alternative (which is the current beha= viour) is just to create them all as @ref{} and
then include the = semantic context (See, see or nil) as appropriate for export.

Regards,

Jon
=C2=A0<= /div>
> Regards,
>
> --
> Nicolas Goaziou



--
Subhan Michael Tindall | Software Developer
| smt@rentrakmail.com
RENTRAK | www.rentrak.= com | NASDAQ: RENT

--20cf307f3b623f442e04d693bf16--