-
Notifications
You must be signed in to change notification settings - Fork 393
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Show birthdays from contacts database #234
Comments
We neither have the information that it's a birthday entry nor is there a standardized format where to put the year of birth and I haven't found a hint on how to do it in icalendar either. In conclusion, I don't think it's possible to do without putting in lots of assumptions about the users intention and then I don't think we should do it. |
I used aCalender and it looked up the birthdates in the local contacts |
that's an independant feature, pull requests welcome. |
You may use birthday adapter for it: Birthday Adapter (Birthday Calendar Adapter) - https://f-droid.org/app/org.birthdayadapter |
cheers mate :) |
Is there any change on this regard 5.5 years later? Maybe an informal widespread standard among the users of this app? For instance Etar Calendar is shipped with a fork of LineageOS Contacts which offers birthdays support on /e/OS. Would be cool to have them synced. |
I solved the issue by syncing my calendar and contacts with a server that creates an additional read-only calendar "birthdays". |
I would like to add: I used simple-calendar until now (The developer sold his apps to a company known to include commercials so i guess more people will join here) where there is a simple slider and it seems it created a local calendar for that issue. In Etar in the settings i have You could download "Fossify Calendar" (a fork from simple calendar) to check yourself. EDIT: While i don't think a "This person will get XY years" is neccessary, it would be a nice addition. |
Currently: "foo bar (*1900)"
Probably better: "117 foo bar (*1900)"
The text was updated successfully, but these errors were encountered: