peer(phone or vcards) has contacts with pictures
sync the peer then try to read photo
peer is synced and photo is the same as in phone (vcards)
syncevolution creates photo file after peer sync but file file name has encoding error
photo field in contact :
file name :
proper file name should be pas_id_5256B5B000000006_photo-file0.jpeg
Just to be sure I understand, the file name as it stands today is usable, isn't it?
It's just not as nice as it could be, because of the extra escaping of the running number?
Yes It is usable but the double quotation may lead to implementation errors.
This is anyway minor issue.
At least we should provide some information on how to decode it.
(In reply to comment #2)
> Yes It is usable but the double quotation may lead to implementation errors.
> This is anyway minor issue.
> At least we should provide some information on how to decode it.
The PHOTO value is an URL. That already defines how to decode it, there's nothing special about it.
In particular, you cannot just strip a the file:// prefix and use the remainder as file name. One has to do URL decoding. Whether encoding is really used is a different matter. The code has to assume that it is, and from that perspective it is actually good to have it tested.
Obviously it is less nice for testers and developers.
Do we agree to treat this as a low priority feature request for EDS ("avoid quoting of number when creating photos") that can be deferred?
Ok, I was not aware that EDS was responsible of this.
We can defer it and open an EDS minor request.
Let's track elsewhere. Closing it here.