Build 29 can be downloaded from here:
Windows: Rainlendar-2.0.1.b29.zip
Linux: Rainlendar-2.0.1.b29.tar.bz2

This is beta version! It has not been tested.

The list of changes:

[2.0.1 Build 29] - 03 Dec 2006
o EventListShowComingEvents didn't work from the advanced settings. Fixed.
o Removed Cleartype related code as it didn't work very well.
o Importing ics files which doesn't contain UIDs works now.
o Improved compatibility of the exported ics files.
o Remove button caused crash if no calendars were selected. Fixed.
o Added EventListAgeFromStartOfWeek to advanced options which defines how the weeks are shown in the event list header.

Link to Linux version wrong. Right link <br><br>Post edited by: msk, at: 2006/12/03 15:00

&quot;Added EventListAgeFromStartOfWeek to advanced options which defines how the weeks are shown in the event list header.&quot;

Fantastic Rainy

I was using 2.0b27 since 2.0.1 has the Cleartype bug. I was able to use Chinese character (unicode or mutlibyte character?) in the EventListHeaderFormat. Now in 2.0.1 b29 some weird characters appeared instead of the format I typed in, but using only English and parameters works fine.
Also, when i use %HS%HE in that field, something like 37HE appears. Actually I was trying to format it to %#d/%#m (%HS %HE) (%D days), but if the date is in current week, %HE will be empty and there will be a space after %HS (e.g. (Sunday )).
Is there anyway to overcome this?<br><br>Post edited by: Jackal, at: 2006/12/05 20:05

I tried using Chinese characters in the event list header and it seems that the wcsftime() fails for some reason. I wasn't able to get it to work with the older builds either. wcsftime() is a system function so it's not possible for me to fix it.

The &quot;37&quot; is caused by the environment variable expansion bug. I can fix that in the next build.

At the moment it's not possible to get rid of the extra space. I have a todo entry to make it possible to customize the first week separately from the rest of the days which should fix the problem.

I just find out that Chinese characters works fine when rainlendar is set to (Traditional) Chinese.