Summary | Select Non-English Time from the Time drop down list. System will show error message. Function won't work |
Queue | Kronolith |
Queue Version | 4.0.2 |
Type | Bug |
State | No Feedback |
Priority | 1. Low |
Owners | |
Requester | alanl (at) azblink (dot) com |
Created | 12/10/2012 (4594 days ago) |
Due | |
Updated | 04/03/2013 (4480 days ago) |
Assigned | 12/10/2012 (4594 days ago) |
Resolved | 04/03/2013 (4480 days ago) |
Github Issue Link | |
Github Pull Request | |
Milestone | |
Patch | No |
dialog of the dynamic use doesn't use localized time formats at all.
of the dynamic use doesn't use localized time formats at all.
We have tested it on "Traditional Chinese" and "Japanese" locale.
Both of these two locale have this reporting bug problem.
If we use in non-English (Chinese zh_TW and jp version), we can not
create any new event in these two language.
I believe, it is a show stopper for "Double Byte Character Set"
version for Horde.
Because, it is the entry point of this application (Calendar), if the
entry point break, we can not use this application in Horde. So, this
is an imporant bug to fix.
We have tested it on "Traditional Chinese" and "Japanese" locale.
Both of these two locale have this reporting bug problem.
Priority ⇒ 1. Low
Patch ⇒ No
State ⇒ Feedback
Priority ⇒ 3. High
State ⇒ Unconfirmed
New Attachment: hode_bug.docx
Patch ⇒ Yes
Milestone ⇒
Queue ⇒ Kronolith
Due ⇒ 12/20/2012
Summary ⇒ Select Non-English Time from the Time drop down list. System will show error message. Function won't work
Type ⇒ Bug
Step 2: On the event dialog, select any entry from the time drop down
list. (Non-English Time showed on the drop dwo list.)
Result: It showed error message saying that the selected item is an
unknown time format. And ask user to try another time format.
Expectation: When select any entry, it should work as the action is
working in English version.