Bug: incorrect/spurious transformation être → êtree.

[lebigot]

Describe the Bug

When a text contains "être", this word is transformed into "êtree", which is incorrect (in French).

How to Reproduce

Steps to reproduce the behavior:

0. Make sure that "Auto-correct common misspellings" is On in the Linter settings.
1. Type "être" in a note.
2. Launch the linter.

Expected Behavior

The word "être" should instead not be touched.

Device

• Desktop
• Mobile not tested

[pjkaufman]

Hey @lebigot , is there a reason not to add that value to the ignore list? English is the only language that the auto fix is really designed for. So for French words that may be the case, but when used in English it may not be the same (assuming that is even a thing). However if that is a French word and the English usage is spelled as you suggest, that should probably be bubbled up to the codespell maintainers to get it fixed there as well.

[pjkaufman]

I have not heard anything about this. in about 2 weeks. If I do not hear anything else by Sunday, I will close this issue since I am not able to validate the claim here on my own with the information provided.

[lebigot]

There is a reason to not add "être" to the ignore list: there is no valid reason for it to be transformed into "êtree" anyway, be it in French or English, where "êtree" doesn't exist, and obviously fixing this at the source is obviously more useful for everybody. :)

Now, codespell 2.2.4 (the latest version) doesn't run into this problem.

Maybe the bug comes from a previous version of codespell? Maybe it is somewhere in linter? Maybe it's a wild guess, but maybe linter somehow doesn't recognize the "ê" and codespell (via linter, not called directly through codespell 2.2.4) applies its rule "tre" → "tree", resulting in "être" being transformed into "êtree", which is not correct?

[pjkaufman]

This may be a bug in the Linter where that rule you suggested may be getting applied. Let me see if it gets modified in a UT and move forward from there. The possibility you suggested could be the case. I wonder if python has a different default set for regex which could cause the issue in question.

[pjkaufman]

Looks like I have a fix for this. Thanks for taking a look at codespell and verifying it was not in the list @lebigot !

[pjkaufman]

The change should go out with the next release.

[lebigot]

Great, thanks!