Pete Maclean

There might be a way to jury-rig a way of filling those blank boxes. But I think it would not be a worthwhile endeavour given that we have to replace the HTML viewer anyway. We have a few candidates for this replacement and we should ensure choosing one that properly handles Progressive JPEGs.

Work continues, slowly but surely. I have completed most of the easy things and am now working on more difficult things which leads to less frequent updates. At the start of this year, I expressed some serious hope that we might have a beta by the end of it. But that seems impossible now. I have over a hundred bug reports to deal with and feel I am doing well if I can deal with one a day. Some reports will be duplicates, some will be already fixed, but plenty will still require attention.

The test is ongoing. Slowly. And it has diverted significantly from its original intention. As well as ensuring compatibility with Eudora we are also making some significant improvements and fixing bugs left over from Eudora. I will update the working of that pop-up window.

It is being worked on. It is coming. Soon? Hard to say.

I wish I could tell you but I cannot. Soon, I hope, but....

Consider it done! (As of the next alpha, that is.)

Oh dear, I have evidently not made things clear enough. Sorry. Eudora and Aurora will each have a private, independent .ini file but they will share everything else (.toc, .fld, .mbx and .pce files). There is no need for you to copy any part of your existing Eudora data.

There are indeed no text files. What you should use is either Alpha.chm (which is a Windows help file) or Alpha_Help.exe (which is an e-book). The contents of the two are the same. The first time you run it, Aurora will make a copy of you Eudora.ini as Aurora.ini which it will then use instead. So there is no configuring that you have to do at the transition. You can move back and forth between Eudora and Aurora although with only one running at any time. If you make changes in your settings in one...