To use TagSoup on your PC you just need to copy the .jar file to any folder on your harddrive. You can get the .jar from tagsoup-1.2.jar here. I simply copied the file to my C:\xml folder and will also use this path later in XMLSpy to enable the tool there.
So how can you use TagSoup then in XMLSpy? You need to have File Commander PRO installed. The plugin provides support for External Tools in the XML editor and we are going to add TagSoup as an external tool.
To open the settings dialog for external tools go to the Settings tab of the plugin and push the "Tools" button. You can then add TagSoup in the following dialog:
Add a new tool and give it a name. Surprisingly I took "TagSoup". Then you need to provide the command and the arguments. This is a little bit tricky because TagSoup just writes the output to the standard output and doesn't create a file. In addition it expects the filename as URI (well it does but luckily it accepts backward slashes). Therefore we provide as arguments:
/c java -jar C:\xml\tagsoup-1.2.jar "file:///$(ActiveDocPath)" > "$(ActiveDocFolder)\$(ActiveDocName).xhtml"
This line takes the current document in XMLSpy, which should be a HTML file, and creates a new file with .xhtml as file extension. This means shortly after pushing the button for the External Tool on the plugin window you can open the new XHTML file in XMLSpy. It will be written to the same folder as the source HTML.
[ 2 comments ] ( 5 views ) | permalink | related link |
( 3 / 7 )
I finished working on the dialog for XML batch validation which can be used directly from the Windows File Explorer. This is how it looks like:
The dialog allows to set all options which are available for the batch validation provided by the valbuddy.exe command-line tool. In fact the dialog allows to load and create the XML setting files and calls this tool to run the batch.
The big benefit of the dialog is that it is no longer necessary to create the XML setting files manually. Instead you simply work from the File Explorer.
[ add comment ] | permalink | related link |
( 3 / 10 )
I'm currently working on the next release of XML ValidatorBuddy and I just added code to run a batch validation in a "test" mode. This means everything is processed as it would be for the real batch except that no validation is performed. So you get a log file with all files which would be validated very quickly. This way you can see how many files are affected and also exactly which ones.
While I was testing the code it came to my mind that this feature can be used for a nice additional benefit: You can also search for your XML instance files and get a nice list of all files as XML structure. On my C drive it took 8 minutes to find more than 8000 XML documents out of 250.000 files in 23.000 folders (using the xinclude option to create the log file should make it even faster).
And then another new feature came to my mind. I will enable the batch process to take a log file as input for processing. This is a good starting point for any functionality which compares different batch runs.
[ add comment ] | permalink | related link |
( 3 / 10 )
I saw the BOSCH IXO screwdriver at the DIY (hardware) store and as I wanted to attach a board in the bathroom anyways I bought it. I have to admit this is the first cordless screwdriver I own and I'm really impressed how much easier it is to drive the screws into the wall now ;-)
If you have the right tools working can be fun. Of course this is also true for XML tools...
[ add comment ] | permalink | related link |
( 3 / 10 )
I'm currently preparing XML ValidatorBuddy 2.3.2 which is a minor release to fix only a few issues related to CSE HTML validation and Schematron support.
[ add comment ] | permalink | related link |
( 2.5 / 4 )
Next
Calendar
