1 XML Virtual FileSystem for Midnight Commander
5 View an XML file in Midnight Commander as a filesystem.
9 Version 1.1.4 (2015-03-21)
10 Minor documentation update.
12 Version 1.1.3 (2015-03-14)
13 Fix a minor bug in handling namespaces (lxml).
15 Version 1.1.2 (2015-01-10)
16 Changed link to installation instructions.
18 Version 1.1.1 (2014-07-17)
19 Fix a bug in removing excessive namespaces (lxml).
21 Version 1.1.0 (2013-11-26)
22 Show comment(s) before the root element.
24 Version 1.0.0 (2013-11-23)
25 With lxml.etree-based implementation show only child namespaces
26 (calculated as combined namespaces minus parent's namespaces).
28 Version 0.3.0 (2013-11-16)
29 Initial release. Implementation based on minidom.
33 Home page: http://phdru.name/Software/mc/xml.html
34 Download: http://phdru.name/Software/mc/xml
35 git clone http://git.phdru.name/extfs.d.git
36 git clone git://git.phdru.name/extfs.d.git
38 Installation instructions: http://phdru.name/Software/mc/INSTALL.html
41 The VFS represents tags as directories; the directories are numbered to
42 distinguish tags with the same name; numbering also helps to sort tags by their
43 order in XML instead of sorting them by name and prevents name clash when tag
44 names coincide with the names of special files used by XML VFS. Attributes,
45 text nodes and comments are represented as text files; attributes are shown in
46 a file named "attributes", attributes are listed in the file as name=value
47 lines (I deliberately ignore a small chance of newline characters in values);
48 names and values are reencoded to the console encoding. Text nodes and comments
49 are collected in a file named "text", stripped and reencoded. The filesystem is
52 Implementation based on minidom doesn't understand namespaces, it just shows
53 them among other attributes. ElementTree-based implementation doesn't show
54 namespaces at all. Implementation based on lxml.etree shows namespaces in a
55 separate file "namespaces".
57 It is useful to have a top-down view on an XML structure but it's especially
58 convenient to extract text values from tags. One can get, for example, a
59 base64-encoded image - just walk down the VFS to the tag's directory and copy
60 its text file to a real file.
62 The VFS was inspired by a FUSE xmlfs: https://github.com/halhen/xmlfs
66 Oleg Broytman <phd@phdru.name>
69 Copyright (C) 2013-2015 PhiloSoft Design