Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

On Getting Rows Doesn't differentiate bet am and pm #1060

Closed
ahmadessamshahin opened this issue Nov 14, 2021 · 3 comments
Closed

On Getting Rows Doesn't differentiate bet am and pm #1060

ahmadessamshahin opened this issue Nov 14, 2021 · 3 comments
Labels
confirmed This issue can be reproduced

Comments

@ahmadessamshahin
Copy link

Description

date column with formate 12hr (am/pm) doesn't differentiate bet if it is am or pm for example

5:30 am | 5:30 pm always read as 5:30 p12

@xuri
Copy link
Member

xuri commented Nov 16, 2021

Thanks for your feedback, could you show us a complete, standalone example program or reproducible demo? Which version of the Excelize are you using, please gave a try the master branch code. And provide your input file attachment without confidential info if you can.

@xuri xuri added the needs more info This issue can't reproduce, need more info label Nov 16, 2021
@manjdk
Copy link

manjdk commented Nov 18, 2021

Hello,
I am facing same issue. First screenshot is showing column format that is used, second - how column looks like in excel xlsx sheet, and last one - what result is. No matter AM or PM is used - that strange p12 value appears and time is not correct. Version I am using is v2.4.1.

Screenshot from 2021-11-18 15-34-17
Screenshot from 2021-11-18 15-36-48
Screenshot from 2021-11-18 15-37-10

@xuri xuri added confirmed This issue can be reproduced in progress Working in progress and removed needs more info This issue can't reproduce, need more info labels Nov 18, 2021
@xuri xuri closed this as completed in 9b0aa7a Nov 20, 2021
@xuri
Copy link
Member

xuri commented Nov 20, 2021

Thanks for your issue, I have fixed it, please upgrade to the master branch code, and this patch will be released in the next version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
confirmed This issue can be reproduced
Projects
None yet
Development

No branches or pull requests

3 participants