Oh, good, Egon, I was hoping you would give this a try. I was pretty sure this
would happen, as I added a lot of links and wasn't really thinking XML when I
did it.
Let's work on this off-list and get back to the group. I need to talk to you
anyway about what you want to include or not in that, and how to format it.
-Bob
Egon Willighagen wrote:
Hi all,
I've had a look at the scripts to convert Bob's interactive webpages to static
DocBook XML for inclusion in the User Guide. This is how we did it in the
past:
1. Use ?xml to get XML
2. use XSLT to convert this to DocBook XML fragments
However,
the current XML output of the JavaScript is seriously broken, and only upto
pmesh goes correct, and the rest comes out as jibberish pmesh comments... :(
Bob,
I briefly tried to convert the *.js directly to XML, but could not figure out
what was what... Are you up to helping me out with this? I want to write a
Perl script that create one XML document from which we can generate the
DocBook XML...
But I need help with understanding what is the function of each *.js file
(toks, cmds, defs, exam)... Some I can figure out, but I struggle with
difference in the newCmd() lines in cmds.js... and how to interpret the
fields, and how they link with the other js files...
The current script I have is attached. Run it like this:
cat cmds.js | cmds2xml.pl
It will get you XML version...
Egon
--
Robert M. Hanson, [EMAIL PROTECTED], 507-646-3107
Professor of Chemistry, St. Olaf College 1520 St. Olaf Ave., Northfield, MN
55057
mailto:[EMAIL PROTECTED] http://www.stolaf.edu/people/hansonr
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Jmol-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jmol-developers
