• Bug#1080311: railway-gtk: should handle timezones in a better way

    From Matthias Geiger@21:1/5 to debacle@debian.org on Sat Mar 8 17:10:01 2025
    Control: tags -1 wontfix

    On Sun, 01 Sep 2024 22:51:30 +0000 Martin <debacle@debian.org> wrote:
    Package: railway-gtk
    Version: 2.4.0-4

    Dear maintainer,

    if users system has a different timezone then the train operator (common
    use case when planning a trip in a different country), it's not obvious, which time is used where.

    E.g. if users system runs in UTC, searching for a connection in Germany (CEST/UTC+2 atm.) at 16 hrs, this is interpreted as 16:00 UTC and it
    shows a train at 18:00 CEST.

    This is technically correct, but confusing. Web sites of train operators interprete search time always as local time of the train, no matter
    which is the time zone of the users system, which is better UX IMHO.

    Alternatively, times zones could be displayed with the times, but that
    would clutter the UI. Not so nice on mobile phone.

    The obvious workaround would be to run railway-gtk with the desired
    timezone, but it looks like railway-gtk ignores the TZ variable!

    Cheers


    Hi Martin,

    after reaching out to upstream they stated that tracking timezones is
    not planned nor being worked on as the providers like DB do not support
    this and timezones in general are hard to keep track of wrt
    departure/arrival times.
    The times displayed in railway-gtk are always the "local" operator
    times, i.e. CET for DB, oebb, etc.

    best,

    werdahias

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)