Ticket #644 (new defect)

Opened 6 years ago

Last modified 3 years ago

kdepim-sync does not write formatted name (FN) corretly (using irmc-sync at other end)

Reported by: Phlogiston Owned by: cstender
Priority: normal Milestone: Plugin Format: vformat 0.40
Component: Format Plugin: vformat: contact Version: 0.38
Severity: normal Keywords:
Cc:

Description

If I add new contacts on my mobile that have only one name, then the formatted name field is empty after syncing to kontact. I think this should be generated.

I'm using the trunk version of today.

Change History

comment:1 Changed 6 years ago by cstender

  • Version set to 0.34
  • Milestone set to OpenSync 0.40

I wrote the FN generator for OpenSync? 0.2x. This code was deactivated in OpenSync? 0.3x. I don't know why, but I guess this has something to do with the new merger.

Daniel, can you please comment on this?

comment:2 Changed 6 years ago by dgollub

  • Owner changed from dgollub to cstender
  • Component changed from OpenSync to Plugin: vformat

I guess the best solution to workaround this issue is to provide (yet another) converter parameter. So FN <-> N conversion is done optionally for certain combination of device and PIMs.

The FN field in PIMs should be the "primary" or only field to display the entry in a list. It should fallback to N field if FN isn't present.... FN <-> N conversion is really ugly. I don't want see this enabled by default.

We should contact kdepim and evo2 upstream development about this issue.

comment:3 Changed 6 years ago by cstender

  • Status changed from new to assigned

comment:4 Changed 6 years ago by cstender

  • Priority changed from high to normal

comment:5 Changed 6 years ago by tuju

  • Milestone changed from 0.40 to 0.42

comment:6 Changed 5 years ago by tuju

  • Version changed from 0.34 to 0.38

comment:7 Changed 5 years ago by cstender

  • Component changed from Format Plugin: vformat to Format Plugin: vformat: contact

comment:8 Changed 3 years ago by cstender

  • Status changed from assigned to new
Note: See TracTickets for help on using tickets.