Skip to content
New issue

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

Tilde as non-breaking space before cite breaks detection #140

Closed
bratekarate opened this issue Sep 18, 2020 · 1 comment
Closed

Tilde as non-breaking space before cite breaks detection #140

bratekarate opened this issue Sep 18, 2020 · 1 comment
Labels
bug Something isn't working
Milestone

Comments

@bratekarate
Copy link
Contributor

Consider the following stylistically problematic sentence:

As discussed by \cite{Source}, it could be argued...

Unless \textcite is used, textidote issues a warning. However, chktex complains about the whitespace before \cite and suggests to replace it with a non-breaking ~.

As discussed by~\cite{Source}, it could be argued...

This change to satisfy chktex will cause textidote to ignore the error, which seems to be undesired behaviour.

@sylvainhalle sylvainhalle added the bug Something isn't working label Sep 21, 2020
@sylvainhalle sylvainhalle added this to the v0.8.2 milestone Sep 21, 2020
@bratekarate
Copy link
Contributor Author

Apparently \textcite does not resolve the issue in the way I thought it does. It seems as though the biblatex commands like \parencite and \textcite are not recognized. Is it planned to include them in the check as well? E.g. allow only the following citation macros in-text:

  • \textcite
  • \citeauthor(*)
  • \citetitle (not common for citations, but could be used in-text in some cases)

Issue a warning for all other \cite variations. Maybe it's more complicated than it seems though.

sylvainhalle added a commit that referenced this issue Mar 31, 2021
Correctly handling the tilde (#160) solves #140 at the same time
sylvainhalle added a commit that referenced this issue Mar 31, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants