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.

Sign up for GitHub

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

Jump to bottom

Locales: C.UTF-8 is not available #20192

Closed
FRidh opened this issue Nov 5, 2016 · 14 comments
Closed

Locales: C.UTF-8 is not available #20192

FRidh opened this issue Nov 5, 2016 · 14 comments
Labels
0.kind: bug Something is broken

Comments

@FRidh
Copy link
Member

FRidh commented Nov 5, 2016

Issue description

The C.UTF-8 locale is missing (locale -a). We do have lots of other UTF-8 locales, but those are all country specific.
@FRidh FRidh added the 0.kind: bug Something is broken label Nov 5, 2016
@vcunat
Copy link
Member

vcunat commented Nov 5, 2016

We use the list provided by upstream in the localedata/SUPPORTED file. Any idea why they don't put it in there?

@FRidh
Copy link
Member Author

FRidh commented Nov 5, 2016

Apparently there is a strong push for putting C.UTF-8 in the binary instead, so that it can be guaranteed that it is available on all systems.
https://sourceware.org/bugzilla/show_bug.cgi?id=17318

@FRidh
Copy link
Member Author

FRidh commented Nov 5, 2016

While we could try and add C.UTF-8 support ourselves (like some other distro's have done or are planning) I think it's something best left to upstream, so I am closing this. If you think it should remain open, feel free to reopen.

@FRidh FRidh closed this as completed Nov 5, 2016
@vcunat
Copy link
Member

vcunat commented Nov 6, 2016 •
edited
Loading

The last inter-linked discussions were from February 2015, so it's possible the push isn't so strong and the issue is just stalled long-term.

I agree we would best leave this to upstream, at least until they do the first step of agreeing on some semantic details and adding C.UTF-8 among the regular generated locales.

@FRidh
Copy link
Member Author

FRidh commented May 23, 2017

It's likely that PEP 538 is accepted and that would mean Python 3.7 is going to try and use C.UTF-8 by default.

@bennofs
Copy link
Contributor

bennofs commented Jun 25, 2017

The patch from Fedora is quite simple: https://src.fedoraproject.org/cgit/rpms/glibc.git/tree/glibc-c-utf8-locale.patch

@alecmev alecmev mentioned this issue Nov 28, 2017
Closed
@concatime
Copy link
Contributor

Anything evolved since last discussion?

@jtojnar jtojnar mentioned this issue May 24, 2018
Closed
@jtojnar jtojnar mentioned this issue Jun 2, 2018
Closed
10 tasks
@FRidh
Copy link
Member Author

FRidh commented Jun 2, 2018 •
edited
Loading

Reopening because we are going to need this with Python 3.7. Not actually needed.

@FRidh FRidh reopened this Jun 2, 2018
@FRidh
Copy link
Member Author

FRidh commented Jun 2, 2018

Latest discussion on the topic upstream:
https://sourceware.org/bugzilla/show_bug.cgi?id=17318

@FRidh FRidh added this to the 18.09 milestone Jun 2, 2018
@vcunat vcunat removed this from the 18.09 milestone Sep 25, 2018
@vcunat
Copy link
Member

vcunat commented Sep 25, 2018 •
edited
Loading

Still not resolved upstream, not even in glibc-2.28 (which we don't have yet).

Mic92 added a commit to Mic92/nixpkgs that referenced this issue Dec 1, 2018
@Mic92
glibc: support of C.UTF-8
69a0c5e 
Modern systems need a modern encoding system to deal with global data.
Along with fedora and debian this enables c.utf-8 in our glibc build.
The idea is to provide a utf-8 locale along with glibc, since we are not
shipping glibcLocales by default because of its size.
Fixes NixOS#20192
@FRidh
Copy link
Member Author

FRidh commented Dec 31, 2018

@Mic92 I see you have a patch in your branch. Did you test it?

@Mic92
Copy link
Member

Mic92 commented Jan 1, 2019

@FRidh I think there was a problem somewhere, which is why I never made a pull request.

@cw789 cw789 mentioned this issue Jan 31, 2019
Merged
10 tasks
@FRidh
Copy link
Member Author

FRidh commented Feb 14, 2019

This is in master, so closing now.

@FRidh FRidh closed this as completed Feb 14, 2019
@FRidh FRidh mentioned this issue Feb 15, 2019
Closed
10 tasks
@dtzWill
Copy link
Member

dtzWill commented Feb 15, 2019

YES! Looking forward to this and resulting cleanups! (like the python PR ^_^)

@skwerlman skwerlman mentioned this issue Feb 27, 2019
Merged
@jtojnar jtojnar mentioned this issue Dec 15, 2019
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
0.kind: bug Something is broken
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@Mic92 @dtzWill @vcunat @FRidh @bennofs @concatime