From: "L.C. Karssen" <lennart@karssen.org>
To: emacs-orgmode@gnu.org
Subject: Re: [BUG][ODT] ODT_STYLES_FILE not read as a list
Date: Mon, 19 Nov 2018 18:21:28 +0100 [thread overview]
Message-ID: <fbadce2b-dc66-7dca-774d-d8066bab292d@karssen.org> (raw)
In-Reply-To: <871s7tcpps.fsf@nicolasgoaziou.fr>
[-- Attachment #1.1: Type: text/plain, Size: 1911 bytes --]
Dear Nicolas,
I saw you changed a couple of things in the ODT exporter code recently.
I installed version (9.1.14-9-g131531-elpa today to see if those commits
fixed the issue(s) discussed in this thread. However, exporting to ODT
with a quoted template file name (#+ODT_STYLES_FILE) still doesn't work.
The window is split and a new (empty) buffer is created. The following
error message appears in *Messages* (note the escaped double quotes):
OpenDocument export failed: Invalid specification of styles.xml file:
"\"my_template.ott\""
The name of the newly created buffer is identical to this message.
The export works when the style file is not enclosed in double quotes.
Best regards,
Lennart.
On 10-11-18 09:16, Nicolas Goaziou wrote:
> Hello,
>
> "L.C. Karssen" <lennart@karssen.org> writes:
>
>> Taking the risk that the manual is lagging behind the actual code, I see
>> the following:
>>
>> #+ODT_STYLES_FILE: uses quotes
>>
>> #+INCLUDE: uses quotes
>> #+TEXINFO_FILENAME: doesn't use quotes [1]
>>
>> #+SETUPFILE: no example in the manual
>> #+HTML_INCLUDE_STYLE: no example in the manual, not sure if this
>>
>> requires a file or CSS code
>>
>> Another point to consider: would requiring quoted filenames make life
>> easier for people using spaces etc. in their filenames? In that case I'd
>> vote for quotes.
>
> Org allows both quoted and unquoted filenames. It is a bug if you spot
> a location where it is not the case. I fixed TEXINFO_FILENAME.
>
> HTML_INCLUDE_STYLE keyword doesn't exist anymore.
>
> It doesn't matter which type the manual uses, IMO.
>
> Regards,
>
--
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
L.C. Karssen
's-Hertogenbosch
The Netherlands
lennart@karssen.org
http://blog.karssen.org
GPG key ID: A88F554A
-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2018-11-19 17:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-30 20:47 [BUG][ODT] ODT_STYLES_FILE not read as a list Christian Moe
2018-10-30 20:49 ` Christian Moe
2018-11-04 22:05 ` Nicolas Goaziou
2018-11-05 8:49 ` Christian Moe
2018-11-06 15:18 ` L.C. Karssen
2018-11-06 15:35 ` Christian Moe
2018-11-06 16:15 ` L.C. Karssen
2018-11-07 8:28 ` Christian Moe
2018-11-07 15:32 ` L.C. Karssen
2018-11-10 8:16 ` Nicolas Goaziou
2018-11-19 17:21 ` L.C. Karssen [this message]
2018-11-19 22:58 ` Nicolas Goaziou
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=fbadce2b-dc66-7dca-774d-d8066bab292d@karssen.org \
--to=lennart@karssen.org \
--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).