Character encoding: Difference between revisions
From FreeMind
Jump to navigationJump to search
Dan Polansky (talk | contribs) No edit summary |
Dan Polansky (talk | contribs) No edit summary |
||
| Line 19: | Line 19: | ||
* There is no or little support for XML declaration at the top of the mind map file; to be tested and clarified. | * There is no or little support for XML declaration at the top of the mind map file; to be tested and clarified. | ||
* Probably no writing in UTF-8, as per above. | * Probably no writing in UTF-8, as per above. | ||
==See also== | |||
* [[File format]] | |||
[[Category:Development]] | [[Category:Development]] | ||
Revision as of 14:26, 6 June 2023
FreeMind stores unicode characters as XML character entities into mind map files.
Reading of UTF-8 encoded mind map files is supported to some extent; to be researched and documented.
Writing of UTF-8 is probably not supported; there was a feature request for this.
Implementation
- Class FileReaderCreator in MindMapMapModel uses UTF-8 as the character encoding: 'return new UnicodeReader(new FileInputStream(mFile), "UTF-8");'
- The above class is instantiated in MindMapMapModel.loadTree(final File) method.
- Which is called from MindMapMapModel.load(File file).
Links:
- MindMapMapModel.java, sourceforge.net
Tracker items
- RC4 regression: incorrect viewing of UTF-8 map, bug, sourceforge.net
Limitations
- There is no or little support for XML declaration at the top of the mind map file; to be tested and clarified.
- Probably no writing in UTF-8, as per above.
