Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
J
jami-client-gnome
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 155
    • Issues 155
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Requirements
    • Requirements
    • List
  • Security & Compliance
    • Security & Compliance
    • Dependency List
    • License Compliance
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • savoirfairelinux
  • jami-client-gnome
  • Issues
  • #404

Closed
Open
Opened Jan 14, 2016 by RingBot@RingBotOwner

gnome/lrc: bad parsing of vcard name with backslash

Issue generated from Tuleap's migration script. Originally submitted by: Stepan Salenikovich (ssalenik)

Reported on the Ring mailing list:

I have a contact called "Lastname, Firstname" and it shows up as
"Lastname\, Firstname". Because the vcf was from a dumb phone, so the
"," is part of the name.

Right now in Ring gnome we get the vcard using the EDS apis, but its parsed in lrc... it may be more reliable to just parse the contact directly using the EDS apis... or else look into fixing the lrc parsing, or maybe use a library for parsing, if available...

example buggy vcard attached
buggy-ring.vcf

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: savoirfairelinux/ring-client-gnome#404