A WordPress plugin developed by Simula Lab Ltd that gives the Arabic site admin the possibility to use Levantine Arabic Month Names in WordPress dates instead of (or in combination with) Modern Standard Arabic month names. It also allows for using Arabic-Indic numerals instead of Arabic numerals in WordPress dates and time. The plugin is also available to download from the official wordpress plugins directory here: https://wordpress.org/plugins/simula-levantine-dates-for-arabic-sites/
- Use Arabic-Indic numeral (١, ٢, ٣) instead of Arabic numerals (1, 2, 3) in WordPress dates and times.
- Use Levantine Arabic months names instead (شباط, آذار) of Modern Standard Arabic months names (فبراير, مارس) in WordPress dates.
- Use a mix of Levantine and Standard Arabic months names (شباط/فبراير, آذار/مارس) or (فبراير/شباط, مارس/آذار) instead of Modern Standard Arabic months names.
Login as an admin, navigate to "Plugins" then click the "Add new plugin" button.
Search for the plugin name in the search bar, as it is available in the wordpress.org public plugins directory then when you find it click on "Install Now".
or...
Download the plugin folder, compress the folder to a .zip
file.
Login as an admin, navigate to "Plugins" then click the "Add new plugin" button.
Then click on "Upload Plugin", and upload the zip file, then click "Install Now"
Activate the plugin upon successful installation.
Make sure the plugin is activated, and that the language of the site is set to "العربية"
Navigate to "الإعدادات", then select "نسق التاريخ في بلاد الشام" from the settings sidebar menu.
Select an option of the available options for "خيارات نسق الشهور"
Check/Uncheck the "استخدم الأرقام الهندية"
Click "Save"
Make sure the desired effect can be observed in the format of dates and times of pages and posts and other site elements.
Compare the "تم النشر في" of the following screenshots:
Before selecting Levantine Arabic month names and Arabic-Indic numerals:
After selecting Levantine Arabic month names and Arabic-Indic numberals:
Please create an issue for the bug, and try to be thourough. If possible include screenshots, and other important details such as WordPress version, PHP version, etc.
Contributions are welcome!
When creating a pull request make sure to use the following template:
Change Summary
- item one
- item two
Related issue number
- issue a
- issue b
Checklist
[ ] code is ready
[ ] add tests
[ ] all tests passing
[ ] test coverage did not drop
[ ] PR is ready for review
- update the plugin code
- test your changes
- update version number in readme.txt and meta data
- git commit changes to this repository
- use svn to checkout the SVN repository
- add changes to /trunk/ and to /tags/{{major.minor.patch}}/
- svn commit changes to plugins directory
The plugin was developed under the GPL-2.0 license: http://www.gnu.org/licenses/gpl-2.0.html.