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

Incorrect DateTimeFormat for nb-NO in Blazor WebAssembly #67115

Closed
AbstractionsAs opened this issue Mar 24, 2022 · 6 comments
Closed

Incorrect DateTimeFormat for nb-NO in Blazor WebAssembly #67115

AbstractionsAs opened this issue Mar 24, 2022 · 6 comments
Assignees
Labels
Milestone

Comments

@AbstractionsAs
Copy link

Description

Getting month and day names returns incorrect values.
Months come back as M01, M02, etc
Days come back as English day names

Reproduction Steps

var culture = CultureInfo.GetCulture("nb-NO");

// Should return 'mars', returns 'M03'
var march= culture.DateTimeFormat.GetMonthName(3);

// Should return 'tirsdag', returns 'Tuesday'
var tuesday = culture.DateTimeFormat.DayNames[2];

Expected behavior

Should return the correct values

Actual behavior

Returns incorrect values

Regression?

No response

Known Workarounds

No response

Configuration

.net 6
Windows 10 (WebAssembly)
x64
Spesific to blazor WebAssembly
All browsers

Other information

No response

@dotnet-issue-labeler dotnet-issue-labeler bot added area-System.Globalization untriaged New issue has not been triaged by the area owner labels Mar 24, 2022
@ghost
Copy link

ghost commented Mar 24, 2022

Tagging subscribers to this area: @dotnet/area-system-globalization
See info in area-owners.md if you want to be subscribed.

Issue Details

Description

Getting month and day names returns incorrect values.
Months come back as M01, M02, etc
Days come back as English day names

Reproduction Steps

var culture = CultureInfo.GetCulture("nb-NO");

// Should return 'mars', returns 'M03'
var march= culture.DateTimeFormat.GetMonthName(3);

// Should return 'tirsdag', returns 'Tuesday'
var tuesday = culture.DateTimeFormat.DayNames[2];

Expected behavior

Should return the correct values

Actual behavior

Returns incorrect values

Regression?

No response

Known Workarounds

No response

Configuration

.net 6
Windows 10 (WebAssembly)
x64
Spesific to blazor WebAssembly
All browsers

Other information

No response

Author: AbstractionsAs
Assignees: -
Labels:

area-System.Globalization, untriaged

Milestone: -

@tarekgh tarekgh added the arch-wasm WebAssembly architecture label Mar 24, 2022
@ghost
Copy link

ghost commented Mar 24, 2022

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

Issue Details

Description

Getting month and day names returns incorrect values.
Months come back as M01, M02, etc
Days come back as English day names

Reproduction Steps

var culture = CultureInfo.GetCulture("nb-NO");

// Should return 'mars', returns 'M03'
var march= culture.DateTimeFormat.GetMonthName(3);

// Should return 'tirsdag', returns 'Tuesday'
var tuesday = culture.DateTimeFormat.DayNames[2];

Expected behavior

Should return the correct values

Actual behavior

Returns incorrect values

Regression?

No response

Known Workarounds

No response

Configuration

.net 6
Windows 10 (WebAssembly)
x64
Spesific to blazor WebAssembly
All browsers

Other information

No response

Author: AbstractionsAs
Assignees: -
Labels:

arch-wasm, area-System.Globalization, untriaged

Milestone: -

@tarekgh
Copy link
Member

tarekgh commented Mar 24, 2022

CC @lewing

@lewing
Copy link
Member

lewing commented Mar 30, 2022

This is likely a result of the way we strip down the formatting data for size reasons. Can you explain your use case to help us prioritize changes?

@lewing lewing added this to the 7.0.0 milestone Mar 30, 2022
@lewing lewing removed the untriaged New issue has not been triaged by the area owner label Mar 30, 2022
@AbstractionsAs
Copy link
Author

AbstractionsAs commented Mar 30, 2022 via email

@ilonatommy
Copy link
Member

Thank you for reporting it, we are aware of the problem. This is a duplicate of #53239.

@ghost ghost locked as resolved and limited conversation to collaborators Jul 23, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

4 participants