Skip to content

Describe date/time formatting functions and options #623

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

Merged
merged 7 commits into from
Feb 7, 2024

Conversation

aphillips
Copy link
Member

Based on the 2024-02-05 teleconference discussion, describe the date/time formatting functions in a manner similar to the number selection design document.

Open issues:

  • I reference BCP175 and the IANA time zone database. Should we have additional zone IDs supported, such as the BCP47 compatible ones from ULIs?
  • We need to choose the supported serialization(s) for date literals. RFC3339, XMLSchema, and JSON all provide some things here. SEDATE's extension to support Temporal should be added when its ready.

Based on the 2024-02-05 teleconference discussion, describe the date/time formatting functions in a manner similar to the number selection design document.
aphillips and others added 4 commits February 6, 2024 10:07
Co-authored-by: Eemeli Aro <eemeli@mozilla.com>
Co-authored-by: Eemeli Aro <eemeli@mozilla.com>
Here I have tried to be more rigorous in describing the functions and their options. Note that we as a group still need to agree to this design.
@aphillips aphillips requested a review from eemeli February 7, 2024 01:15
Copy link
Collaborator

@eemeli eemeli left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Eh, this is fine. I appreciate the explicit note about variable string values.

For more information, see [Working with Timezones](https://w3c.github.io/timezone).

> [!IMPORTANT]
> The [ABNF](/main/spec/message.abnf) and [syntax](/main/spec/syntax.md) of MFv2
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
> The [ABNF](/main/spec/message.abnf) and [syntax](/main/spec/syntax.md) of MFv2
> The [ABNF](/spec/message.abnf) and [syntax](/spec/syntax.md) of MF2

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed by using /main/spec/syntax.md (etc.)

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks. I did a direct fix.

@aphillips aphillips added functions Issue pertains to the default function set normative Issue affects normative text in the specification LDML45 LDML45 Release (Tech Preview) labels Feb 7, 2024
@aphillips
Copy link
Member Author

I'm going to merge this now as a basis for discussion next week in the F2F.

@aphillips aphillips merged commit 9d25057 into main Feb 7, 2024
@aphillips aphillips deleted the aphillips-date-time-description branch February 7, 2024 17:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
functions Issue pertains to the default function set LDML45 LDML45 Release (Tech Preview) normative Issue affects normative text in the specification
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants