Skip to content
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

Help newlib TZ parser #7699

Merged
merged 3 commits into from
Nov 10, 2020
Merged

Help newlib TZ parser #7699

merged 3 commits into from
Nov 10, 2020

Commits on Nov 10, 2020

  1. TZ: help newlib parser

    Timezones coded with <±nn>±nn<±nn>[±nn][,...] are incorrectly parsed by newlib's TZ parser.
    In these timezones, <±nn> is used because there is no matching name like in other timezones.
    Example: 'GMT0BST' for London, (GMT is known, BST is 'British Summer Time').
    Example: '<+1030>-10:30<+11>-11' for Lord Howe Island.
    These names GMT,BST,CET,... are meant to be human readable but are useless in our use case.
    Replacing <±nn> occurences by UNK allows newlib's TZ parser to nicely interpret all timezones.
    Ultimately, newlib should handle such tz descriptor. Until then, they are handled by this script.
    d-a-v committed Nov 10, 2020
    Configuration menu
    Copy the full SHA
    664fee9 View commit details
    Browse the repository at this point in the history
  2. fix comment

    d-a-v committed Nov 10, 2020
    Configuration menu
    Copy the full SHA
    70fb2d8 View commit details
    Browse the repository at this point in the history
  3. Configuration menu
    Copy the full SHA
    de87dc7 View commit details
    Browse the repository at this point in the history