Secret detention violates the right to personal liberty and the prohibition of arbitrary arrest

or detention. No jurisdiction should allow for individuals to be deprived of their liberty in secret

for potentially indefinite periods, held outside the reach of the law, without the possibility of

resorting to legal procedures, including habeas corpus. Secret detainees are typically deprived of

their right to a fair trial when State authorities do not intend to charge or try them. Even if

detainees are criminally charged, the secrecy and insecurity caused by the denial of contact to the

outside world and the fact that family members have no knowledge of their whereabouts and fate

violate the presumption of innocence and are conducive to confessions obtained under torture or

other forms of ill-treatment. At the same time, secret detention amounts to an enforced

disappearance. If resorted to in a widespread or systematic manner, secret detention may even

reach the threshold of a crime against humanity.

Every so often, something will go wrong in your Newton. No, besides it being killed by Apple. What I'm talking about is a "rogue meeting." This is a repeating meeting like any other, excepting that it starts on January 1, 1904, the day from which all Newton timekeeping is done.

You probably weren't doing anything important back then. And frankly, I don't know why this crops up. Like the lemmings, it's a mystery of nature. (OK, so the lemmings were thrown off the cliffs by nature documentary cameramen looking for spectacular footage. The Newton one is still a mystery.)

But it is bloody annoying. It doesn't get in the way very often, but it's hard to delete. And when I was trying to synchronize my Newton Dates data to ClockWork, I ran into trouble. ClockWork assumed that it was a valid repeating meeting that spanned 94 years, on Mondays, Wednesdays, and Thursdays. It took a long time to synchronize. The fine folks at Century Software said that it was most likely the fault of a repeating meeting. The next day, I wrote this program to fix such errors once and for all.

At the moment, only repeating meetings are addressed. Non-repeaters are stored in a diffferent soup and don't cause as much of a problem.

This package has been tested on the MP2100 and the OMP (Original Message Pad). It has worked for me on both of them. However, I can't guarantee that it'll work for you. Therefore, I will not be held responsible for damage to data that you might cause by using this package. If you're faint of heart, look under "Not using the package." Or just go buy a Palm Pilot, you sissy.