Issue Details (XML | Word | Printable)

Key: JRA-5647
Type: Improvement Improvement
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Brian Nguyen [OLD]
Reporter: Shinji Taneto
Votes: 0
Watchers: 1
Operations

Add/Edit UI Mockup to this issue
If you were logged in you would be able to see more operations.
JIRA

Date Picker is displayed with blank

Created: 13/Jan/05 12:57 AM   Updated: 03/May/05 12:39 AM
Component/s: Internationalisation
Affects Version/s: 3.0.3
Fix Version/s: 3.2 Beta

Time Tracking:
Not Specified

Environment: JIRA Standalone on WinXP with j2sdk1.4.2_01

Participants: Brian Nguyen [OLD], Great Lou and Shinji Taneto
Since last comment: 4 years, 15 weeks, 4 days ago
Resolution Date: 17/Mar/05 09:53 PM
Labels:


 Description  « Hide
I added language_ja_JP.jar with translated .properties files, and switched to Japanese locale as default.
Then, I was trying to create a new issue and click calendar icon, but date picker was displayed with blank window.

I searched the exisiting bug with same situation and found the following comment:

http://jira.atlassian.com/browse/JRA-2652

----------------------------------------------------------------------------------------------------
I'm in chinese environment(i'll use the calendar-zh.js in calendar.jsp). When click the date picker image in create-new-issue page, it will pop up a windows with a script error. Debug and find following error prompt:
Calendar._TT.DEF_DATE_FORMAT is null or it's not an object
(some this meaning in chinese).

And the cussor of the debugger stop at following the last line:
Calendar = function (mondayFirst, dateStr, onSelected, onClose) {
// member variables
this.activeDiv = null;
this.currentDateEl = null;
this.getDateStatus = null;
this.timeout = null;
this.onSelected = onSelected || null;
this.onClose = onClose || null;
this.dragging = false;
this.hidden = false;
this.minYear = 1970;
this.maxYear = 2050;
this.dateFormat = Calendar._TT["DEF_DATE_FORMAT"];
----------------------------------------------------------------------------------------------------

Does anyone know a solution for this problem?

Shinji Taneto
shinji.taneto@portus.co.jp



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Great Lou added a comment - 13/Mar/05 01:45 AM

I'd just solved similar problem,below is my solution:

1. check JIRA configuration wether using Encoding UTF-8.if so, u must check very carefully that the file calendar-*.js is also Encoded by UTF-8,and the file name is correct. (so many problems relate to using calendar occur only because of using wrong encoding format or wrong calendar-*.js file name. ) I use Editplus to check wether the file have UTF-8 format:
open the file calendar-**.js in Editplus, if file content looks fine and file-format-text displayed in Editplus status bar is "PC,U8",then the file is ok(file-format-text is located in right-bottom of Editplus Editor).

2. check jira-application.properties ,setup correct date fromat,for example:
jira.date.picker.java.format = yyyy.MM.dd
jira.date.picker.javascript.format = %Y.%m.%e

3.check calendar-**.js,setup correct dataformat .Mine is :

// date formats
Calendar._TT["DEF_DATE_FORMAT"] = "yyyy.MM.dd";
Calendar._TT["TT_DATE_FORMAT"] = "yyyy.MM.dd";

4.check calendar-**.js,be sure have these lines:

// First day of the week. "0" means display Sunday first, "1" means display
// Monday first, etc.
Calendar._FD = 0;


Brian Nguyen [OLD] added a comment - 13/Mar/05 09:42 PM
Hi,

The bug relating to the blank calendar when using the datepicker has been raised in an earlier issue JRA-5765. To fix this error you will need to change the name of the file calendar-jp.js to calendar-ja.js.

Thanks,
Brian


Shinji Taneto added a comment - 13/Mar/05 11:01 PM
Thank you very much, Great Lou, Brian,

Now, datepicker works fine.
I changed the encoding to UTF-8 and renamed calendar-jp.js to calendar-ja.js.
Also, I changed jira-application.properties as Great Lou mentioned.

Thanks again for your help.

Best Regards,
Shinji


Brian Nguyen [OLD] added a comment - 17/Mar/05 09:53 PM
I believe this issue has been resolved now.
If you come across any further problems either reopen this issue or create a new issue.