Bug 64226
Summary: | Sort creates wrong order if sorting multiple fields | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Fedor Pikus <pikus> |
Component: | textutils | Assignee: | Tim Waugh <twaugh> |
Status: | CLOSED NOTABUG | QA Contact: | Ben Levenson <benl> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.2 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2002-09-26 02:03:24 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
Fedor Pikus
2002-04-29 18:50:11 UTC
This 'multiple fields' bug is likely caused by the fact that if LC_COLLATE is undefined (and that's the default configuration it seems) sort ignores spaces. This came up in bug 17204 too. I've found 'default' sort also ignores hyphens. The following text is considered sorted: x 30 x -4 x 50 Seems pretty wrong IMO. I couldn't find a Posix spec for what should happen when LC_COLLATE is undefined. If it's up to the implementer it would seem defaulting to C-style would be safer than the current approach. -Bill Hees 'Undefined'? What exactly is LC_COLLATE in your example? Not C, I'll be bound. |