Locale Contributions Wanted 🙋🙏

Release 1.6.2 was just published to the NPM with I18n support. Thanks again, everyone, for helping with this effort.

Day.js users come from all around the world, so I will happily accept translations from other languages for this project. And your work will affect thousands of daily users of Day.js.

Feel free to open a pull request if you’ve finished one of the three translations.

Locale (I18n)

Locale is the first translation work we need to do, and it will be released with our main code. Locale template

Readme file

Readme file let user get a glance of our project. And tells them what we are doing. If there is no sub pages’ translation, please keep the links in readme linked to English sub pages. Add a link to your translation in the default english readme file. Default English Readme

Sub pages of the document

Sub pages is the detailed documents of our project.

NOTE: It is welcome to put your language in the first place in locale example in files such as I18n.md. e.g. for Japanese docs

import 'dayjs/locale/ja'
// was import es in English ducoment
dayjs.locale('ja') // use Japanese locale globally 

Sub pages folder

Directory structure

Please place the translation files in a separate folder, and named with ISO 639-1 area code. Directory structure could be found below.

.
├── docs
│   └── es
│        ├── API-reference.md
│        ├── I18n.md
│        ├── Installation.md
│        ├── Plugin.md
│        └── README-es.md
├── src
│   └── locale
│        └── es.js
└── README.md  // default index english readme

Finally, thanks again for your contribution.

Append: We use ISO 639-2 country code. Check lists short codes for language here or here

[iamkun]

Thanks, I’ve updated the .gitignore file, and it should be OK now.

[MartinDawson]

At the moment dayjs only accepts language language code such as ‘en’. Would be nice to accept formats like ‘en-US’ instead of having dayjs fail later on.

The same as Moment.js Issue 422