emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Dokos <nicholas.dokos@hp.com>
To: Csanyi Pal <csanyipal@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Exporting to FreeMind - opened in FreeMind failed
Date: Mon, 09 Jul 2012 12:22:12 -0400	[thread overview]
Message-ID: <7472.1341850932@alphaville> (raw)
In-Reply-To: Message from Csanyi Pal <csanyipal@gmail.com> of "Mon, 09 Jul 2012 17:55:22 +0200." <87bojp0w0l.fsf@debian-asztal.i-did-not-set--mail-host-address--so-tickle-me>

Csanyi Pal <csanyipal@gmail.com> wrote:

> OK
> I started emacs with the command 'emacs -Q' and did the followings:
> 
> Open the Test.org file in Org mode.
> Export the tree into FreeMind format with the command:
> C-c C-e m
> 
> Get the Test.mm file.
> 
> In the FreeMind when I open the Test.mm file, I get the following
> message: 
> 
> Error while parsing file:freemind.main.XMLParseException: XML Parse
> Exception during parsing of a map element at line 80: Expected: map 
> 
> What can I do further to solve this problem?
> 

Well, I suspect that none of us here is a freemind "expert" (I know I'm
not), with the possible exception of Lennart Borgman, the author of
org-freemind.el. So the main question is: is this a bug in freemind or
is this a bug in the org freemind export? You have not posted the org
file that produced all of this (or if you have, I cannot see it clearly
in your mail). That could help. If Lennart could be persuaded to take a
look, that might help.  And if you could be persuaded to simplify the
example (ECM = complete *minimal* example) so that it exhibits the
problem with as few nodes as possible (I count seven nodes in your .mm
file: does it need to be that complicated?), that might help.

Here is an example of an org file that produces a map that works:

--8<---------------cut here---------------start------------->8---

* foo

this
--8<---------------cut here---------------end--------------->8---

How much do you need to complicate it to produce something that does
*not* work?

Nick

  reply	other threads:[~2012-07-09 16:22 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-08 18:40 Exporting to FreeMind - opened in FreeMind failed Csanyi Pal
2012-07-09 13:24 ` Bastien
2012-07-09 13:28   ` Lennart Borgman
2012-07-09 13:40     ` Csanyi Pal
2012-07-09 13:37   ` Csanyi Pal
2012-07-09 13:42     ` Bastien
2012-07-09 13:43       ` Csanyi Pal
2012-07-09 13:53         ` Bastien
2012-07-09 14:13           ` Csanyi Pal
2012-07-09 14:34             ` Bastien
2012-07-09 14:55               ` Csanyi Pal
2012-07-09 15:23                 ` Nick Dokos
2012-07-09 15:55                   ` Csanyi Pal
2012-07-09 16:22                     ` Nick Dokos [this message]
2012-07-09 16:46                       ` Csanyi Pal
2012-07-10 15:41                         ` Manish
2012-07-10 16:52                           ` Csanyi Pal
2012-07-10 16:55                             ` Csanyi Pal
2012-07-09 14:35             ` Csanyi Pal

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=7472.1341850932@alphaville \
    --to=nicholas.dokos@hp.com \
    --cc=csanyipal@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).