Reply
Thread Tools
Mandibela's Avatar
Posts: 270 | Thanked: 195 times | Joined on Aug 2009 @ Finland
#61
Lotsa thanks to you everyone!

I just synced my MacBook (10.4.11) with the N900 somewhat succesfully. iSync version is 2.4. It's very nice that the plugin worked with 10.4.

This is from my mac:
Code:
10:40:10.841 [iSync:1412] ERROR (.sync.Parser.VCal): Failed to parse vCal (1) near index 30: BEGIN:VEVENT
                                                   : SUMMARY;ENCODING=QUOTED-PRINTABLE;CHARSET=UTF-8:=
                                                   : Arvaa=20mik=C3=A4=20p=C3=A4iv=C3=A4?
                                                   : UID:70
                                                   : DTSTART:19830721T000000
                                                   : DTEND:19830721T000000
                                                   : ATTACH:
                                                   : PRIORITY:0
                                                   : SEQUENCE:0
                                                   : CLASS:PUBLIC
                                                   : X-EPOCAGENDAENTRYTYPE:APPOINTMENT
                                                   : X-METHOD:NONE
                                                   : X-SYMBIAN-LUID:76
                                                   : LAST-MODIFIED:20091204T151140Z
                                                   : DCREATED:20091204T151140Z
                                                   : RRULE:YM1 7 21000721T000000
                                                   : AALARM:20100720T000000
                                                   : ;PT7M
                                                   : ;
                                                   : END:VEVENT
                                                   : END:VCALENDAR
                                                   :
I got plenty more... But you guys already know about those, so I'm just waiting for now.
 
Posts: 33 | Thanked: 10 times | Joined on Jan 2010
#62
Could there be a way of enforcing it to escape the CRLF using the Advanced Options > vCard/vCal common settings >

a. Escape semicolon in non-compound property values
c. Characters to escape in property values

... options inside the iSync Plugin-Maker?
 
Posts: 61 | Thanked: 36 times | Joined on Feb 2006 @ Harpenden
#63
Originally Posted by 3quid View Post
Could there be a way of enforcing it to escape the CRLF using the Advanced Options > vCard/vCal common settings >

a. Escape semicolon in non-compound property values
c. Characters to escape in property values

... options inside the iSync Plugin-Maker?
Give it a go I'm away from my Mac right now* (work insists I use a Dell box) so I can't do anything until this evening.


* Not quite true, I've got a hackintosh netbook with me, but the the plugin maker doesn't fit on the 1024x600 res screen.
 
Posts: 33 | Thanked: 10 times | Joined on Jan 2010
#64
Will do I can't give it a go till later either. I have deadlines due today

I am determined to get this problem resolved though. Annoying not to be able to set event alarms on the move. Especially as the event is then completely ignored by iCal.
 
Posts: 27 | Thanked: 23 times | Joined on Sep 2009 @ Helsinki
#65
Can confirm that my problem has the same problem, i.e. events created with an alarm on the N900 dont get synced to the Mac :-(

Trying to fiddle with the options now, let's hope one of them solves this.
 
Posts: 33 | Thanked: 10 times | Joined on Jan 2010
#66
OK thanks joergen, glad its not just us!

I have tried using the settings relating to escapes, CRLF and whitespace but no joy. In fact I don't see any of the settings inside the Advanced Options > vCard/vCal common settings taking any effect at all. I tried, for example, to put AALARM in the 'properties to ignore' list but it still continues to try and parse AALARM. I wanted to see if the event would work if AALARM was stripe out on import.

Should that work? or is it only for custom "X-xxx-xxxxx" properties?
 
Posts: 61 | Thanked: 36 times | Joined on Feb 2006 @ Harpenden
#67
Originally Posted by 3quid View Post
OK thanks joergen, glad its not just us!

I have tried using the settings relating to escapes, CRLF and whitespace but no joy. In fact I don't see any of the settings inside the Advanced Options > vCard/vCal common settings taking any effect at all. I tried, for example, to put AALARM in the 'properties to ignore' list but it still continues to try and parse AALARM. I wanted to see if the event would work if AALARM was stripe out on import.

Should that work? or is it only for custom "X-xxx-xxxxx" properties?
I think it is objecting to the general format of the VCALENDAR so it doesn't get as far as recognising the AALARM to strip out. That would explain why we see no event at all instead of an event with the alarm missing.
 
Posts: 61 | Thanked: 36 times | Joined on Feb 2006 @ Harpenden
#68
I think we're really not going to get this to work with the software we have. Digging through the detailed iSync log :-
Code:
TIME: 20:51:26.893
THREAD: 0x116af5bd0
TYPE: .sync.Parser.VCal
LEVEL: ERROR
LINE: 548
FUNCTION: -[VCalParser parseData:]
DEPTH: 11
LENGTH: 315

Failed to parse vCal (1) near index 97: BEGIN:VEVENT
SUMMARY;ENCODING=QUOTED-PRINTABLE;CHARSET=UTF-8:=
Fffffff
UID:490
DTSTART:20100118T211500Z
DTEND:20100118T221500Z
ATTACH:
SEQUENCE:0
LAST-MODIFIED:20100118T205403Z
DCREATED:20100118T205403Z
AALARM:20100118T210000
;PT3M
;
END:VEVENT
END:VCALENDAR
That is a piece of Objective-C code buried who knows where in the code stack that is spitting the dummy at the extra CRLF characters. We could raise a bug with Apple that they are not correctly parsing VCALENDAR entries (good luck with that), or we petition Nokia to suppress the extra CRLF in an update. If I knew where the N900 was generating it and I had the source I'd go and fix it. That is far more likely to happen than changing Apple code. Unfortunately, this isn't really a bug in the N900 as far as I can see so I doubt it would get much traction.
 
Posts: 61 | Thanked: 36 times | Joined on Feb 2006 @ Harpenden
#69
Originally Posted by fuzzbang View Post
I haven't done BNF in a while myself either, but I think you have misread the grammar.

Code:
strnosemi	= *(*nonsemi ("\;" / "\" CRLF)) *nonsemi
The BNF shows that the only way to embed a CRLF before the terminal semicolon is to escape it with a backslash first "\"... which is not happening with the N900 code (based on the dumps shown in this thread).

It looks like someone needs to open a bug with Maemo on this.
I read that as
strnosemi is made up of a sequence of zero or more instances of any of the following :- nonsemicolons \; / \ CRLF followed by zero or more instances of nonsemicolons.

Or put it another way strnosemi can contain any character, including CRLF provided that all semicolons are preceded by \
 
Posts: 27 | Thanked: 23 times | Joined on Sep 2009 @ Helsinki
#70
Haven't been lucky with the options either :-(

I am pretty sure that this is a bug in the N900; i'm pretty sure a newline is supposed to be escaped in a vcal property, unless one is specifying quoted-printable as the encoding. (So the newine in the summary is probably ok in a formal sense, but it seems to be bogus to start the string with a newline anyways).
 
Reply


 
Forum Jump


All times are GMT. The time now is 18:35.