emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jambunathan K <kjambunathan@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: new odt-exporter: problems with formatting in captions
Date: Tue, 17 Dec 2013 00:39:12 +0530	[thread overview]
Message-ID: <87fvps62av.fsf@gmail.com> (raw)
In-Reply-To: 86zjo09ael.fsf@gmx.de


Wrt items (1) and (2), I am planning to remove the support for short
captions.  (The caption going as part of table:name or draw:name) as
part of fix for

http://lists.gnu.org/archive/html/emacs-orgmode/2013-12/msg00100.html

The fix is not ready yet.  I am just feeling lazy after having not
looked at the code for almost an year now.

NOTE: If someone knows how to accommodate short captions (so that an
that an Index/TOC could be generated from within LibreOffice based on
it, please let me know.)

----------------------------------------------------------------

For the benefit of audience, if you use embedded images in your document
the document produced by the ODT exporter will be openable by
LibreOffice < 4.0 but not with LibreOffice > 4.1.  (In other words,
LibreOffice folks have introduced some backward incompatible changes.)

To ensure that the document produced by the exporter is usable resave
the document from within LibreOffice.  (i.e., make some trivial changes
to the ODT document and do a save again).  This way the XML produced by
the exporter will be re-written by LibreOffice and the problem will be
averted.

----------------------------------------------------------------

As a side note, I am discussing with Emacs maintainers whether they
would be comfortable about having me maintain the exporter right from
within Emacs repo.  I am not sure how the discussion will go.

http://lists.gnu.org/archive/html/emacs-devel/2013-12/msg00509.html


martin.guertler@gmx.de (Martin Gürtler) writes:

> 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&lt;text:span 
>  text:style-name="OrgSubscript"&gt;1&lt;/text:span&gt;&lt;text:span 
>  text:style-name="OrgSuperscript"&gt;2&lt;/text:span&gt;">
> ---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

  reply	other threads:[~2013-12-16 19:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-16 13:45 new odt-exporter: problems with formatting in captions Martin Gürtler
2013-12-16 19:09 ` Jambunathan K [this message]
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=87fvps62av.fsf@gmail.com \
    --to=kjambunathan@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
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).