Comment 15 for bug 286567

OK, thanks for the updated script! It runs to completion, and indeed prints debugging info. The curious part is that the typical event looks like this:

......BEGIN:VEVENT
......DTSTAMP:20081022T164250Z
......ORGANIZER;CN=Tim Holy:MAILTO:<email address hidden>
......CREATED:20060412T212539Z
......UID:libkcal-1053224003.358
......SEQUENCE:1
......LAST-MODIFIED:20060413T131556Z
......SUMMARY:Some event
......PRIORITY:3
......LINESTARTSWITH DSTART: DTSTART:20060428T154500Z
......LINESTARTSWITH DSTART GSUBBED: DTSTART:20060428T154500Z
......LINESTARTSWITH DSTART: DTEND:20060428T163000Z
......LINESTARTSWITH DSTART GSUBBED: DTEND:20060428T163000Z
......TRANSP:OPAQUE
......END:VEVENT

So, oddly, the gsubbing doesn't seem to be doing anything: the gsubbed version is the same as the original.

Ah, but wait! I made a stab in the dark and replaced the two gsub lines with
            line = line.gsub("Z","")
            line = line.gsub("#{replace}:","#{replace};TZID=#{timezone}:")
i.e., inserted the "line = " part in front. This seems to work properly, with one funny exception: any line that already had a "TZID" (e.g., appointments I've made since upgrading and working this issue out) got replaced with a "TID" because of the gsubbing "Z" to a "". So, is there a way of insuring that the match to Z occurs only at the end of the line?

I'm happy to send you the calendar file off-line, if you wish. You can email me directly, my last name followed by wustl and then a dot and then edu (parse that, spammers!)