Menu

v1.5.7 shows file format changes which are incompatible with older FP versions

nnako
2016-02-19
2016-02-21
  • nnako

    nnako - 2016-02-19

    Hi,

    I installed and started the recent preview version of Freeplane (v1.5.7_beta_pre02 from the download area). After opening, modifying and saving some of my maps, I am no longer able to open them in any previous version (I tried v1.2.23, v1.3.15 and v1.5.5). Until not long ago, I was always able to open any map with any old Freeplane application, saved using Freeplane up to v1.5.5 . Some new functions would of course not have been available, but the map in general could at least be read.

    Unfortunately, the changes log does not mention any of the recent format incompatibilities. So, looking into the MM files of the different versions, I saw some changes:

    • until v1.3.15 (as well as v1.2.23)

      • HTML is stored in a block structure encapsulated in a richcontent tag within a node tag
      • ...
    • in v1.5.5

      • HTML content is serialized within the TEXT attribute of a node tag
      • a new value defaultstyle.attributes for attribute LOCALIZED_TEXT within the stylenode tag
      • some new attributes are introduced e.g. new STYLE bubble in stylenode tag
      • ...
    • from v1.5.6

      • HTML contnt seems to be represented as until in v1.3.15 again (block structure)
      • a new fit_to_viewport attribute in the properties tag within the hook tag
      • MAX_WIDTH attribute of a stylenode tag with a new unit "px"
      • ...

    It seems that the last mention (the "MAX_WIDTH" with "px" unit) causes the incompatibility. At least, removing the attribute from the respective tags facilitates a successful read operation into older FP versions.

    Is there any workaround possible to ensure backwards compatibility of the MM file? Could this workaround be realized within future FP versions?

    Thank you for considering this request.

     

    Last edit: nnako 2016-02-19
  • Dimitry Polivaev

    I am sorry, format backward compatibility to older freeplane versions is not possible.

     
    • Igor Garcia Olaizola

      Oh! Does it mean that export developers have to adapt our parsers? i didn't test my LaTeX and Beamer exporting xsl filters but if the mm XML spec. has been modified, there will be for sure new incompatibilities.

      Is there somewhere any info regarding these modifications?

      Best,

      Igor

      On 20 Feb 2016, at 12:15, Dimitry Polivaev dpolivaev@users.sf.net wrote:

      I am sorry, format backward compatibility to older freeplane versions is not possible.

      v1.5.7 shows file format changes which are incompatible with older FP versions

      Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/freeplane/discussion/758437/

      To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/

       
    • Ken Hill

      Ken Hill - 2016-02-20

      Even when I export a 1.5.7 map to FP 1.1 it does not open in 1.3.16.

      Is that expected behavior?

       
  • Dimitry Polivaev

    You are right, the export should be fixed.
    I created ticket https://sourceforge.net/p/freeplane/bugs/2327/