Skip to content

Commit cd2e11b

Browse files
committed
A little more changelog for #1429
1 parent c520747 commit cd2e11b

File tree

1 file changed

+9
-8
lines changed

1 file changed

+9
-8
lines changed

docs/changelog.rst

Lines changed: 9 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -4,9 +4,9 @@ Changelog
44
1.3.12 (in development)
55
-----------------------
66

7-
This little update makes queries more powerful and removes a performance
8-
bottleneck. There's an experimental new plugin for synchronizing metadata with
9-
music players.
7+
This little update makes queries more powerful, sorts music more
8+
intelligently, and removes a performance bottleneck. There's an experimental
9+
new plugin for synchronizing metadata with music players.
1010

1111
Packagers should also note a new dependency in this version: the `Jellyfish`_
1212
Python library makes our text comparisons (a big part of the auto-tagging
@@ -23,11 +23,12 @@ New features:
2323
* The autotagger's **matching algorithm is faster**. We now use the
2424
`Jellyfish`_ library to compute string similarity, which is better optimized
2525
than our hand-rolled edit distance implementation. :bug:`1389`
26-
* **Sorting is now case insensitive** by default. This means that artists will
27-
be sorted lexicographically regardless of case, e.g., *Bar foo Qux*.
28-
Previously this would have resulted in *Bar Qux foo*. This behavior can be
29-
configured via the :ref:`sort_case_insensitive` configuration option.
30-
See :ref:`query-sort`. :bug:`1429`
26+
* Sorting is now **case insensitive** by default. This means that artists will
27+
be sorted lexicographically regardless of case. For example, the artist
28+
alt-J will now properly sort before YACHT. (Previously, it would have ended
29+
up at the end of the list, after all the capital-letter artists.)
30+
You can turn this new behavior off using the :ref:`sort_case_insensitive`
31+
configuration option. See :ref:`query-sort`. :bug:`1429`
3132
* :doc:`/plugins/fetchart`: There are new settings to control what constitutes
3233
**"acceptable" images**. The `minwidth` option constrains the minimum image
3334
width in pixels and the `enforce_ratio` option requires that images be

0 commit comments

Comments
 (0)