Consider making task list `[ ]` more aligned with spec (not allow Unicode spaces)
The GFM spec indicates that only a normal space, not unicode spaces such as
- [ ] NO-BREAK SPACE (U+00A0)
- [ ] FIGURE SPACE (U+2007)
- [ ] NARROW NO-BREAK SPACE (U+202F)
- [ ] THIN SPACE (U+2009)
- [ ] normal SPACE (U+0020)
should be supported. However our task parsing code allows it (see https://github.com/deckar01/task_list/commit/dd204f94887103a2190dc075ee86e92fb15b5fe9).
!80674 (merged) fixes the problem where we couldn't check boxes that contained these unicode spaces.
Let's consider whether it makes sense to remove support for the Unicode spaces. Some reasoning is outlines here
This also indicates a reason why this happens in the first place:
It depends on the keyboard layout. When I use a Mac Belgian AZERTY, I type the
[
using ALT+SHIFT+(, then the space. Sometimes, I keep the ALT key pressed a little longer and it type a non-breaking space instead.