summaryrefslogtreecommitdiff
path: root/lib
AgeCommit message (Collapse)AuthorLines
2025-07-18Add localization support.Birte Kristina Friesel-5/+134
Right now, only two languages are supported, and only a fraction of strings are already translated. There's also quite a bunch of todos left where strings are assembled in the Model, which has no access to localization functions. But that's something for iterative refinement over the next months, and (especially when it comes to adding languages and translation strings to templates) merge requests. Squashed commit of the following: commit 67d756f3bd167003907c8357126630dd7c1a3cfa Author: Birte Kristina Friesel <derf@finalrewind.org> Date: Fri Jul 18 19:53:56 2025 +0200 more translations commit 8cb0d65e70e42180419a5dd7634d332e65488dd4 Author: Birte Kristina Friesel <derf@finalrewind.org> Date: Fri Jul 18 18:54:12 2025 +0200 sme more translations commit ff12f010380914f9461966f2ef8ac6b303712ee4 Author: Birte Kristina Friesel <derf@finalrewind.org> Date: Fri Jul 18 18:53:31 2025 +0200 Add language selection to account page commit 9bf27132cbf2f87bca5af564914d96a57045ecc1 Author: Birte Kristina Friesel <derf@finalrewind.org> Date: Fri Jul 18 16:42:28 2025 +0200 Translate footer components commit 90c2c6505e933848268ed9c5bbe21e0b459cd72a Author: Birte Kristina Friesel <derf@finalrewind.org> Date: Fri Jul 18 16:16:50 2025 +0200 Use Accept-Language header if user has no preferred languages commit 814cb4a4dd4017606829ecc6b6c70822bf52a30e Author: Birte Kristina Friesel <derf@finalrewind.org> Date: Fri Jul 18 16:11:19 2025 +0200 Add list of preferred languages to user settings commit 731b789855914cb94ec091604e32aa68a678404a Author: Birte Kristina Friesel <derf@finalrewind.org> Date: Fri Jul 18 15:33:42 2025 +0200 Localization with Locale::Maketext WiP, no suitable foundation for merge requests yet. Still todo: * override Accept-Language header via account settings * Adjust all the templates and frontend javascript Related to #223
2025-07-11Fix train position calculation on first leg of polyline2.15.14Birte Kristina Friesel-1/+1
2025-07-11estimate_trip_position: Remove dead codeBirte Kristina Friesel-11/+0
2025-07-11InTransit: re-add fallback path to location estimation.Birte Kristina Friesel-11/+20
It makes sense when annotating the position with the user rather than the vehicle.
2025-07-10in transit: show estimated train position and full route (greyed out)2.15.13Birte Kristina Friesel-9/+203
2025-07-06database: Relax platform and line length constraints2.15.12Birte Kristina Friesel-0/+151
Closes #267
2025-07-06Revert "/journey/edit: datetime inputs"2.15.11Birte Kristina Friesel-4/+4
This reverts commit 02a6b9072d16c521142f04f5dd4a316aa269a5de. DateTime inputs on the web are absolutely horribly broken as soon es they use sub-minute accuracy (i.e., seconds). Switch journey edits back to %d.%m.%Y %H:%M(:%S) to restore proper editing support. /journey/add and /checkin/add retain their datetime pickers and will not support sub-minute accuracy. Closes #272
2025-07-06geolocation: dbris: show each unique stop only once2.15.10Birte Kristina Friesel-1/+1
2025-07-05Traveling: perltidyBirte Kristina Friesel-10/+12
2025-07-05edit_journey: support timestamps with sub-minute resolutionBirte Kristina Friesel-4/+15
2025-07-05Merge branch 'date-inputs' of github.com:deingithub/travelynxBirte Kristina Friesel-13/+35
2025-07-04Revert "work: dbris: be slightly less pessimistic"2.15.6Birte Kristina Friesel-1/+1
This reverts commit 5693277807924744c2ace92015f01c0f9f25e8a8.
2025-07-03Journey-based checkins: store platforms with route; set arrival platform from it2.15.5Birte Kristina Friesel-0/+31
Closes #269
2025-06-29/checkin/add: allow eliding date on intermediate stopsCassidy Dingenskirchen-4/+28
2025-06-29/checkin/add: datetime inputs, change intermediate stop input format to ISO8601Cassidy Dingenskirchen-1/+1
2025-06-29/history/map: date inputsCassidy Dingenskirchen-5/+3
2025-06-29/journey/edit: datetime inputsCassidy Dingenskirchen-2/+2
2025-06-29/journey/add: datetime inputsCassidy Dingenskirchen-1/+1
2025-06-29work: dbris: be slightly less pessimistic2.15.3Birte Kristina Friesel-1/+1
2025-06-29Journeys->get: type: trim trailing white space (hello, hafas)Birte Kristina Friesel-1/+1
2025-06-29Journeys->get: pre-compute delay dataBirte Kristina Friesel-0/+6
2025-06-29work: limit dbris journey requests to 0.5 HzBirte Kristina Friesel-4/+6
If $backend is not set, we may have non-dbris checkins in between -- in that case, we don't need to wait as long
2025-06-27work: support distinct worker invocations per backendBirte Kristina Friesel-160/+171
2025-06-25Journeys->add: allow consecutive route stops at the same timestampnetworkException-2/+2
This patch relaxes the route timestamp sanity checking introduced in 9e6728a3e14fbe48b7e7aa1d7c0ae2d4e79f0ece by allowing the same timestamp (usually minute accuracy) to occur multiple times for consecutive stops. This is common for trams, for example.
2025-06-24add_intransit_form: add simple sanity check for route timestampsBirte Kristina Friesel-2/+15
2025-06-24Journeys->add: a little bit of sanity checking for route timestampsBirte Kristina Friesel-2/+10
2025-06-23update_arrival_motis: store arrival platform, if availablenetworkException-1/+2
See b4879a8a48ccecf1071d1ed76a02fecfb4eba3b6
2025-06-23Journey: show dep/arr stop in table; include platforms if availableBirte Kristina Friesel-1/+3
Also: show checkin timestamp
2025-06-23update_arrival_{dbris,efa,hafas}: store arrival platform, if availableBirte Kristina Friesel-3/+5
2025-06-23InTransit->add: Use existing JSON instanceBirte Kristina Friesel-7/+7
2025-06-23Manual journey entry: support sched arr/dep timestamps of intermediate stopsBirte Kristina Friesel-9/+25
2025-06-22add_intransit_form: only use station_info if is definedBirte Kristina Friesel-2/+2
2025-06-22add_intransit: allow users to specify timestamps for intermediate stopsBirte Kristina Friesel-6/+15
2025-06-22add_intransit_form: ensure arrival > departureBirte Kristina Friesel-0/+3
2025-06-21Add bare-bones support for manual checkins (still bound to a specific backend)Birte Kristina Friesel-4/+276
Extension opportunities (maybe, eventually) * provide datetimes of intermediate stops * provide an API for real-time data updates * look up stops that travelynx does not yet know about rather than rejecting them outright
2025-06-21add journey: do not hardcode backend2.14.18Birte Kristina Friesel-2/+4
2025-06-20station board: map upstream HTTP 500 to HTTP 502Birte Kristina Friesel-1/+1
2025-06-20CSV history export: Use EVA IDs rather than Ril100; add carriage and operatorBirte Kristina Friesel-15/+23
See #255
2025-06-20MOTIS: Normalize timestamps to Europe/BerlinnetworkException-0/+5
2025-06-19Traveling#station: GET parameters always override user configurationBirte Kristina Friesel-8/+29
Closes #253
2025-06-19EFA backends are no longer experimental2.14.13Birte Kristina Friesel-2/+2
2025-06-19stations_str: ris has been renamed to dbris; add is_motisBirte Kristina Friesel-0/+24
This fixes missing dbris and motis indicators in dumpstops
2025-06-19dumpstops: add is_dbris, is_efa, is_motis flagsBirte Kristina Friesel-3/+3
2025-06-19EFA: Show disambiguation pageBirte Kristina Friesel-0/+13
Closes #249
2025-06-18Stations->add_or_update: show user-friendly error if latlon are missing2.14.12Birte Kristina Friesel-0/+3
This can happen with EFA SEV stops
2025-06-18EFA: trip IDs should include a time, not just a dateBirte Kristina Friesel-3/+7
Closes #243
2025-06-18DBRIS: Support short IDs (A=1@L=eva)2.14.11Birte Kristina Friesel-2/+2
2025-06-17DBF links: support efa and motis backendsBirte Kristina Friesel-1/+3
2025-06-16MOTIS: Store trip operatornetworkException-0/+3
2025-06-16database: relaxe train_type length constraint for EFA and MOTIS checkinsBirte Kristina Friesel-0/+147
Closes #239
generated by cgit v1.2.3 (git 2.39.1) at 2025-10-04 11:23:48 +0000