A Remote Edit Test Post

  I have created this post with Scripting2 on 7/11/10; 1:44:51 PM BST.
  Hopefully, my next modification will be from iJot.
  Well, not quite yet. It seems the latest released verion of scripting2, which I am using to write this post, is 0.28. The 2 new OPML attributes used to identify the publishing server and user name start with version 0.29.
  In the meantime, I'll work from a locally doctored OPML file.
  Well, with a little help from my friend(s), I'm now on version 0.29a :-)
  On with the experiment...
  Now that I have reposted, the top heading of this entry does include the 'server' and 'username' attributes.
  Right, I now have all the interface coded in webOutliner and iJot. All that's left is coding the actual xml-rpc transaction on iJot's back end. This should be pretty straightforward, so Murphy willing, my next modification to this post should be from iJot.
  So... Is this modification being published ? Wow it sure works as advertised.
  Now I need to release the code to the alpha server.
    Done.
  Back on the scripting2 end, everything almost work. It does work pretty well actually, although I can no longer use the version in my workspace, which is now outdated by my various modifications in iJot.
    There is still a bug though: even if see the modifications in the published page, and reload the source outline in scripting2 for further modification, the opml version which was saved by edit.scripting2.com no longer loads in iJot. More investigations are in order.
  Ok, so when the OPML is saved on edit.scripting2.com by the xml-rpc server as a result from my call to scripting2.savePost, the order of the attributes for the xml tag line is inverted again:
    The outline starts with <?xml encoding="utf-8" version="1.0"?> even though the opml text passed to the savePost function as third parameter was <?xml version="1.0" encoding="utf-8"?>
    The attributes inversion seems to cause all browser based XML parsers to reject the XML as malformed.
    But curiously, the OPML documents I generate directly from the scripting2 tool have the attributes in the proper sequence.
    Found out the code in scripting2 was expecting an OPML document encoded in ISO-8859-1. As a matter of fact, the whole of Frontier seems to be dealing in ISO-8859-1.
    Whereas iJot's XML is all encoded in UTF-8. Should not be a problem, but it turns out the code to re-order the tag attributes in scripting2 expects an ISO-8859-1 encoding declaration.
    So now iJot re-encodes the OPML text to ISO-8859-1 before saving it back to scripting2. Let's see if this works better...
    The opml is saved properly. But this post seems to have problems rendering on scripting2...