From: martin.guertler@gmx.de (Martin Gürtler)
To: emacs-orgmode@gnu.org
Subject: new odt-exporter: problems with formatting in captions
Date: Mon, 16 Dec 2013 14:45:54 +0100 [thread overview]
Message-ID: <86zjo09ael.fsf@gmx.de> (raw)
Hi,
I just converted a 150 page document I used to convert to odt with the old
exporter. Following problems occurred:
1. table with #+CAPTION
If the caption contains formatting (~, ==, _, ^), the exporter
produces an invalid content.xml.
minimal example:
---8<------------------------------------------------------------
#+OPTIONS: num:t toc:nil \n:nil @:t ::t |:t ^:{} -:t f:t *:t <:nil
* First paragraph
#+CAPTION: A_{1}^{2}
| head 1 | head2 |
|-----------+----------|
| content 1 | content2 |
---8<------------------------------------------------------------
The problem can be seen in the following xml fragment:
---8<------------------------------------------------------------
<table:table table:style-name="OrgTable"
table:name="A<text:span
text:style-name="OrgSubscript">1</text:span><text:span
text:style-name="OrgSuperscript">2</text:span>">
---8<------------------------------------------------------------
The table:name attribute ends prematurely at the "OrgSubscript". This
could probably be mended by using single quotes for these attributes
inside attributes.
2. again #+CAPTION
if the caption contains a string with /escaped/ underlines (please
note the #+OPTION ^:t)
---8<------------------------------------------------------------
#+OPTIONS: num:t toc:nil \n:nil @:t ::t |:t ^:t -:t f:t *:t <:nil
* First paragraph
#+CAPTION: YYYYMMDD\_hhmmss.csv.
| head 1 | head2 |
|-----------+----------|
| content 1 | content2 |
---8<------------------------------------------------------------
The escaped _ is not detected; instead, a literal \ and subscript
are detected, and teh document is invalid as above. This escaping
seems not to be mentioned in the documentation, probably because it
is no longer valid. Might be of interest to people who want to
convert old documents.
3. the \ref syntax seems not to work anymore; substituting by \ref{text}
by [[text]] worked.
4. Empty lines between #+NAME and the respective table are no longer tolerated
remarks: I like the new smart quotes. More comfortable than putting in
the utf characters via C-8-RET (which is handy, though, for simple
formulae).
Regards
Martin
--
Dr. Martin Gürtler
Phone: +49-341-2254303
Mobile: +49-1578-4469069
next reply other threads:[~2013-12-16 13:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-16 13:45 Martin Gürtler [this message]
2013-12-16 19:09 ` new odt-exporter: problems with formatting in captions Jambunathan K
2013-12-18 10:15 ` Martin Gürtler
2013-12-16 22:31 ` Andreas Leha
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=86zjo09ael.fsf@gmx.de \
--to=martin.guertler@gmx.de \
--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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).