<commit_before><commit_msg>Added preliminary doc about releases parsing<commit_after>One of the key points of this application is the parsing of everything into Releases.

A Release object contains semantic information, build from the release's name. This is meant to make it easy to
determine compatibility of Subs with Episodes.

# Type

## Episodes

## Subtitles
As most sources use their own naming, subtitles parsing depends on the source.

## Matching
Subtitle and Episode Releases are meant to be Matched for Compatibility.

### Multi-target subtitles
It is quite common that subtitles will be compatible across releases, usually when the same source was used.

One key difficulty is that some names mixup information. For instance, the Subtitle Release
`The Simpsons.S24E17.What Animated Women Want.LOL.720p` says Group LOL, but Resolution 720p. LOL only does 480p
releases. This would mean that this Subtitle was written for the LOL Episode Release, but also works for the 720p one
(whoever Released it).

This particular use-case is not implemented yet.

**Possible solution**

One way would be to create two Subtitle Release objects, one with
`group` set to `lol` + resolution `480p` (lol only does 480p), and the other with `resolution` set to `720p`, and the
group unset.
{'fraction_non_alphanumeric': 0.050623052959501556, 'fraction_numerical': 0.019470404984423675, 'mean_word_length': 4.762331838565022, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 4, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '1331689', 'n_tokens_mistral': 370, 'n_tokens_neox': 333, 'n_words': 189}