Skip to content

Commit 3c50c2d

Browse files
committed
space
1 parent 5a994e4 commit 3c50c2d

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

chapters/1.Preprocessing/02_normalization.qmd

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ Just as a gardener would prune dead branches, enrich the soil, and care for the
1616
The main goal of normalization is to remove irrelevant content and standardize the data in order to reduce noise. Below are some key actions we’ll be performing during this workshop:
1717

1818
| Action | Why it matters? |
19-
|-------------|-----------------------------------------------------------|
19+
|------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
2020
| Remove URLs | URLs often contain irrelevant noise and don't contribute meaningful content for analysis. |
2121
| Remove Punctuation & Symbols | Punctuation marks and other symbols including those extensively used in social media for mentioning (\@) or tagging (#) rarely adds value in most NLP tasks and can interfere with tokenization (as we will cover in a bit) or word matching. |
2222
| Remove Numbers | Numbers can be noise in most contexts unless specifically relevant (e.g., in financial or medical texts) don't contribute much to the analysis. However, in NLP tasks they are considered important, there might be considerations to replace them with dummy tokens (e.g. \<NUMBER\>), or even converting them into their written form (e.g, 100 becomes one hundred). |
@@ -143,7 +143,7 @@ Now that we have normalized variations of apostrophes, we can properly handle co
143143
So, while it may seem like a small step, it often leads to cleaner data, leaner models, and more accurate results. First, however, we need to ensure that apostrophes are handled correctly. It's not uncommon to encounter messy text where nonstandard characters are used in place of the straight apostrophe ('). Such inconsistencies are very common and can disrupt contraction expansion.
144144

145145
| Character | Unicode | Notes |
146-
|-------------|-------------|----------------------------------------------|
146+
|-----------|---------|---------------------------------------------------------|
147147
| `'` | U+0027 | Standard straight apostrophe, used in most dictionaries |
148148
| `` | U+2019 | Right single quotation mark (curly apostrophe) |
149149
| `` | U+2018 | Left single quotation mark |

0 commit comments

Comments
 (0)