IntlDateFormatter manual doesn't include enough parameter explanation
Nobody has claimed this yet.
- 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.
-
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 -
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 -
And finally which
TRADITIONALcalendars are supported?
For example, in Saudi Arabia, Iran and a few other countries,TRADITIONALcalendar returns official calendar, but In USA,TRADITIONALis the same asGREGORIAN. 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 caseHowever for a Chinese speaking person in Malaysia
TRADITIONALCalendar 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
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- 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