Usage

The examples assume that you have configured your environment in a way that you can call freemind2wikigui, freemind2wiki, fm2confl and confl2fm.

The command-line tools will read from standard input if the source parameter is not given. Also, the converter will write to standard output if the target parameter is not given.

You may consider to use the Confluence WebDAV Plugin. The converter may then directly create pages in Confluence. No more copying & pasting.

Converting mind-maps to Confluence markup

The following examples produce equal results.

freemind2wiki --convert freemind2confluence --source mindmap.mm --target mindmap.txt
fm2confl --source mindmap.mm --target mindmap.txt
fm2confl -s mindmap.mm -t mindmap.txt

# the same, working in Linux environments
cat mindmap.mm | fm2confl > mindmap.txt

Converting Confluence markup to a mind-map

The following examples produce equal results.

freemind2wiki --convert confluence2freemind --source mindmap.txt --target mindmap.mm
confl2fm --source mindmap.txt --target mindmap.mm
confl2fm -s mindmap.txt -t mindmap.mm

# the same, working in Linux environments
cat mindmap.txt | confl2fm > mindmap.mm

Using the rudimentary graphical user interface

# launch the gui, terminal will stay opened
freemind2wikigui

Changing the character encoding

By default, freemind2wiki uses the default character encoding specified by your environment. You may change the character encoding either by passing parameters on the command-liine or by editing etc/freemind2wiki.conf. Command-line parameter settings will override definitions in the configuration file.

Command-line:

# will decode the mind-map using UTF8 and save the generated markup in US-ASCII charset.
fm2confl --source mindmap.mm --target mindmap.txt --source-charset UTF8 --target-charset US-ASCII

# will decode the markup using US-ASCII and save the generated mind-map in UTF8 charset.
confl2fm --source mindmap.txt --target mindmap.mm --source-charset US-ASCII --target-charset UTF8

The configuration file (etc/freemind2wiki.conf) is self-documenting and it is not explained here.