Hi,
I use ToDoList (abstractspoon) for a while to manage my tasks created in Freemind. I export tasks from TodoList to Freemind to create my activity report in Ooo, an d i'm french. Till RC10, no problem accents are well imported and all is fine. Since RC11, accented characters are replaced by a square. When i look in file all seems ok and if i open it in RC10, all is back...
I encountered this with importing maps from XMind (i use it sometime for ishikawa diagrams), but deleting the first line (<?xml...?>) solves the problem as Freemind is clever enough to translate it. Not this time...
Thanks for help
This difference can be caused by 0.9.0 RC11's use of UTF-8 character encoding when reading mind map files. In some RC versions of 0.9.0, FreeMind used the default encoding when reading mind map files.
The change of 0.9.0 RC11 is a response to the following bug report:
RC4 regression: incorrect viewing of UTF-8 map, 2009-06-22
http://sourceforge.net/tracker/?func=detail&atid=107118&aid=2810535&group_id=7118
The behavior of 0.9.0 RC11 as regards the used character encoding when reading mind map files should be the same as that of 0.9.0 RC3.
FreeMind natively stores non-Latin unicode characters as unicode XML entities ("ř") rather than storing them directly in a chosen encoding, so mind maps created directly by FreeMind are unaffected by the change of character encoding.
I do not know what method you use to export from TodoList to FreeMind, but what should help is if you convince the convertor to use UTF-8 character encoding in the result mind map.
Unfortunately, FreeMind does not understand the specification of character encoding present in XML declaration (<?xml version="1.0" encoding="UTF-8"?>); and FreeMind writes no XML declaration into mind map files.
--Dan
As a further explanation, using UTF-8 encoding rather than the default one has the advantage that UTF-8 is a fully international and widely used unicode encoding, unlike some of the default encodings. The default encoding depends on the locale of the operating system, and often does not cover the whole of unicode. Opening all files with UTF-8 assures uniform behavior across operating systems, one that supports all scripts and languages. A flexible alternative would be that FreeMind would read the character encoding from the XML declaration, but that is much more work right now in late 0.9.0. On another note, some programs generate FreeMind mind maps in UTF-8 (hence the bug report for 0.9.0 RC4), so whether we use UTF-8 or the default encoding, we inconvenience some users. The hope is that using UTF-8 is the most convenient option in general. --Dan
Hi,
please attach an example, and I'll have a look at it.
TIA, Chris