Ticket #5 (new enhancement)

Opened 5 years ago

Last modified 4 years ago

MXML version number

Reported by: Freddie Akeroyd Owned by: Mark Koennecke
Priority: minor Milestone: 4.3.0
Component: applications Version:
Keywords: Cc: ROsborn@…

Description

Reported By: Ray Osborn <ROsborn@…>

The MXML version number appearing in the global attributes of a NeXus file is set manually to 2.0 even though, in the example below, the actual version number was 2.2.2.

$ NXbrowse NXtest.xml NXBrowse 3.0.0 Copyright (C) 2000 R. Osborn, M. Koennecke, P. Klosowski

NeXus_version = 3.0.0 XML_version = mxml-2.0 file_name = NXtest.xml file_time = 2005-05-25 12:12:10-0500

Mark, I believe that this is really a problem with the MXML library. Can you persuade the author to put in the version number into the MXML header file so that it can be correctly determined by the NAPI? Otherwise, I think we should just state that the XML_version is 'mxml' without any version number at all.

I modified the string to mxml as proposed in order to fix this quickly. I will propose a mxmlGetVersion function to the author of mxml which will take longer as this is not a critical bug.

Mark

Change History

comment:1 Changed 5 years ago by Peter Peterson

  • Milestone set to NeXus 4.1

comment:2 Changed 5 years ago by Freddie Akeroyd

  • Component set to applications
  • Milestone changed from NeXus 4.1 Ready to NeXus 4.2 Ready

comment:3 Changed 4 years ago by Mark Koennecke

  • Milestone changed from NeXus 4.2 Ready to NeXus 4.3 Ready
Note: See TracTickets for help on using tickets.