From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-orgmode@gnu.org
Subject: Re: Support Freemind/Freeplane export
Date: Sun, 03 Mar 2013 09:12:49 +0100 [thread overview]
Message-ID: <87ip58ucji.fsf@Rainer.invalid> (raw)
In-Reply-To: 87lia51llv.fsf@bzg.ath.cx
Bastien writes:
> Also, the change in ox-html.el is not good IMHO: it will populate
> everyone's HTML code with unfamiliar strings (like " " instead
> of " ") just for the sake of keeping ox-freemind.el users happy.
It also requires that the HTML is output in UTF-8. I would
(reluctantly, I don't really know much about how this would work)
suggest that the export should always be done with symbolic entities and
a post-export filter should then replace them with whatever the
particular backend prefers. Does that work?
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptation for Waldorf microQ V2.22R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
next prev parent reply other threads:[~2013-03-03 8:13 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-02 18:05 Support Freemind/Freeplane export Jambunathan K
2013-03-02 21:36 ` Nicolas Goaziou
2013-03-02 22:29 ` Bastien
2013-03-02 22:49 ` Bastien
2013-03-03 8:12 ` Achim Gratz [this message]
2013-03-03 8:39 ` Bastien
2013-03-03 8:52 ` Nicolas Goaziou
2013-03-03 15:03 ` Jambunathan K
2013-03-03 16:25 ` Jambunathan K
2013-03-03 21:00 ` Nicolas Goaziou
2013-03-03 17:32 ` Bastien
2013-03-03 17:47 ` Always use utf-8 for HTML export (No support for other coding systems) Jambunathan K
2013-03-03 18:28 ` Achim Gratz
2013-03-03 18:43 ` Nagarjuna G
2013-03-03 19:39 ` Achim Gratz
2013-03-03 23:51 ` Robert Horn
2013-03-04 4:14 ` Jambunathan K
2013-03-04 7:21 ` Bastien
2013-03-04 8:04 ` Robert Klein
2013-03-04 19:01 ` Bastien
2013-03-03 17:44 ` Support Freemind/Freeplane export Jambunathan K
2013-03-03 18:20 ` Bastien
2013-03-04 1:33 ` François Pinard
2013-03-10 15:52 ` Scott Randby
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=87ip58ucji.fsf@Rainer.invalid \
--to=stromeko@nexgo.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).