Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. General and Desktop
  4. Is time zone ID for Buenos Aires wrong?
Forum Update on Monday, May 27th 2025

Is time zone ID for Buenos Aires wrong?

Scheduled Pinned Locked Moved Unsolved General and Desktop
timezone
2 Posts 2 Posters 786 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • K Offline
    K Offline
    kamorrissey
    wrote on 25 May 2018, 16:07 last edited by kamorrissey
    #1

    I ran into an incompatibility issue that required me to back out a recent fix in a product. We have an Android-based embedded device managed through a Windows Qt 5.9.1 application. The embedded device uses none of Qt.

    The device uses "America/Argentina/Buenos_Aires" as the ID for the Buenos Aires time zone. This is consistent with what I see in the IANA TZ data file (at https://www.iana.org/time-zones).

    Qt, on the other hand, uses "America/Buenos_Aires" as the ID, which is nonconforming. What's puzzling is that QTimeZone documentation says it uses the IANA TZ database, so I don't understand why there's a difference. I also don't yet know if any other TZs have similar problems.

    Does this constitute a bug in Qt?

    1 Reply Last reply
    0
    • M Offline
      M Offline
      mrjj
      Lifetime Qt Champion
      wrote on 25 May 2018, 16:31 last edited by
      #2

      Hi
      It could be.
      I would search https://bugreports.qt.io/secure/Dashboard.jspa
      for info.

      1 Reply Last reply
      0

      2/2

      25 May 2018, 16:31

      • Login

      • Login or register to search.
      2 out of 2
      • First post
        2/2
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • Users
      • Groups
      • Search
      • Get Qt Extensions
      • Unsolved