RE: [Orgmode] link export confused when URL parameter is another URL

[Cook, Malcolm]

David,

Thanks for your sleuthing.....

I've not been digging on orgmode internals, so I defer to you of course.  

But it seems to me that the [[link][text]] pattern might provide a context in 
which embedded links are not sought (i.e. there is no link internal to 
top-level link).

Just a thought.... perhaps expressible as a context-free-grammar.

Cheers back,

Malcolm
 

-----Original Message-----
From: David Maus [mailto:address@hidden 
Sent: Wednesday, October 20, 2010 11:36 PM
To: Cook, Malcolm
Cc: 'address@hidden'
Subject: Re: [Orgmode] link export confused when URL parameter is another URL

At Thu, 30 Sep 2010 15:17:00 -0500,
Cook, Malcolm wrote:
>
>
> If find that this orgtext
>
>       [[http://www.foo.com/foo?URL=http://www.bar.com][test]]
>
> exports to html incorrectly as
>
>       
> [[http://www.foo.com/foo?URL=[[http://www.bar.com][test][http://www.ba
> r.com][test]]]
>
> using today's fresh git pull make install
>
> Any pointers?

The problem here is that Org's (legacy) support for plain links (i.e. without 
square brackets) kicks in and transforms the fragment part to a normal square 
bracket link.

My regexp-foo is not as it should be, but I am on this one to fix it; What we 
need to express in `org-export-normalize-link' is, that a plain link is 
something that looks like a hyperlink but not preceded directly by a square or 
angle bracket and not after a question mark followed by zero or more 
no-whitespace-characters.

Best,
  -- David
--
OpenPGP... 0x99ADB83B5A4478E6
Jabber.... address@hidden
Email..... address@hidden