You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the GanttComposite.java file of the package org. eclipse. newula. widgets. Ganttchart, in the getDate String method, DateHelper. getDate (cal, _settings. getWeekHeaderTextDisplayBottom()) performs string splitting on the return value, causing "星期一(Monday)" and "星期二(Tuesday)" to become "星" in the Chinese environment. This seems very unfriendly to Chinese users. Since I am using a lower version, I modified substring (0,1) to substring by decompiling. (2, 3), temporarily resolved this issue. I think the Gant diagram plugin is very good, so I hope this issue can be fixed in a new version.
Before making changes
After making changes
Thanks!
The text was updated successfully, but these errors were encountered:
liutaoPLM
changed the title
In the Chinese (zh_cn) environment, if displayed in week mode in GanttChat, incorrect date conversion may occur.
In the Chinese (zh_cn) environment, if displayed in week mode in GanttChart, incorrect date conversion may occur.
Jun 18, 2024
I have no idea why it's taking just the first character. That doesn't seem very locale sensitive, but doubt hard coding (2, 3) is going to be correct in all cases either.
In the GanttComposite.java file of the package org. eclipse. newula. widgets. Ganttchart, in the getDate String method, DateHelper. getDate (cal, _settings. getWeekHeaderTextDisplayBottom()) performs string splitting on the return value, causing "星期一(Monday)" and "星期二(Tuesday)" to become "星" in the Chinese environment. This seems very unfriendly to Chinese users. Since I am using a lower version, I modified substring (0,1) to substring by decompiling. (2, 3), temporarily resolved this issue. I think the Gant diagram plugin is very good, so I hope this issue can be fixed in a new version.
Before making changes
After making changes
Thanks!
The text was updated successfully, but these errors were encountered: