-
Notifications
You must be signed in to change notification settings - Fork 333
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
Event start & end time wrongly converted in the RSS feed #10914
Comments
The problem is that at the time where the time string is generated, we don't have the information of the user that created the event since we're converting a BBCode |
Yeah, I feared something alike ;-) but this is also the explanation for the used strings being in English and not the language of the account (which I think would be a reasonable thing). |
Translating the days/months in any language but English is possible in PHP but it requires the underlying system to have these translations installed in the OS. It would be yet another soft requirement to check on install. |
Not the days & months, well those as well, but also the strings used by Friendica for the headers of "Starts:" and "Finishes:". For the RSS feed it is useless to have the datetime format string translate-able as the translations are not applied. |
The labels |
Should we convert the event entries in the feed to the user's timezone? |
The RSS feed of a Friendica account contains the entries for new events in the calendar. After entering these dates in local time (e.g. CEST) the time in the RSS feed are converted to UTC - but no hint is shown that they are displayed in UTC instead of CEST.
Maybe a side effect of #10818
Steps to Reproduce
Enter the event details in local time. e.g. CEST 19:30.
Have a look in the RSS feed, which will show the event details in UTC
Expected Result:
The time for the beginning and ending of an event should be converted into the local time of the user when generating the RSS feed.
Platform Info
Friendica Version: 2021.12-dev (libranet.de)
The text was updated successfully, but these errors were encountered: