| Summary | vCard import fails with quoted-printable encoded values |
| Queue | Turba |
| Queue Version | 4.2.5 |
| Type | Bug |
| State | Not A Bug |
| Priority | 1. Low |
| Owners | |
| Requester | marth (at) tsvschlieben (dot) de |
| Created | 04/14/2015 (3737 days ago) |
| Due | |
| Updated | 04/24/2015 (3727 days ago) |
| Assigned | 04/24/2015 (3727 days ago) |
| Resolved | 04/24/2015 (3727 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
State ⇒ Not A Bug
question marks. The vcard is not completely rendered as an attachment
though,because htmlspecialchars() returns empty on the invalid
strings. Nothing we could do about though.
New Attachment: vcard-test.vcf
the encoding declaration to UTF-8 to simulate a wrong encoded vcard)
Result:Silently discard any chars behind the first wrong encoded char
Expected: Maybe some kind of warning so the user is aware that
something went wrong at the import and there is an encoding issue with
the vcard file?
State ⇒ Feedback
However I'm not sure that quietly discard data is the best way to
handle this...
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ vCard import fails with quoted-printable encoded values
Queue ⇒ Turba
Milestone ⇒
Patch ⇒ No
State ⇒ Unconfirmed
characters everything after this char is stripped.
Example:
[...]
NOTE;CHARSET=UTF-8;ENCODING=QUOTED-PRINTABLE:foo=E4bar
[...]
Expected result:
fooäbar
Result:
foo