The Discourse local time displays wonderful dates in the web UI. However in emails it can be very very confusing.
For example: May 18, 2018 11:03 PM will display as May 19, 2018 9:03 AM in an emails which leaves recipients very confused.
I propose a multi step approach to improving this.
Immediate change… just display time zone with the time in emails so we would have May 19, 2018 9:03 AM Australia/Sydney
Longer term change, start storing local time zone in the user profile table (detect via JS and hand to server with a header). Then in emails we can send the times in the “last know local timezone”
Longer Longer term, allow users to control preferred timezone in user profile (automatic vs manually set to something)
Working on it, but I still don’t understand why you say that it will display as May 19, 2018 9:03 AM in an email. This is not what will happen, it will display:
May 19, 2018 09:03 AM (Australia: Sidney)
The issue is that it will display all timezones set when configuring the date, and you might end up with something very verbose. So yes we will need step2, to have something cool here, so you say send this email to this user living in Australia/Sidney timezone
Que la zona horaria del correo electrónico se base en la zona horaria original establecida en la publicación
Si establezco mi valor de zona horaria como [date=2019-12-15 time=23:59:00 timezone="EST"]
Debería enviarse por correo electrónico tal cual.
Permitir un mejor formato de la zona horaria dentro de esta configuración del foro:
Actualmente es un poco limitado:
(solo en caso de que queramos mostrar el nombre completo de la zona horaria o algún otro formato especial)
Actualmente es un poco limitado:
Alternativamente, permitir que el administrador elija la zona horaria con la que desea enviar los correos electrónicos en la configuración, quizás un interruptor como:
discourse local dates email format timezone