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
Description
I am writing a program to convert an Excel file to csv using Excelize.
Basically, Excelize works well, but it cannot read the date format if the format is a date and Japanese calendar.
I read the source code and found that the Japanese calendar format does not seem to be supported.
I would like to see it supported if possible.
Steps to reproduce the issue:
Excel cell formatting > Date > local: Japanese, Calendar type: Japanese
example cell view: 令和3年6月30日 (this is 2021/06/20)
Write the line obtained by excelize.Rows.Columns() to csv
Describe the results you received: 44377
Describe the results you expected:
I wanted to get 令和3年6月30日 as it appeared in Excel
Output of go version:
go version go1.20.6 darwin/arm64
Excelize version or commit ID:
v2.7.1
Environment details (OS, Microsoft Excel™ version, physical, etc.):
Windows server 2012 R2
Microsoft Excel for Microsoft 365 MSO (version 2301 build: 16.0.16026.20196)
The text was updated successfully, but these errors were encountered:
Thanks for your issue. I have added support for the Japanese calendar, please try to upgrade the master branch code, and this feature will be released in the next version.
Description
I am writing a program to convert an Excel file to csv using Excelize.
Basically, Excelize works well, but it cannot read the date format if the format is a date and Japanese calendar.
I read the source code and found that the Japanese calendar format does not seem to be supported.
I would like to see it supported if possible.
Steps to reproduce the issue:
令和3年6月30日
(this is 2021/06/20)Describe the results you received:
44377
Describe the results you expected:
I wanted to get
令和3年6月30日
as it appeared in ExcelOutput of
go version
:Excelize version or commit ID:
Environment details (OS, Microsoft Excel™ version, physical, etc.):
The text was updated successfully, but these errors were encountered: