--- Comment #12 from Chen Congwu <congwu.chen(a)intel.com> 2009-11-24 19:19:59 PST
(In reply to comment #9)
Mind the extra white space at line ends. I don't care about those
source code, but would like to keep the strings clean. I also suggest a
Regarding the new "evolutionsource" parsing: are spaces
around a comma allowed?
What if a user has chosen a sync source name which includes a comma? We need
some kind of escaping for this.
Right, I am adding "boost::trim" to strip the spaces and using "\" as
escape character to handle comma in source name problem.
Note I am not using SafeConfigNode because it is designed to be used for
internal properties which will is read and written only by SyncEvolution.
The "evolutionsource" is a public property which maybe set by user explicitly.
Therefore I am just adding escape capable decoding and update the documentation
Pushing to phone branch now.. Please have a look.
Configure bugmail: http://bugzilla.moblin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.