You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is inspired by this StackOverflow question. The problem is that even with ns.LOCALE some non-ASCII letters are not sorted as you might expect, but running it through unicode.normalize does the trick.
It is not clear if this should be the default behavior or an add-on. It is also not clear if it should default to 'NFD' or if it can be more flexible.
The text was updated successfully, but these errors were encountered:
All unicode input now gets 'NFD' normalization, which ensures that
all characters that look the same are represented by the same code
points. 'NFD' was chosen because it is the expanded for which will
cause (for example) 'é' to be placed immediately after 'e' rather than
after 'z'.
Users can choose 'NFKD' with ns.COMPATIBILITYNORMALIZE (or ns.CN) which
will change certain characters to their compatible (and often ASCII)
representation. This may be useful to cause force numbers in odd
representations to be transformed to ASCII which will potentially give
better sorting orders.
This will close issue #44.
This is inspired by this StackOverflow question. The problem is that even with
ns.LOCALE
some non-ASCII letters are not sorted as you might expect, but running it throughunicode.normalize
does the trick.It is not clear if this should be the default behavior or an add-on. It is also not clear if it should default to
'NFD'
or if it can be more flexible.The text was updated successfully, but these errors were encountered: