emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Matt Price <moptop99@gmail.com>
To: Org Mode <emacs-orgmode@gnu.org>
Subject: odt export bug, I think.
Date: Tue, 16 Aug 2011 16:52:46 -0400	[thread overview]
Message-ID: <CAN_Dec_ibAgbGFuhdWP60FpKuRKt5uK6hVf7gGF78jW--E_Mrg@mail.gmail.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 848 bytes --]

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;"

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

[-- Attachment #1.2: Type: text/html, Size: 1241 bytes --]

[-- Attachment #2: test.odt --]
[-- Type: application/vnd.oasis.opendocument.text, Size: 8346 bytes --]

[-- Attachment #3: test.org --]
[-- Type: application/octet-stream, Size: 268 bytes --]

- Massey, Doreen. “[[http://www.jstor.org/sici?origin=sfx%g3Asfx&sici=1363-3554%281995%2939%3C182%3E1.0.CO%3B2-L&][Places and Their Pasts.]] History Workshop Journal 39 (Spring 1995): 182-192
- Novick, Robert "The Defense of the West," ch. 10 of /That Noble Dream/ 

next             reply	other threads:[~2011-08-16 20:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-16 20:52 Matt Price [this message]
2011-08-17 23:47 ` odt export bug, I think Jambunathan K
2011-08-18  0:44   ` Matt Price

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAN_Dec_ibAgbGFuhdWP60FpKuRKt5uK6hVf7gGF78jW--E_Mrg@mail.gmail.com \
    --to=moptop99@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).