Reply
Thread Tools
Posts: 61 | Thanked: 36 times | Joined on Feb 2006 @ Harpenden
#41
 
Posts: 33 | Thanked: 10 times | Joined on Jan 2010
#42
Are you sure thats the right spec sheet?

I found a different spec sheet on vcal here which contains this ...

Audio Reminder
This property is identified by the property name AALARM. The property defines an audio reminder for the vCalendar entity. An audio reminder is an alarm that is sounded for the event.
The value for the audio reminder consists of the Run Time, or the date and time that the reminder is to be executed; Snooze Time, or the duration of time after the Run Time that the reminder is to be dormant prior to being repeated; Repeat Count, or the number of times that the reminder is to be repeated; and the Audio Content, or the digital sound to be played when the reminder is executed.
The following are some examples of this property:
AALARM;TYPE=WAVE;VALUE=URL:19960415T235959; ; ; file:///mmedia/taps.wav
AALARM;TYPE=WAVE;VALUE=CONTENT-ID:19960903T060000;PT15M;4;<jsmith.part2.=
960901T083000.xyzMail@host1.com>
So the PT3M is the snooze time of the alarm and for whatever reason the parser doesn't like it. iCal doesn't have snooze times really I guess because you set them from the alarm reminder when it pops up. Then I assume it just alters the date of the reminder? (lot of assumptions and guessing going on in that sentence!)

Last edited by 3quid; 2010-01-17 at 14:18.
 
Posts: 26 | Thanked: 25 times | Joined on Jan 2010 @ USA, Maine
#43
I have been trying to sort through the standards stuff and found http://www.imc.org/pdi/ There are several documents in here and it would appear they are in charge of the standards and there appears to be separate efforts for Contacts and Calendars.
 
Posts: 61 | Thanked: 36 times | Joined on Feb 2006 @ Harpenden
#44
I've found some python code for parsing ICS files. It successfully parses one generated by BusyCal/iCal, put chokes on the one from the N900. I'm going to dig some more into it to find out what exactly it is objecting to. It looks like PR1.1 is producing invalid VEVENT files....
 
Posts: 33 | Thanked: 10 times | Joined on Jan 2010
#45
So... I guess we have to work out exactly what "Failed to parse vCal (1) near index 97" means? Well.. I know what it means, it failed! but where that problem is coming from.. iCal or N900? The formatting of the AALARM property? on different lines like that? Any ideas?
I created an .ics using the sync output that failed... there are few things.

1. version needs to be 2.0 to import as a .ics but I think that's just for direct import of .ics because the sync from ical>n900 showed version 1.0 as well.

2. the line "SUMMARY;ENCODING=QUOTED-PRINTABLE;CHARSET=UTF-8:=
ManualEntry" shows up in iCal as an event called "=" so it doesn't seem to like new lines

3. if you don't place the AALARM info (including the snooze value) onto one line like this "AALARM:20100129T130500;PT3M;" it won't import at all

Not sure if any of these have any bearing with the auto-syncing but I am sure the formatting must have very similar requirements?
 
Posts: 26 | Thanked: 25 times | Joined on Jan 2010 @ USA, Maine
#46
I know you are both focussing on the Calendar syncing but i have been poking around the contact side to test it out more thoroughly. I have about 3500 contacts from all over the world and there are issues with different languages, formats, and more. Working with 3Quid I was able to do sync and on the surface it mostly worked but there were some details that did not. I am new to the Isync plug in world but am currently running a test, details below. It has been running for over an hour and still has a long way to go and there are many errors that have been flagged. Have either of you run this scenario test? At this point in the testing, all my contacts on the N900 have been deleted and it is still running.

Screenshot attached.
Attached Images
 
 
Posts: 33 | Thanked: 10 times | Joined on Jan 2010
#47
The plugin will not currently pass the tests that pluginmaker sets and it's likely that it never will when made by mere mortals like me! passing all those tests is a massive task. forget them for now if I were you.

Evidence to ignore tests for now ... and I quote "Ignore the test-suite; I could not get a single test running"
 
Posts: 26 | Thanked: 25 times | Joined on Jan 2010 @ USA, Maine
#48
3Quid - If you are a mere mortal I hate think where that would put me . The last time I did serious programming it was Z80 assembly and that was when the Z80 was the hottest processor out there!

I really appreciate all the effort on this and I am thrilled that I can do at least a basic sync on my contacts
 
Posts: 61 | Thanked: 36 times | Joined on Feb 2006 @ Harpenden
#49
If I change the line wrapping in the broken example, I can get it to parse. I don't know if the incorrect wrap is due to :-
  • This forum software
  • The iCal log file
  • The N900

The 'fixed' example is this :-
Code:
BEGIN:VCALENDAR
VERSION:1.0
TZ:+00
DAYLIGHT:TRUE;+01;20100328T020000;20101024T010000;GMT;BST
BEGIN:VEVENT
SUMMARY;ENCODING=QUOTED-PRINTABLE;CHARSET=UTF-8:=Testing=20alarms=20w/log
UID:513
DTSTART:20100129T132000Z
DTEND:20100129T142000Z
ATTACH:
SEQUENCE:0
LAST-MODIFIED:20100117T130040Z
DCREATED:20100117T130040Z
AALARM:20100129T130500;PT3M;
END:VEVENT
END:VCALENDAR
Where every line should start

WORDINCAPS:
 
Posts: 61 | Thanked: 36 times | Joined on Feb 2006 @ Harpenden
#50
It looks like this forum software is responsible for some wrapping (the line SUMMARY; is wrapped when it shouldn't), but the layout of the AALARM entry is significantly different compared to the original
Code:
AALARM:20100129T130500
;PT3M
;
 

The Following User Says Thank You to scudderfish For This Useful Post:
Reply


 
Forum Jump


All times are GMT. The time now is 15:57.