Workflowy now supports exporting to OPML

Posted by Dr Andus
Jun 2, 2013 at 10:47 AM

Alexander Deliyannis wrote:
>I suspect that the issue is rather fundamental and relates to the
>codepage used for the files. You can open the OPML files in a text
>editor and see at the top of the XML description what encoding they use.
>I suspect that Bonsai can only recognise the simple latin character set,
>while Carbonfin recognises others, but encodes everything into this.

I see… Actually I’m not focusing on the accented characters issue any more, as CarbonFin wasn’t able to import those either and I could avoid using them, if necessary (mostly people’s names). CarbonFin gave me the error message “Unable to import this outline. Could not decode to unicode - xml encoding was either wrong or missing and UTF-8 didn’t work.” So I imported the opml file where I manually removed accented characters. I’m more concerned with the other problem, the inability to import inline notes.

Regarding the XML/OPML description, the following happened:

The original Workflowy export file says

Once it’s been roundtripped (and fixed) via CarbonFin, it says

So it seems that CarbonFin somehow changed it back to an older format (?), which could also display the inline notes.