Backup_Repos/beets
1
0
Fork 0
mirror of https://github.com/beetbox/beets.git synced 2026-01-30 20:13:37 +01:00
Code Issues Projects Releases Wiki Activity

Add some more docs to canonicalization with example

Browse source 
It really didn't make sense to me before I did some further research. You shouldn't have to do further research to understand this apart form reading the docs.
This commit is contained in:
Sven-Hendrik Haase 2016-02-06 07:46:31 +01:00
parent 19a5d8c45f
commit 10d44fe526
1 changed files with 10 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
docs/plugins/lastgenre.rst
View file

@ -47,6 +47,16 @@ be turned into coarser-grained ones that are present in the whitelist. This
works using a `tree of nested genre names`_, represented using `YAML`_, where the
leaves of the tree represent the most specific genres.
The most common way to use this would be with a custom whitelist containing only
a desired subset of genres. For example, if the custom whitelist contains `rock`
and `heavy metal` (which is a child node of `rock` in the default genre tree)
then an item that has its genre specified as `viking metal` would actually be
tagged as `heavy metal` because neither `viking metal` nor its parent
`black metal` are in the whitelist. Considering that, it's not very useful to
use the default whitelist (which contains about any genre contained in the tree)
with canonicalization because nothing would ever be matched to a more generic
node since all the specific subgenres are in the whitelist to begin with.
.. _YAML: http://www.yaml.org/
.. _tree of nested genre names: https://raw.githubusercontent.com/beetbox/beets/master/beetsplug/lastgenre/genres-tree.yaml