Hello,
google supports web-published ical import and display with their beta:
http://www.google.com/
A problem exists with how they choose to import event information by ignoring 8-bit data without encoding. (Something allowed by the ical RFC.)
We have export of our ical working with most common ical calendar tools (MS Outlook, Sunbird, Apple's ICal, and more.)
If we choose to limit event information to 7-bit content, then we lose the ability to encode unicode charsets as 8-bit and allow for charset/alphabets unless included in the lower 128 printable ASCII.
So, what do you think? Should fourm events be exportable to google calendar at the cost of 8-bit and multi-byte charsets for event descriptions?
Our present export method forces the ical event to have a link directly to the forum event, so any 8-bit or multibyte characters initially included in the event description, will still be viewable on the web, in the forums.
google supports web-published ical import and display with their beta:
http://www.google.com/
A problem exists with how they choose to import event information by ignoring 8-bit data without encoding. (Something allowed by the ical RFC.)
We have export of our ical working with most common ical calendar tools (MS Outlook, Sunbird, Apple's ICal, and more.)
If we choose to limit event information to 7-bit content, then we lose the ability to encode unicode charsets as 8-bit and allow for charset/alphabets unless included in the lower 128 printable ASCII.
So, what do you think? Should fourm events be exportable to google calendar at the cost of 8-bit and multi-byte charsets for event descriptions?
Our present export method forces the ical event to have a link directly to the forum event, so any 8-bit or multibyte characters initially included in the event description, will still be viewable on the web, in the forums.