It automatically produces a tabular display of any selected tag by collecting repeating attribute and tag names and then arranging them into columns. The result is a clutter-free and informative tabular display.
The implementation is very efficient te memory and CPU resources so you can quickly navigate through very large XML files up to about 500 megabytes.
More features include table sorting, syntax-highlighting editor, automatic indentation/pretty-printing of exiting code, drill down, as-you-type syntax checking, bookmarks, convert to spreadsheet, Branch Selector, non-collapsing editing and more.
XML Marker have total internationalization support with both Unicode/utf-8 and code pagina encoding.
Interesting UI and elementary to use.
Quick and nicely done, however when set spil default XML editor te folder options the editor will not open XML fie from the Flight Simulator gauge viewer. Come up with \“can\’t find C:\\Documents\” error. Other XML editors set spil default work fine.
Text substitute has a bug: If you substitute s1 with s2 where s1 is a substring of s2, it goes (obviously) into a endless recursion.
Nice editor! I would like to see Ctrl+Huis (go to the beginning) and Ctrl+End(got to the end of the document) supported. When selected text is deleted (working with shift+arrows), next selection starts at the very beginning of the document, which can cause accidental deletion of parts of the document you don\’t want to delete.
Very nice error reporting while typing. I will be glad to have a ordinary \“intellisense\” feature- when you type a \”>,\” to have closing tag added automatically for you. It will be good also if the document tree on the left doesn\’t close everytime you type something…. no matter the document is not well formed at the time of typing it will be good if there is a \“less restricted\” way of analyzing it so the tree doesn\’t close.
Indeed valid points. All, except the intellisense, will get stationary ter the upcoming next version.
After using XML Marker for a while I\’ve noticed one annoying detail. The scroll down arrow scrolls one line at a time but the scroll up button scrolls numerous lines at a time. Don\’t know if this is intentional or a coding bug.
I have successfully reproduced the bug and motionless it. The fix will be available te the upcoming next version.
There seems to be a problem with any unicode character with a hex code containining 22 eg c? (a chinese character) hex value = 7522 . The 7522 gets interpreted spil \\\“u (\\\” = hex 22, u = hex 75) It finishes up with an error like Gegevens = \\\”\\\“u\\\”
I can\’t tell you how blessed I feel, witnessing development embarking on this invaluable contraption.
This has for a long time bot a favourite contraption of mine ter my XML toolkit. So glad to hear it is to get more love with version Two
It’s a very useful program.
But I’ve a feature request:
Please notice that the XML opstopping has bot modified outside of the XML Maker and conditional reload the verkeersopstopping.
Love this software. I too am enthusiastic to see it’s getting more attention ! 🙂 When can wij expect a fresh version ? Thanks!
It should be released within about a month. Sorry for the very long delay.
Any update on the fresh version ??
This program is amazing. I have attempted out a handful of different XML Editor contraptions, and none of them come close to this. XML Marker is very quick, takes little memory, but is still powerful. Right now I am using it to navigate through a 100MB opstopping, and it has no problems.
Agree with previous comment – this runs circles around many ‘professional’ XML viewers (which, of course, can do much more, but don’t have the finesse displayed here!)
Indeed looking forward to next release! – I tagged this spil ‘abandoned-ware’, excellent to learn it’s not!
I weerklank that sentiment – and I have many of those ‘professional’ viewer/editors. I’m truly looking forward to your release of the UTF -8 compliant version of this product. Thanks for providing the XML community with such a superb implement!
very nice to use, especially the table view, with a possible ordering method for each katern.
A nice to have feature will be a “double click” or “shortcut key” to open the “Edit using Editor” feature te the table selection Browser.
This also has for a long time bot a favourite implement of mine. Cant wait for v2
I indeed like this editor and use it all the time. the only thing I miss ter comparison with XMLS py is a notification and update if the opstopping has bot externally switched.
Excellent program – I wasgoed looking for a program that could graphically display a DTD schema. I embarked looking at Altova and other paid program when I came acroos this and it’s ideal for the elementary use I want it for.
Looking forward to the next release.
Thanks for the good device!
Any chance you could provide feature like, say dual click the Tree Selection Browser window and it maximizes the panel to ease the viewing?
Just downloaded to flow a large verkeersopstopping that I had bot able to view te previous version, but had not had tree. This opstopping is 1.Trio gb. It can read ter the entire verkeersopstopping but vanishes during the parsing? Can I still use the old version?
yes, you can use the old version. They are designed to work side by side. I am not sure I understand the particular problem, can you elaborate and send the problem verkeersopstopping?
You’ve got a nice program, and I would have considered buying it because I need an application that will treat 100Mb+ XML files without problems, but somehow your app misses that XML tags can be not only te Latin letters but te other languages also. I live ter Russia and here I have to work with XML files that have tag names te Russian like <,>,<,/>, and the encoding attribute te the XML declaration clearly states:
Your application treats the tag names te Russian like:
Warning: Expecting char gegevens
Error: Unexpected text
Error: Invalid unicode sequence.
I’ve a question to ask will your software support national encodings or I will have to look for something else?
Xml marker Two.0 exclusively uses the Unicode standard for all non-Latin languages. Unicode emerges to suit most users and is the recommended encoding for all applications. There should be support for non-Unicode encoding te one of the future releases of XML Marker, but it is a rather low priority feature. The main development effort right now if DTD and Schema visualization and validation.
Update: non-Unicode encoding is now working te the development version and should be available spil a free update ter the next month or so.
Fine to see an update – loved v1.* 🙂
I’d indeed like a feature where I could select some text ter the ‘top right’ window (is there a name for that window?) and then locate its position ter the tree view.
I also like version version 1.1, but version Two.1 is so much better and is due for a free update that includes:
- DTD and Schema validation and visualization
- Tree and grid searches
- Code pagina encoding
About the The locate the text: Click anywhere te the text window and then click the locate ter tree icon, or press Ctrl+L
I am glad you like it. version Three.0 (a free update to version Two.1) should be out soon and will include the following:
- DTD and Schema validation and visualization
- Tree and grid searches
- Code pagina encoding
About the The locate the text: Click anywhere ter the text window and then click the locate ter tree icon, or press Ctrl+L
Very nice – treats large files truly well, effortless to use. Would like a tabbed interface so I could open numerous files ter the same example.
1.1 is my dearest xml editor! I use it mostly for viewing xml files from different sources. When testing Two.1 it stops at an “Invalid Unicode Sequence”. For mij this is not a problem, but parsing stops. Could you add a way to disregard this error, label it spil a warning or permit parsing to proceed when errors?
Any plans on making a 64bit version?
Yes. 64 bit version should be released ter the next version among the following features.
DTD and schema validation and visualization.
Improvements to permit thicker files (64 bit version and some efficiency fixes)
Search te grid and tree.
Filtering using XPath and regular expression
The Indent feature – how do I liquidate the indentation before saving? This capability is written ter the feature description but not the method.
The only way to eliminate the indentation is to use the undo instruction. Merienda you do that you will lose all the switches that you have done after the indent. The reason is that the indent function switches the document by adding and removing spaces and fresh line characters.
Somewhere ter the future there should be an option to undo the indent without undoing subsequent switches. It will be implemented by adding aparente spaces and fresh lines that are now present te the document itself.
There is a problem with the indentation, when it creates fresh lines, only Linefeed is used for creating fresh lines instead of Carriage Come back + Linefeed.
This is truly noticeable when you then select all, copy and then paste into notepad, and it’s just pasted ter spil one big line.
Could this be immobile please? It works te v1.1.
I have managed to recreate the problem and will fix it on the next version. Spil a workaround, use the dos2unix guideline line program to convert the line ending of the verkeersopstopping.
An effortless way to obtain dos2unix is by installing git.
#1) I’d like the equal sign (after attributes) to NOT have spaces packaged around them (or make it configurable).
#Two) I’d like an “un-indent” (wij often work with XML ter configuration strings, and it would be nice to be able to EDIT the XML te XML Marker, but get it all back spil one continuous line of text to waterput back te our configuration string).
#Trio) It would be Truly nice to be able to see the XPath of a given knot (maybe te the Status line, but I’d choose something I could waterput on the clipboard).