As the developers of Open Journal Systems, Open Conference Systems, Open Harvester Systems, and Open Monograph Press, the PKP team are experts in helping journal managers and conference organizers make the most of their online publishing projects. PKP Publishing Services offers support for:

As a customer of PKP Publishing Services, you will not only receive direct, personalized support from the PKP Development Team, but will be contributing to the ongoing development of the PKP applications. All funds raised by PKP Publishing Services go directly toward enhancing our free, open source software. For more information, please contact us.

Forum rules
This forum is meant for general questions about the usability of OCS from an everyday user's perspective: conference managers, presenters, and directors are welcome to post questions here, as are librarians and other support staff. We welcome general questions about the role of OCS and how the workflow works, as well as specific function- or user-related questions.

What to do if you have general, workflow or usability questions about OCS:

1. Read the documentation. We've written documentation to cover from OCS basics to system administration and code development, and we encourage you to read it.

2. take a look at the tutorials. We will continue to add tutorials covering OCS basics as time goes on.

3. Post a question. Questions are always welcome here, but if it's a technical question you should probably post to the OCS Technical Support subforum; if you have a development question, try the OCS Development subforum.

Changing to Persian may be a little tricky, but try and follow the instructions set out in the following thread: viewtopic.php?f=9&t=2068. PHP's date formatting tools may not be up to Persian dates. Don't worry about the patch discussed in the above thread: it has been included in recent releases.

- %a - abbreviated weekday name according to the current locale- %A - full weekday name according to the current locale- %b - abbreviated month name according to the current locale- %B - full month name according to the current locale- %c - preferred date and time representation for the current locale

You will also have to ensure that your default locale is set to Persian in config.inc.php. we can't guarantee that this will work: this is essentially a PHP function, and they may not fully support Persian. Please let us know how you do, and we may be able to provide more assistance.

We're not especially familiar with using Persian dates -- but we're using standard PHP tools to manage dates, so I did a bit of googling to find whether and how PHP supports them. From pages such as http://bakery.cakephp.org/articles/view/persian-date-helper it appears that PHP does not natively support Persian dates (though I could be wrong). If that's the case, you'll need to do a little bit of PHP work to get Persian dates working. Here is what you'll need to do:

Following is a work around to have Jalali calendar in Farsi pages of OJS:

1. Create a jalali folder in classes (lowercase)2. Place the file Jalali.inc.php in that folder (attached here)3. in the file TemplateManager.in.php: Includ 'smarty/plugins/modifier.date_format.php' at the beginning

The Jalali plugin only affects the display of dates, not the date select tools. However, if your server supports Farsi dates and you're using the Farsi locale, the Smarty date selector should include translated month names. If you are maintaining your own server, make sure that the fa_IR locale is enabled in /etc/locale.gen. You may need to run locale-gen after uncommenting this line. (Note that these instructions will depend largely on what kind of server you are running.)

Hello all,I'm not sure if I should post this here.I may eventually do the worst thing in forums and cross-post (here) just to reinforce the point.The point is that date-time configurations should be defined by language.This means that a single option to define the formats is not enough for a multilingual system.I believe the simplest way to do this is to create separate config files for languages, loaded when language changes (maybe even created on-the-fly after installation) and a general config file with the basics.Then, the administrator would have a new option to configure each option for each language.I think this makes more sense, although not sure how or if it will/should be implemented.The date-time config may also be implemented as a Pluing, if possible...