From: torys.anderson@gmail.com (Tory S. Anderson)
To: emacs-orgmode@gnu.org
Subject: Re: Orgmode → ODT: Certain chars break export
Date: Fri, 13 Feb 2015 10:18:24 -0500 [thread overview]
Message-ID: <87egpt6drz.fsf@gmail.com> (raw)
In-Reply-To: <87386avzrl.fsf@gmx.us> (rasmus@gmx.us's message of "Fri, 13 Feb 2015 12:04:14 +0100")
From a user perspective just stripping the characters seems best to me, but finding out what the characters seems obnoxious. Neither a quick search nor skimming the ODT doc specification[1][2] seem to give any insight into a set of illegal characters. Does elisp have anything similar to Java's "isWhitespace"[3] that could be used to check character features?
Rasmus <rasmus@gmx.us> writes:
> torys.anderson@gmail.com (Tory S. Anderson) writes:
>
>> While we're on the topic of ODT export problems: I was in the process
>> of converting PDF to Text to Org to ODT/DocX and discovered that
>> certain characters seem to break exported odt documents, which fail
>> with a line and col number. So far the only one I know for sure is the
>> "\f" (Char: C-l (12, #o14, #xc)). Hopefully a single fix can handle
>> all such cases.
>>
>> You probably don't need it, but I verified with the following file:
>> http://toryanderson.com/files/breakorg.org
>
> The export is fine, but the produced XML is invalid since it contains an
> illegal character. But how to resolve this? Should ox strip illegal
> charterers (if so what are they)? If so, could they be used for entities?
>
> —Rasmus
Footnotes:
[1] https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office
[2] http://docs.oasis-open.org/office/v1.2/os/OpenDocument-v1.2-os-part1.html#__RefHeading__1415196_253892949
[3] http://www.fileformat.info/info/unicode/char/000c/index.htm
next prev parent reply other threads:[~2015-02-13 15:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-13 10:45 Orgmode → ODT: Certain chars break export Tory S. Anderson
2015-02-13 11:04 ` Rasmus
2015-02-13 15:18 ` Tory S. Anderson [this message]
2015-02-13 16:07 ` Rasmus
2015-02-13 16:41 ` Tory S. Anderson
2015-02-14 1:18 ` Rasmus
2015-02-14 8:50 ` Vaidheeswaran
2015-02-14 10:43 ` Vaidheeswaran
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=87egpt6drz.fsf@gmail.com \
--to=torys.anderson@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).