We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
For some macros (only observed with \parencite so far), optional arguments in brackets cause false positives in the LanguageTool checks. Example:
\parencite
\parencite{source} yields no errors. \parencite[p. 12-24]{source} yields:
\parencite{source}
\parencite[p. 12-24]{source}
--(L8C704-L8C713): Possible spelling mistake found. Suggestions: [parents, parent, precise, parasite, parentage, parenting, recite, Prentice, Principe, parented, parricide, partite, perennate, martensite, pargasite, potentite, variscite] (729)
... I like the parasite suggestion though. They should add that macro to latex :)
Use command line argument (or config file) --remove-macros parencite (thanks for adding this flag, great for such cases!)
--remove-macros parencite
The text was updated successfully, but these errors were encountered:
The culprit is
textidote/Source/Core/src/ca/uqac/lif/textidote/cleaning/latex/LatexCleaner.java
Line 382 in ba5694c
Sorry, something went wrong.
As a matter of fact, parencite should be handled like other cite commands, so the fix is not where I said it should be
parencite
cite
6026bea
No branches or pull requests
Bug Description
For some macros (only observed with
\parencite
so far), optional arguments in brackets cause false positives in the LanguageTool checks. Example:\parencite{source}
yields no errors.\parencite[p. 12-24]{source}
yields:... I like the parasite suggestion though. They should add that macro to latex :)
Temporary workaround
Use command line argument (or config file)
--remove-macros parencite
(thanks for adding this flag, great for such cases!)The text was updated successfully, but these errors were encountered: