Re: [O] odt export bug, I think.

[Jambunathan K]

Hello Matt

> Hi,
>
> I think I've found an odt export bug.  Certain complex URL's stored
> within links can end up being rendered with forbidden characters,
> e.g. '<' and '>'.  so, e.g., a link to this URL:
>
> http://www.jstor.org.myaccess.library.utoronto.ca/sici?origin=
> sfx%253Asfx&sici=1363-3554%25281995%252939%253C182%253E1.0.CO%253B2-L
> &
>
> was rendered in content.xml like this:
> xlink:href="http://www.jstor.org/sici?origin=sfx:sfx&amp;sici=
> 1363-3554(1995)39<182>1.0.CO;2-L&amp;"


I have some understanding of what the issue is. I would like to
know/confirm a few things before proceeding ahead:

1. How does the original URL look like? 
2. Where does the URL come from? Is it generated by an application or is
   it hand copied by you from your browser.
3. How do you enter the URL in to the org file. Specifically do you

   - Simply type it. ie type the open brackets, paste the link, paste
     the description, close  the brackets etc.
  
  Or

   - You use C-c l to store the link in Org file.

  Note that question 3 is very crucial because. This is because for the
  URL that you have provided what you see with C-c l on the link is
  different from what is actually stored in the Org file. (You can see
  how actually Org stores the link by backspacing from beyond the link
  or by toggling descriptive/literal links in the menu bar)

Please respond to Question 1 keeping behaviour in 3 mind. I am
specifically interested in seeing whether the app/database (if there is
one) actually provides a hexified link or not. I also see the
possibility that one could have handcrafted the URL in an one-off sense
by concatenating key/val pairs and forming the query string oneself. In
this case (a novice) user may not have hexified the URL to begin with.

ps: If my understanding is correct you are also having similar problems
with the html export (M-x org-export-as-html) as well. Either html file
is malformed or the link in the html export file simply doesn't
work. (TIP: odt exporter is derived from the html exporter. So it is
always a good idea to check the status of html export whenever one runs
in to issues with odt exporter)

I anticipate that fix for this issue might need some discussions with
Bastien, David Maus and may be others.

Jambunathan K.




>
> resulting in a syntax error when libreoffice tries to load it.  I've
> attached a minimal test file that reproduces the bug. 
>
> This is happening under a recent git snapshot of org-mode, using an
> emacs snapshot from 2011-04.  Not sure if there are other xml-related
> packages whose versions I should be tracking.
>
> Thanks as always, and let me know what I can do to help with this.
>
> Matt
>
>
>
>

--