Version: (using KDE KDE 3.3.2) Installed from: SuSE RPMs Just a wish: I've several contacts from which I know the day and month of birth but not the year. Currently I cannot enter them in kaddressbook so I do not get any notifications for their birthdays getting close ... :( (This wish is somewhat related to bug #43065)
On Mon, Dec 20, 2004 at 02:52:07PM -0000, Andreas Schallenberg wrote: Hi Andreas, > Just a wish: I've several contacts from which I know > the day and month of birth but not the year. > Currently I cannot enter them in kaddressbook so > I do not get any notifications for their birthdays > getting close ... :( We need the year to calculate the age at many different places, so if you don't know the year, put in a dummy value. Ciao, Tobias
For most people I know I don't know the year they're born and I guess that's pretty common. I think the vCard backend doesn't support year-less dates, but couldn't some unrealistic value used as "year is unknown"? I currently use 9999 as the year if I don't know it. Would that work (ie. is it ok to REOPEN this bug)? It would still be a hack but at least one which is officially supported and could be ignored by age calculations etc.
On Thu, Apr 21, 2005 at 09:04:49PM -0000, Malte S.Stretz wrote: Hi, > I think the vCard backend doesn't support year-less dates, Right... > Would that work (ie. is it ok to REOPEN this bug)? > It would still be a hack but at least one which is > officially supported and could be ignored by age calculations etc. _We_ can ignore it for calculations, but any other app which imports our vCards will display very strange results. For this reason I'll never implement such an ugly hack! Ciao, Tobias
Yeah, but as a user I need to use *some* hack anyway. If there was one which was supported by the app, the value could be ignored by itself and when you export such a vCard, it could warn that other apps might have problems with that value. Currently there everybody has to do his own hack, so you will get weird values nevertheless. For most people you just will never get to know their birthyears (and asking "hey, could you also tell me your birthyear, because, umm, you know my addressbook needs it" is always a bit weird), so why not try to find a solution which hurts the least. Just shutting the eyes and telling the users to find their own solution just doesn't work IMO.
Not exporting the birthday when the year it has a certain value (9999) certainly seems to be a hack. But thats better than not supporting unknown years at all. However, there should be a way to export data for other KDE addressbooks including these "unknown" years.
*** Bug 110049 has been marked as a duplicate of this bug. ***
It is somehow dissatisfying that this cannot be implemented due to the vcard standard not supporting this. Maybe we should try to ask at the IMC to include a way out in the next vcard specification? I'm reopening this wish since I do not seem to be the only person requesting this (votes: at least three others strongly do) and it cannot be viewed as solved.
Contact uses vcards internally? I didn't know that. And if vcards don't support year-less dates, then maybe Contact could store year-less dates in another format, maybe in a second field called "year-less birthday which cannot be exported in the vcard format" (well, I'm joking here). I tried to enter the year "0000", but Contact translated that into "2000". I'm now using "1900" for my year-less birthday dates. I'm using Contact entirely within KDE. I do not need vcard compatibility...
*** This bug has been confirmed by popular vote. ***
On Wed, Aug 03, 2005 at 10:38:26AM -0000, owner@bugs.kde.org wrote: Hi, could we pleae leave this bug closed, I'm really tired of explaining again and again why we won't implement it... Ciao, Tobias
Today I subscribed to the IMC mailing list for vcards and sent a description of the problem to that list. Let's see what the feedback is. Tobias: I do not expect that you switch from vcard to something else. But as soon as these unknown years can be coded in a vcard (in a future version maybe) then there is something to do here. That is the reason I don't see that this should be left with "WONTFIX". At least, thats my opinion.
To #11: No replies came on that list :(
The development of the old KAddressBook will be discontinued for KDE 4.4. Since the new application has the same name, but a completly new code base we close all bug reports against the old version and ask the submitters to resend there reports against the new product.
I hope this can be added to the new Akonadi-powered KAddressBook then :)
The old KAddressBook will be disconinued in KDE 4.4. Plesae report you bugs against the new version of KAddressBook.