feat: allow blank lines and comments in dictionary.dict
#756
Conversation
Fails on `lints_lots_of_latin_correctly` due to the dictionary containing `et al.` around line 49,839 as the sole dictionary entry containing a space. Is that actually intentional and supported? This version would support comments after any whitespace following a dictionary entry with its affix annotation on the same line. If we do need to support words with spaces then I'll redesign this to require a comment delimiter.
|
Personally, I think a comment delimiter would be a good idea regardless. Results in much less ambiguity. For example, if someone opens the dictionary and sees |
Yes I'm seeking clarification on the issue of terms with spaces. In tests I found I can add them arbitrarily but I can't get them suggested unless I use the term with the spaces removed, and optional some other characters removed, but not with the space in the wrong place, etc. There are tons of terms to add if this is going to be a thing. Only problem with the delimiter is it can also be ambiguous in that it can look like a an annotation flag. I've also started a syntax highlighter so that would also make the comments stand out. The idea is there would be a bunch of whitespace, not just one, at least locally aligned. Which is not to say I'm closed to the idea of a delimiter (-: |
Description
This version would support comments after any whitespace following a dictionary entry with its affix annotation on the same line.
If we do need to support words with spaces then I'll redesign this to require a comment delimiter.
How Has This Been Tested?
Fails on
lints_lots_of_latin_correctlydue to the dictionary containinget al.around line 49,839 as the sole dictionary entry containing a space.Is that actually intentional and supported?
Checklist