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

Substitute out geopolitical term in TimeZoneInfo #82916

Merged
merged 1 commit into from
Mar 3, 2023

Conversation

mdh1418
Copy link
Member

@mdh1418 mdh1418 commented Mar 2, 2023

PoliCheck classified the term as geopolitical. Replaced with term referred to in https://www.unix.com/man-page/freebsd/8/tzsetup/.

@ghost ghost assigned mdh1418 Mar 2, 2023
@dotnet-issue-labeler
Copy link

I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label.

@@ -134,7 +134,7 @@ private static List<string> ParseTimeZoneIds(StreamReader reader)
{
if (!string.IsNullOrEmpty(zoneTabFileLine) && zoneTabFileLine[0] != '#')
{
// the format of the line is "country-code \t coordinates \t TimeZone Id \t comments"
// the format of the line is "ISO 3166 territory code \t coordinates \t TimeZone Id \t comments"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is interesting that the standard is using Country Code https://www.iso.org/iso-3166-country-codes.html. I don't mind using territory though.

@tarekgh tarekgh added this to the 8.0.0 milestone Mar 2, 2023
@tarekgh tarekgh merged commit 86173c0 into dotnet:main Mar 3, 2023
@ghost ghost locked as resolved and limited conversation to collaborators Apr 2, 2023
@mdh1418 mdh1418 deleted the fix_timezoneinfo_geopolitical_term branch June 10, 2024 21:45
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants