php / php/doc-en

IntlDateFormatter manual doesn't include enough parameter explanation

Open
#1,484 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Extension: intl
Dominant language
XML
Stars
596
Forks
890
Avg merge
1d 15h
Merged PRs (30d)
55

Description

From manual page: https://php.net/class.intldateformatter


There are not enough explanations of constructor parameters.

  1. What are valid values for $locale? I happen to know that locale is not just en-US or fa-IR and it is like fa_IR@calendar=persian

  2. What are valid values for $pattern? I can see y, m and d in combinations, but how do I specify time pattern in input? for example when on GMT it is still 9PM, it is already next day on GMT+8

  3. And finally which TRADITIONAL calendars are supported?
    For example, in Saudi Arabia, Iran and a few other countries, TRADITIONAL calendar returns official calendar, but In USA, TRADITIONAL is the same as GREGORIAN. This means passing date through format, will change it to official calendar of country for first case but will not touch it for second case, which is desired effect in my case

    However for a Chinese speaking person in Malaysia TRADITIONAL Calendar is not official calendar which means in a global website simply passing every date through format will not return official date.
    To address this, I need to know which Traditional Calendars are supported and in my code change them accordingly

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the IntlDateFormatter manual page at https://php.net/class.intldateformatter and review the constructor-parameter documentation. Research valid locale forms, date and time pattern syntax, and supported TRADITIONAL calendars; the work is done when these questions are answered clearly with appropriate examples or references.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.