Well, let's go through the differences:
1. Header comment. I happen to like it the way it is, because I think it makes it easier to see the start of an event if you're scrolling rapidly through a file. I could change this quite easily if enough people like it the other way, though.
2. Indentation level. I use four spaces rather than one tab. I think I had a reason for this, but I can't remember for sure...
o Again, if people would rather have a tab, I can change this easily.
3. Empty trigger. In the EUG parsing engine, objects with three or fewer children are printed on one line -- UNLESS their name is "trigger", "and", "or", "not", or anything starting with "action_". Perhaps I should make an exception to the exception if they are empty....
4. Comments for event name, description, and action name. I can do it that way easily enough, IF I can find a place for a comment field. I'll see what I can do.
5. Blank lines before and after the dates. This, I cannot do. If I were merely printing out text, this would be trivial; however, I am actually loading the event data dynamically (just like I would load an event from a file). Therefore, to make this change, I would have to add a special check in EVERY OBJECT I EVER LOAD (which I think is undesirable). Sorry, but I just can't do it.
Thanks for your input!