The grammar check tools are not working properly for the Brazilian Portuguese dictionary of the Writer when I use the resources for tracking changes. When we hide the changes (with the "tracking changes" option enabled, the tool still takes the hidden characters into account when pointing out which words are mispelled. Sorry if I'm not using the correct name of the features. That's because I use the translated version.
Steps to Reproduce:
1.With "Brazilian Portuguese" selected as the default language, write the word "cerrto".
2. Enable the "Record Changes" function and erase one of the "r".
3. Disable "Show Track Changes".
Though the word is now correct ("certo"), it will be underlined in red, because the Writer still takes the erased "r" into account.
The word "certo" should not be underlined, because it's a common word from Brazilian Portuguese.
User Profile Reset: Yes
OpenGL enabled: Yes
I use the tiles interface ("Em abas"), that looks similar to Word interface, but I believe I experienced the trouble also with the standard interface.
Version: 22.214.171.124 (x64)
Build ID: 8349ace3c3162073abd90d81fd06dcfb6b36b994
CPU threads: 4; OS: Windows 10.0 Build 19041; UI render: Skia/Raster; VCL: win
Locale: pt-BR (pt_BR); Interface: pt-BR
This is likely not specific to Brazilian Portuguese linguistic tools. The track change feature is known to interfere with spellcheckers, see bug 66043.
So this may be a duplicate, I haven't read both bug reports carefully enough to decide.
Dear Márcio Sena,
A new major release of LibreOffice is available since this bug was reported.
Could you please try to reproduce it with the latest version of LibreOffice
from https://www.libreoffice.org/download/libreoffice-fresh/ ?
I have set the bug's status to 'NEEDINFO'. Please change it back to
'UNCONFIRMED' if the bug is still present in the latest version.
The track change and spell check are working correctly in the latest version. Thank you very much.
(In reply to Márcio Sena from comment #3)
> The track change and spell check are working correctly in the latest
> version. Thank you very much.
Great, let's close this bug then. Thanks for the feedback.