Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0001135Openbravo ERPZ. Otherspublic2007-04-18 11:362022-02-01 07:24
Reporteruser11 
Assigned ToTriage Platform Base 
PrioritynormalSeverityminorReproducibilityalways
StatusnewResolutionopen 
PlatformOS5OS Version
Product Version 
Target VersionFixed in Version 
Merge Request Status
Review Assigned To
OBNetwork customer
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0001135: Calendar only support western calendars
DescriptionHello,

Diferent places in the world use different calendar formats. In Iran, for example, they use the Islamic Calendar:

http://en.wikipedia.org/wiki/Islamic_calendar [^]

IBM has a good summary of the different calendar types:

http://www-306.ibm.com/software/globalization/topics/locales/calendar_intro.jsp [^]

We should add support for other calendar formats in our calendar control.

Jordi,
Steps To Reproduce
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2016-06-02 14:25hgbotCheckin
2016-06-02 14:25hgbotNote Added: 0086924
2016-06-02 14:25hgbotStatusclosed => resolved
2016-06-02 14:25hgbotFixed in SCM revision => http://code.openbravo.com/erp/pmods/org.openbravo.retail.deliveryconditions/rev/fa49d529166a4062472e71118e79c68bb8550938 [^]
2016-06-24 10:08hgbotCheckin
2016-06-24 10:08hgbotNote Added: 0087882
2016-06-24 10:08hgbotFixed in SCM revisionhttp://code.openbravo.com/erp/pmods/org.openbravo.retail.deliveryconditions/rev/fa49d529166a4062472e71118e79c68bb8550938 [^] => http://code.openbravo.com/erp/pmods/org.openbravo.retail.deliveryconditions/rev/33ce4ad88f7e0cfb0eb660a4547a2084abd970e6 [^]
2016-06-24 10:09hgbotCheckin
2016-06-24 10:09hgbotNote Added: 0087883
2016-06-24 10:09hgbotFixed in SCM revisionhttp://code.openbravo.com/erp/pmods/org.openbravo.retail.deliveryconditions/rev/33ce4ad88f7e0cfb0eb660a4547a2084abd970e6 [^] => http://code.openbravo.com/erp/pmods/org.openbravo.retail.deliveryconditions/rev/df8787bfba1786b1c7d5000108741c0d6563a45a [^]
2020-10-02 12:43marvintmAssigned Touser71 => platform
2020-10-02 12:43marvintmNote Added: 0123494
2020-10-02 12:43marvintmStatusresolved => new
2020-10-02 12:43marvintmResolutionfixed => open
2022-02-01 07:24alostaleAssigned Toplatform => Triage Platform Base

Notes
(0004724)
user71   
2005-06-01 00:00   
(edited on: 2008-06-12 09:43)
This bug was originally reported in SourceForge bug tracker and then migrated to Mantis.

You can see the original bug report in:
https://sourceforge.net/support/tracker.php?aid=1702785 [^]
(0000990)
user71   
2007-04-19 07:23   
(edited on: 2008-06-12 09:18)
Logged In: YES
user_id=1770604
Originator: NO

Hello EveryBody,
There is a little diffrent between Persian (Shamsi) calendar and lunar (ghamari) calendar and gregorian Calendar
persian calendar has 12 month as shown below
1.Farvardin - 31 days - Equal April
2.Ordibehesht - 31 days - Equal May
3.Khordad - 31 days - Equal June
4.Tir - 31 days - Equal July
5.Mordad - 31 days - Equal August
6.Shahrivar - 31 days - Equal September
7.Mehr - 30 days - Equal October
8.Aban - 30 days - Equal November
9.Azar - 30 days - Equal December
10.Day - 30 days - Equal January
11.Bahman - 30 days - Equal February
12.Esfand - 29 days - Eqaul March
And per each four years esfand becomes 30 days
(0000991)
user71   
2007-06-27 16:37   
(edited on: 2008-06-12 09:18)
Logged In: YES
user_id=1500724
Originator: NO

We are using the jscalendar's project. They are in charge of the localization of the calendar. If they implements this kind of calendar we would implement them in our ERP.
(0000992)
user71   
2007-07-18 06:24   
(edited on: 2008-06-12 09:18)
Logged In: YES
user_id=1770604
Originator: NO

you can see more details about persian calendar here
http://en.wikipedia.org/wiki/Persian_calendar [^]
(0000993)
user71   
2007-07-18 08:08   
(edited on: 2008-06-12 09:18)
Logged In: YES
user_id=1623109
Originator: NO

That was changed to:
http://www-304.ibm.com/jct03001c/software/globalization/topics/locales/calendar_intro.jsp [^]
(0086924)
hgbot   
2016-06-02 14:25   
Repository: erp/pmods/org.openbravo.retail.deliveryconditions
Changeset: fa49d529166a4062472e71118e79c68bb8550938
Author: Prakash M <prakash <at> qualiantech.com>
Date: Wed May 25 09:57:42 2016 +0530
URL: http://code.openbravo.com/erp/pmods/org.openbravo.retail.deliveryconditions/rev/fa49d529166a4062472e71118e79c68bb8550938 [^]

Fixes Issue 1135: Delivery Condition Time Validation

---
M src-db/database/sourcedata/AD_MESSAGE.xml
M web/org.openbravo.retail.deliveryconditions/js/receiptEdit.js
M web/org.openbravo.retail.deliveryconditions/js/receiptMultiLineEdit.js
---
(0087882)
hgbot   
2016-06-24 10:08   
Repository: erp/pmods/org.openbravo.retail.deliveryconditions
Changeset: 33ce4ad88f7e0cfb0eb660a4547a2084abd970e6
Author: Prakash M <prakash <at> qualiantech.com>
Date: Wed May 25 09:57:42 2016 +0530
URL: http://code.openbravo.com/erp/pmods/org.openbravo.retail.deliveryconditions/rev/33ce4ad88f7e0cfb0eb660a4547a2084abd970e6 [^]

Fixes Issue 1135: Delivery Condition Time Validation

---
M src-db/database/sourcedata/AD_MESSAGE.xml
M web/org.openbravo.retail.deliveryconditions/js/receiptEdit.js
M web/org.openbravo.retail.deliveryconditions/js/receiptMultiLineEdit.js
---
(0087883)
hgbot   
2016-06-24 10:09   
Repository: erp/pmods/org.openbravo.retail.deliveryconditions
Changeset: df8787bfba1786b1c7d5000108741c0d6563a45a
Author: Prakash M <prakash <at> qualiantech.com>
Date: Wed May 25 09:57:42 2016 +0530
URL: http://code.openbravo.com/erp/pmods/org.openbravo.retail.deliveryconditions/rev/df8787bfba1786b1c7d5000108741c0d6563a45a [^]

Fixes Issue 1135: Delivery Condition Time Validation

---
M src-db/database/sourcedata/AD_MESSAGE.xml
M web/org.openbravo.retail.deliveryconditions/js/receiptEdit.js
M web/org.openbravo.retail.deliveryconditions/js/receiptMultiLineEdit.js
---
(0123494)
marvintm   
2020-10-02 12:43   
Commits associated to the issue are not actually related to it. Issue is most probably still valid.