|
2010-01-18
, 12:34
|
Posts: 33 |
Thanked: 10 times |
Joined on Jan 2010
|
#62
|
|
2010-01-18
, 12:58
|
Posts: 61 |
Thanked: 36 times |
Joined on Feb 2006
@ Harpenden
|
#63
|
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?
|
2010-01-18
, 13:01
|
Posts: 33 |
Thanked: 10 times |
Joined on Jan 2010
|
#64
|
|
2010-01-18
, 19:38
|
Posts: 27 |
Thanked: 23 times |
Joined on Sep 2009
@ Helsinki
|
#65
|
|
2010-01-18
, 20:18
|
Posts: 33 |
Thanked: 10 times |
Joined on Jan 2010
|
#66
|
|
2010-01-18
, 20:24
|
Posts: 61 |
Thanked: 36 times |
Joined on Feb 2006
@ Harpenden
|
#67
|
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?
|
2010-01-18
, 21:05
|
Posts: 61 |
Thanked: 36 times |
Joined on Feb 2006
@ Harpenden
|
#68
|
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
|
2010-01-18
, 21:09
|
Posts: 61 |
Thanked: 36 times |
Joined on Feb 2006
@ Harpenden
|
#69
|
I haven't done BNF in a while myself either, but I think you have misread the grammar.
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).Code:strnosemi = *(*nonsemi ("\;" / "\" CRLF)) *nonsemi
It looks like someone needs to open a bug with Maemo on this.
|
2010-01-18
, 21:33
|
Posts: 27 |
Thanked: 23 times |
Joined on Sep 2009
@ Helsinki
|
#70
|
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: