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

siunitx issues #134

Closed
cl0rm opened this issue Dec 16, 2021 · 1 comment
Closed

siunitx issues #134

cl0rm opened this issue Dec 16, 2021 · 1 comment
Assignees
Labels
1-bug 🐛 Issue type: Bug report (something isn't working as expected) 2-confirmed Issue status: Confirmed, reproducible bug in LTeX 3-fixed Issue resolution: Issue has been fixed on the develop branch
Milestone

Comments

@cl0rm
Copy link

cl0rm commented Dec 16, 2021

when using siunitx, the parser does somehow not work:

an example to reproduce this is the following German sentence

Die Eingangsspannung wird mit einem Flyback - Konverter von ca. \SI{12}{\volt} auf \SI{4,2}{\volt}, die Ladespannung der Batterie, angehoben.

the second \SI generates issues (COMMA_PARENTHESIS_WHITESPACE)

@cl0rm cl0rm added 1-bug 🐛 Issue type: Bug report (something isn't working as expected) 2-unconfirmed Issue status: Bug that needs to be reproduced (all new bugs have this label) labels Dec 16, 2021
@cl0rm cl0rm changed the title siunitx support siunitx issues Dec 16, 2021
@valentjn valentjn added 2-confirmed Issue status: Confirmed, reproducible bug in LTeX and removed 2-unconfirmed Issue status: Bug that needs to be reproduced (all new bugs have this label) labels Dec 16, 2021
@valentjn valentjn added this to LTeX Dec 16, 2021
@valentjn valentjn moved this to ✋ To Do in LTeX Dec 16, 2021
Repository owner moved this from ✋ To Do to 🎉 Done in LTeX Dec 18, 2021
@valentjn valentjn self-assigned this Dec 18, 2021
@valentjn valentjn added the 3-fixed Issue resolution: Issue has been fixed on the develop branch label Dec 18, 2021
@valentjn valentjn added this to the 15.3.0 milestone Dec 18, 2021
@github-actions
Copy link

This issue is now fixed on develop. The fix will be included in the next release of LTEX.

If you don't want to wait, you can try out the nightly pre-release tomorrow. Nightly pre-releases are published every morning at around 4am UTC.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1-bug 🐛 Issue type: Bug report (something isn't working as expected) 2-confirmed Issue status: Confirmed, reproducible bug in LTeX 3-fixed Issue resolution: Issue has been fixed on the develop branch
Projects
Status: 🎉 Done
Development

No branches or pull requests

2 participants