2017-06-03 18:27:05 +00:00
|
|
|
|
# coding: utf8
|
|
|
|
|
from __future__ import unicode_literals
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
# These exceptions are used to add NORM values based on a token's ORTH value.
|
|
|
|
|
# Individual languages can also add their own exceptions and overwrite them -
|
|
|
|
|
# for example, British vs. American spelling in English.
|
|
|
|
|
|
|
|
|
|
# Norms are only set if no alternative is provided in the tokenizer exceptions.
|
|
|
|
|
# Note that this does not change any other token attributes. Its main purpose
|
|
|
|
|
# is to normalise the word representations so that equivalent tokens receive
|
|
|
|
|
# similar representations. For example: $ and € are very different, but they're
|
|
|
|
|
# both currency symbols. By normalising currency symbols to $, all symbols are
|
|
|
|
|
# seen as similar, no matter how common they are in the training data.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
BASE_NORMS = {
|
|
|
|
|
"'s": "'s",
|
|
|
|
|
"'S": "'s",
|
|
|
|
|
"’s": "'s",
|
|
|
|
|
"’S": "'s",
|
|
|
|
|
"’": "'",
|
|
|
|
|
"‘": "'",
|
|
|
|
|
"´": "'",
|
|
|
|
|
"`": "'",
|
|
|
|
|
"”": '"',
|
|
|
|
|
"“": '"',
|
|
|
|
|
"''": '"',
|
|
|
|
|
"``": '"',
|
|
|
|
|
"´´": '"',
|
|
|
|
|
"„": '"',
|
|
|
|
|
"»": '"',
|
|
|
|
|
"«": '"',
|
2017-10-14 12:58:52 +00:00
|
|
|
|
"‘‘": '"',
|
|
|
|
|
"’’": '"',
|
|
|
|
|
"?": "?",
|
|
|
|
|
"!": "!",
|
|
|
|
|
",": ",",
|
|
|
|
|
";": ";",
|
|
|
|
|
":": ":",
|
|
|
|
|
"。": ".",
|
|
|
|
|
"।": ".",
|
2017-06-03 18:27:05 +00:00
|
|
|
|
"…": "...",
|
|
|
|
|
"—": "-",
|
|
|
|
|
"–": "-",
|
|
|
|
|
"--": "-",
|
|
|
|
|
"---": "-",
|
2017-10-14 12:58:52 +00:00
|
|
|
|
"——": "-",
|
2017-06-03 18:27:05 +00:00
|
|
|
|
"€": "$",
|
|
|
|
|
"£": "$",
|
|
|
|
|
"¥": "$",
|
|
|
|
|
"฿": "$",
|
|
|
|
|
"US$": "$",
|
|
|
|
|
"C$": "$",
|
💫 Tidy up and auto-format .py files (#2983)
<!--- Provide a general summary of your changes in the title. -->
## Description
- [x] Use [`black`](https://github.com/ambv/black) to auto-format all `.py` files.
- [x] Update flake8 config to exclude very large files (lemmatization tables etc.)
- [x] Update code to be compatible with flake8 rules
- [x] Fix various small bugs, inconsistencies and messy stuff in the language data
- [x] Update docs to explain new code style (`black`, `flake8`, when to use `# fmt: off` and `# fmt: on` and what `# noqa` means)
Once #2932 is merged, which auto-formats and tidies up the CLI, we'll be able to run `flake8 spacy` actually get meaningful results.
At the moment, the code style and linting isn't applied automatically, but I'm hoping that the new [GitHub Actions](https://github.com/features/actions) will let us auto-format pull requests and post comments with relevant linting information.
### Types of change
enhancement, code style
## Checklist
<!--- Before you submit the PR, go over this checklist and make sure you can
tick off all the boxes. [] -> [x] -->
- [x] I have submitted the spaCy Contributor Agreement.
- [x] I ran the tests, and all new and existing tests passed.
- [x] My changes don't require a change to the documentation, or if they do, I've added all required information.
2018-11-30 16:03:03 +00:00
|
|
|
|
"A$": "$",
|
2019-04-11 09:32:28 +00:00
|
|
|
|
"₺" : "$",
|
2017-06-03 18:27:05 +00:00
|
|
|
|
}
|