which mimics the work relationship statement on the MB web site e.g.
`{live} {medley:medley including a} {partial} {instrumental} {cover}
recording of`
It may happen during config option upgrade:
picard.config.ConfigUpgradeError: Error during config upgrade from version 1.3.0dev3 to 1.3.0dev4 using upgrade_to_v1_3_0_dev_4():
Traceback (most recent call last):
File "./picard/config.py", line 141, in run_upgrade_hooks
hook['func'](*hook['args'])
File "./picard/config_upgrade.py", line 137, in upgrade_to_v1_3_0_dev_4
_s[opt] = load_release_type_scores(_s.raw_value(opt))
File "./picard/config_upgrade.py", line 126, in load_release_type_scores
values = setting.split()
AttributeError: 'NoneType' object has no attribute 'split'
Reported in http://tickets.musicbrainz.org/browse/PICARD-592
... based on actual knowledge of how characters are used in practice.
low quotation mark -> normal quotation mark rather than comma
oi should be gha -> gh rather than oi
ideographic punctuation, multiplication / division and middle dot are not punctuation
... whose local knowledge of how characters are actually used identified
more appropriate characters to map to.
soft hyphen -> nothing (since it is invisible)
multiplication -> x rather than * (visually closer)
remove duplicate oe
for punctuation, normalization (merging similar looking characters into
the most common one), accents, and full conversion to ascii.
Functions and tests moved into separate files.
Although more comprehensive, the code should run faster because it
eliminates several loops (inc. a loop with two unicodedata references).
This is intended to form the basis of future PRs to:
a. Clean up (simplify) the file naming code
b. Provide script function(s) for cleaning individual tags / file name
parts
c. Add support for translation / transliteration plugins (which I think
make more sense than being included in Picard itself).
d. Support for converting Tags to ISO-8859-1 rather than ascii (since
that is what is supported by ID3 at least)
e. Possible additional options for allowing / preventing normalization,
possible reorganisation of options to centralise all encoding settings
onto one page rather than metadata, tags and file naming pages at
present (to be discussed).
