Bug 104892
Summary: | There is a need for more than one sorting strategy in sv locale | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux Beta | Reporter: | Göran Uddeborg <goeran> |
Component: | glibc | Assignee: | Jakub Jelinek <jakub> |
Status: | CLOSED WONTFIX | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | beta1 | CC: | fweimer |
Target Milestone: | --- | Keywords: | FutureFeature |
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-09-28 06:51:27 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Göran Uddeborg
2003-09-23 10:54:13 UTC
I was rather baffled by the new sort order as well, but have recently realized that sort appears to be sorting without regard to non-alphanumeric characters in non-C locales on the first pass. So we currently sort to: aaaaaaa A and G motor vehicles abalone Andersen, Hans Christian $$$ and no sense $$$ and sense Antigone Is this -really- the specified behavior for UTF-8 locales? I don't personally know of anyone who wants or expects this behavior. Can we at least get switches added to sort and join that will selectively disable this behavior and pay attention to non-alphanumerics in the sort? This is not about UTF-8 locales, but about what sorting is common for various languages. If you look into a dictionary, you'll see the order you get. ANd it is certainly not something recent, sort has been behaving like that for a few years already. As for the original request, I think such non-standard handling belongs into the applications which need such handling. In the particular case that would make the application significantly more complex. It today is using a PostgreSQL database, and functions like sorting is done by the database. It is not tempting to have to redo it in the application. Currently (or last I heard), they had defined a non-standard locale instead. That was deemed to be less complicated. To me it feels unfortunate one should have to do that. If the different sorting order can be expressed using the specification language localedef can provide (and I think it can, just define a high enough priority to whitespaces), then define your own locale sv_SE@wordorder or so. This data need not come with glibc, just put it in a separate package and use localedef at installation time to create the binary form. I have no interest for glibc to get into these kinds of details. We provide a good default, anything else is up to specialized "localization" packages. I'm closing this bug as WONTFIX since something like this will not get into the upstream nor RH glibc package. |