name mode size
..
Dragdrop QuakeML to Make Earthquake List HTML 100755 505B
Dragdrop XML to Make Text List of All Element Paths 100755 521B
Dragdrop XML to Pretty Print 100755 514B
Dragdrop XML to Run Element Catch-All 100755 508B
Example of Running Salty from the Command Line 100644 1kB
Make example earthquake list HTML 100644 479B
Readme.html 100644 5.51kB
Readme.html
<html><body> Salty XML Transformer was not designed with security in mind, so, I don't recommend running it on a web server on a computer connected to the internet. <p> But, if you somehow set up a local web server, then, this link might work. Though you might have to edit Salty a bit, such as to correct some default paths for things, which might be different on your system: <p> <a href="http://localhost/Salty-XML-Transformer/Salty-XML-Transformer/salty-xml-transformer.php?xml=Vuemaps/Example-Vuemap.vue&xslt=Sheets/VUE/Make-Vuemap-BG-Yellow.xsl&dest=Example-Vuemap&revuize=yes">http://localhost/Salty-XML-Transformer/Salty-XML-Transformer/salty-xml-transformer.php?xml=Vuemaps/Example-Vuemap.vue&xslt=Sheets/VUE/Make-Vuemap-BG-Yellow.xsl&dest=Example-Vuemap&revuize=yes</a> <p> <br> 22:31:41 03/28/2017. Unfortunately, plain XML files using actual Unicode characters (instead of Unicode entities) might have some or all of their Unicode characters messed up when they are transformed. Haven't figured out how to fix that yet, so, these two links won't produce satisfactory results yet: <p> <ol><li><a href="http://localhost/Salty-XML-Transformer/Salty-XML-Transformer/salty-xml-transformer.php?xml=Xmls/Example-Xml.xml&xslt=Sheets/VUE/Make-Vuemap-BG-Yellow.xsl&dest=Example-Xml">http://localhost/Salty-XML-Transformer/Salty-XML-Transformer/salty-xml-transformer.php?xml=Xmls/Example-Xml.xml&xslt=Sheets/VUE/Make-Vuemap-BG-Yellow.xsl&dest=Example-Xml</a> <p> <li><a href="http://localhost/Salty-XML-Transformer/Salty-XML-Transformer/salty-xml-transformer.php?xml=Xmls/Example-Xml.xml&xslt=Sheets/VUE/Make-Vuemap-BG-Yellow.xsl&dest=Example-Xml&mojifix=y">http://localhost/Salty-XML-Transformer/Salty-XML-Transformer/salty-xml-transformer.php?xml=Xmls/Example-Xml.xml&xslt=Sheets/VUE/Make-Vuemap-BG-Yellow.xsl&dest=Example-Xml&mojifix=y</a> </ol> <p> <br> But this other example XML file, using Unicode entities instead of actual Unicode characters, can be transformed just fine, though the output will contain Unicode entities rather than normal Unicode characters: <p> <a href="http://localhost/Salty-XML-Transformer/Salty-XML-Transformer/salty-xml-transformer.php?xml=Xmls/Example-Xml-With-Entities-Instead-Of-Unicode.xml&xslt=Sheets/VUE/Make-Vuemap-BG-Yellow.xsl&dest=Example-of-Sheet---Print-Node-Text&mojifix=y">http://localhost/Salty-XML-Transformer/Salty-XML-Transformer/salty-xml-transformer.php?xml=Xmls/Example-Xml-With-Entities-Instead-Of-Unicode.xml&xslt=Sheets/VUE/Make-Vuemap-BG-Yellow.xsl&dest=Example-of-Sheet---Print-Node-Text&mojifix=y</a> <p> <br> <b>Version 1.2 Demo</b>. Now it's possible to give Salty arguments to pass as parameters to XSLT. <p> <a href="http://localhost/Salty-XML-Transformer/Salty-XML-Transformer/salty-xml-transformer.php?xml=Xmls/Example-Xml.xml&xslt=Sheets/Print-Params.xsl&PARAM1:xpath=current-dateTime()&PARAM2:xpath=current-time()&PARAM3=just a string">http://localhost/Salty-XML-Transformer/Salty-XML-Transformer/salty-xml-transformer.php?xml=Xmls/Example-Xml.xml&xslt=Sheets/Print-Params.xsl&PARAM1:xpath=current-dateTime()&PARAM2:xpath=current-time()&PARAM3=just a string</a> </ul> <p> <br> <hr> <p> <br> It's also possible to run Salty from a command line. <p> In the same folder as this Readme, there's a Bash script named "Example of Running Salty from the Command Line" which demonstrates this. <p> (Because I currently don't have the energy or patience to make Salty perfect, all Salty output goes to somewhere inside the folder <code>/root/Web-Server/Salty-XML-Transformer-Output/</code> regardless of whether or not you're actually using a web server.) <p> <br> <hr> <p> <br> <pre> Command line arguments: Arg 1: A path to an XML file or VUE map to be transformed. Arg 2: A path to an XSLT sheet which will be used on the file pointed out by Arg 1. Optional Arg 3: Set to "y" or "yes" or "revuize" (all equivalent) to set "should_convert_output_back_to_vue_format" to true. Makes Salty run the included Salty-related Perl script "unrelocvuecomments" (whose longer name is "Undo Moving a VUE Map's Top Comment Lines Into a CDATA Section") on the XSLT output. Optional Arg 4: A path to the file where output should go. Must be inside whatever path is in the Dest_Folder constant. By default, that path is: "/root/Web-Server/Salty-XML-Transformer-Output/" Relative paths are assumed to be in there. (Except if the path contains dots that lead out of that folder.) Optional Arg 5: Set to "y" or "yes" or "mojifix" (all equivalent) to set "should_try_to_convert_trashed_unicode_to_entities" to true. Makes Salty run the included Salty-related Perl script "somehow-fix-unicode-garbage-in-Salty-XML-Transformer-output" on the XSLT output. (Moji is short for mojibake, "the name for incorrect, unreadable characters shown when computer software fails to show text correctly.") All args beyond Arg 5 are assumed to be parameters that should be passed into the XSLT sheet being used. If a parameter's value should be interpreted as an Xpath statement, put ":xpath" after the parameter's name. Example: time:xpath=current-dateTime() Everything else is assumed to be something other than an Xpath. By default, Salty converts non-Xpath parameters to XdmValues using Saxon's createAtomicValue function. <p><br><hr><p><br> Getvars (when run in web mode) "xml" = Arg 1 above "xslt" = Arg 2 above "revuize" = Arg 3 above "dest" = Arg 4 above "mojifix" = Arg 5 above Any other name = Assumed to be a parameter for XSLT. </pre>