Inconsistent case sensitivity in sorting key lists

Question

Inconsistent case sensitivity in sorting key lists

Closed this issue 10 years ago · 6 comments

This leads to mutually incompatible license files in cases where the keys sort differently.

Case-insensitive: Cocoa, PHP, CoreFoundation
Case-sensitive: Python, Ruby, C#

Given the prevalence of the PHP implementation, that algorithm should probably prevail. Should probably also make a stand on diacritic-sensitive sorting, too.

Answer 1 · 2010-10-08T12:19:34.000Z

As of 2217857, Ruby is now correctly case-insensitive.

Answer 2 · 2010-10-08T12:22:10.000Z

As of 06ba6a6, there's several test cases that can be used to evaluate an implementation's compliance with the "official" signatures.

Answer 3 · 2014-02-03T22:19:48.000Z

I wonder why you guys sort keys for hashing... really I cannot imagine why...

Answer 4 · 2014-04-15T12:18:38.000Z

Please release AP V2,
get rid of the sorting and sequentially hash key and values as common sense dictates....

Answer 5 · 2014-06-07T22:43:55.000Z

As AP is fortunately open source, you or anybody else are welcome to branch it and set up any alternative standards that you like.

Answer 6 · 2014-06-27T08:25:20.000Z

You mean "branching" the project just to fix what is currently "nuts" in AP??
No man; my common sense tells me this project has 2 VERY BIG flaws that should be
fixed in a new version of AP not in a new branch of it.

The hash should be performed top down over the "unsorted" license file.
The hash should be performed over "Keys" and Values, not just only on values

Probably the day that you guys decide to address these simple changes this handy project will make a little bit more sense.