Maths symbols and unicode-math input inside siunitx commandsUsing dashes with siunitx with pgfplotstableunicode-math/mathspec interferes with siunitxblindtext, unicode-math, and babel won't play nice because of setmathfont (in LyX)Unicode-math and fractionsUnicode-math upright symbolsStrange overfull hboxes with siunitx S column and unicode-mathunicode-math and order of setmath commands“Old” math font commands (mathrm etc.) and unicode-math (“range” option)siunitx and fontspec/unicode-mathsiunitx, input-symbols = ( - ), group-four-digits, group-separator=,
Proof of work - lottery approach
Is there a problem with hiding "forgot password" until it's needed?
How do we know the LHC results are robust?
How do scammers retract money, while you can’t?
How can a function with a hole (removable discontinuity) equal a function with no hole?
How can I kill an app using Terminal?
Customer Requests (Sometimes) Drive Me Bonkers!
when is out of tune ok?
Term for the "extreme-extension" version of a straw man fallacy?
Opposite of a diet
How did Arya survive the stabbing?
Anatomically Correct Strange Women In Ponds Distributing Swords
Is HostGator storing my password in plaintext?
Do the temporary hit points from Reckless Abandon stack if I make multiple attacks on my turn?
Why, precisely, is argon used in neutrino experiments?
How do I go from 300 unfinished/half written blog posts, to published posts?
What is the intuitive meaning of having a linear relationship between the logs of two variables?
Are student evaluations of teaching assistants read by others in the faculty?
Why are there no referendums in the US?
Type int? vs type int
How to write papers efficiently when English isn't my first language?
Closest Prime Number
Why Were Madagascar and New Zealand Discovered So Late?
System.debug(JSON.Serialize(o)) Not longer shows full string
Maths symbols and unicode-math input inside siunitx commands
Using dashes with siunitx with pgfplotstableunicode-math/mathspec interferes with siunitxblindtext, unicode-math, and babel won't play nice because of setmathfont (in LyX)Unicode-math and fractionsUnicode-math upright symbolsStrange overfull hboxes with siunitx S column and unicode-mathunicode-math and order of setmath commands“Old” math font commands (mathrm etc.) and unicode-math (“range” option)siunitx and fontspec/unicode-mathsiunitx, input-symbols = ( - ), group-four-digits, group-separator=,
What I’m trying to do is to input Unicode characters directly inside siunitx commands, like SIrange≳9≈40kilogram. But it does not work and I get errors like ! Package siunitx Error: Invalid token '≳' in numerical input..
Looking further, inputing the standard command for these symbols does not work for all of them either: SIrangegtrsim9approx40kilogram; gtrsim breaks but approx is accepted.
Some MNWE:
documentclassstandalone
usepackagesiunitx
usepackageunicode-math
begindocument
SIrange≳9≈40kilogram\
SIrangegtrsim9approx40kilogram
enddocument
Does what I’m trying to do makes any sense? Is there a way to do that?
siunitx unicode-math
asked Mar 17 at 18:00
ArchangeArchange
877
add a comment |
What I’m trying to do is to input Unicode characters directly inside siunitx commands, like SIrange≳9≈40kilogram. But it does not work and I get errors like ! Package siunitx Error: Invalid token '≳' in numerical input..
Looking further, inputing the standard command for these symbols does not work for all of them either: SIrangegtrsim9approx40kilogram; gtrsim breaks but approx is accepted.
Some MNWE:
documentclassstandalone
usepackagesiunitx
usepackageunicode-math
begindocument
SIrange≳9≈40kilogram\
SIrangegtrsim9approx40kilogram
enddocument
Does what I’m trying to do makes any sense? Is there a way to do that?
siunitx unicode-math
asked Mar 17 at 18:00
ArchangeArchange
877
1
I think the parser needs to know those in advance to support them. It does not handle all symbols by default only common ones. The ones you present here are not really common
– daleif
Mar 17 at 18:11
add a comment |
What I’m trying to do is to input Unicode characters directly inside siunitx commands, like SIrange≳9≈40kilogram. But it does not work and I get errors like ! Package siunitx Error: Invalid token '≳' in numerical input..
Looking further, inputing the standard command for these symbols does not work for all of them either: SIrangegtrsim9approx40kilogram; gtrsim breaks but approx is accepted.
Some MNWE:
documentclassstandalone
usepackagesiunitx
usepackageunicode-math
begindocument
SIrange≳9≈40kilogram\
SIrangegtrsim9approx40kilogram
enddocument
Does what I’m trying to do makes any sense? Is there a way to do that?
siunitx unicode-math
asked Mar 17 at 18:00
ArchangeArchange
877
What I’m trying to do is to input Unicode characters directly inside siunitx commands, like SIrange≳9≈40kilogram. But it does not work and I get errors like ! Package siunitx Error: Invalid token '≳' in numerical input..
Looking further, inputing the standard command for these symbols does not work for all of them either: SIrangegtrsim9approx40kilogram; gtrsim breaks but approx is accepted.
Some MNWE:
documentclassstandalone
usepackagesiunitx
usepackageunicode-math
begindocument
SIrange≳9≈40kilogram\
SIrangegtrsim9approx40kilogram
enddocument
Does what I’m trying to do makes any sense? Is there a way to do that?
siunitx unicode-math
siunitx unicode-math
asked Mar 17 at 18:00
ArchangeArchange
877
asked Mar 17 at 18:00
ArchangeArchange
877
asked Mar 17 at 18:00
ArchangeArchange
877
asked Mar 17 at 18:00
ArchangeArchange
877
asked Mar 17 at 18:00
ArchangeArchange
877
877
1
I think the parser needs to know those in advance to support them. It does not handle all symbols by default only common ones. The ones you present here are not really common
– daleif
Mar 17 at 18:11
add a comment |
1
I think the parser needs to know those in advance to support them. It does not handle all symbols by default only common ones. The ones you present here are not really common
– daleif
Mar 17 at 18:11
1
1
I think the parser needs to know those in advance to support them. It does not handle all symbols by default only common ones. The ones you present here are not really common
– daleif
Mar 17 at 18:11
I think the parser needs to know those in advance to support them. It does not handle all symbols by default only common ones. The ones you present here are not really common
– daleif
Mar 17 at 18:11
add a comment |
2 Answers
2
active
oldest
votes
You can add other comparators to the default list:
documentclassarticle
usepackagesiunitx
usepackageunicode-math
sisetup
input-comparators =
< = > approx ge geq gg le leq ll sim % default
gtrsim ≳ ≈
,
begindocument
SIrange≳9≈40kilogram
SIrangegtrsim9approx40kilogram
enddocument
answered Mar 17 at 21:10
egregegreg
729k8819273240
Awesome, thanks. I guess there are reasons for the initial list being limited to those symbols? Like symbols origins (TeX/LaTeX/amssymb…) for the others or something in that vein?
– Archange
Mar 18 at 15:11
@ArchangeThe author added the most common comparators, I guess.
– egreg
Mar 18 at 15:32
add a comment |
You could set parse-numbers to false to allow arbitrary code in the number fields:
documentclassstandalone
usepackagesiunitx
usepackageunicode-math
begindocument
SIrange[parse-numbers = false]≳9≈40kilogram\
SIrange[parse-numbers = false]gtrsim9approx40kilogram
enddocument
Or, you could declare the symbols explicitly in sisetup:
documentclassstandalone
usepackagesiunitx
sisetup
input-symbols=≈≳gtrsimapprox
usepackageunicode-math
begindocument
SIrange≳9≈40kilogram\
SIrangegtrsim9approx40kilogram
enddocument
answered Mar 17 at 19:15
DG'DG'
11.1k21846
1
parse-numbers=falsehas side effects I would prefer to avoid.input-symbolsis good, butinput-comparatorsfrom @egreg has even better semantical value. ;)
– Archange
Mar 18 at 15:14
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "85"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f479968%2fmaths-symbols-and-unicode-math-input-inside-siunitx-commands%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
You can add other comparators to the default list:
documentclassarticle
usepackagesiunitx
usepackageunicode-math
sisetup
input-comparators =
< = > approx ge geq gg le leq ll sim % default
gtrsim ≳ ≈
,
begindocument
SIrange≳9≈40kilogram
SIrangegtrsim9approx40kilogram
enddocument
answered Mar 17 at 21:10
egregegreg
729k8819273240
Awesome, thanks. I guess there are reasons for the initial list being limited to those symbols? Like symbols origins (TeX/LaTeX/amssymb…) for the others or something in that vein?
– Archange
Mar 18 at 15:11
@ArchangeThe author added the most common comparators, I guess.
– egreg
Mar 18 at 15:32
add a comment |
You can add other comparators to the default list:
documentclassarticle
usepackagesiunitx
usepackageunicode-math
sisetup
input-comparators =
< = > approx ge geq gg le leq ll sim % default
gtrsim ≳ ≈
,
begindocument
SIrange≳9≈40kilogram
SIrangegtrsim9approx40kilogram
enddocument
answered Mar 17 at 21:10
egregegreg
729k8819273240
Awesome, thanks. I guess there are reasons for the initial list being limited to those symbols? Like symbols origins (TeX/LaTeX/amssymb…) for the others or something in that vein?
– Archange
Mar 18 at 15:11
@ArchangeThe author added the most common comparators, I guess.
– egreg
Mar 18 at 15:32
add a comment |
You can add other comparators to the default list:
documentclassarticle
usepackagesiunitx
usepackageunicode-math
sisetup
input-comparators =
< = > approx ge geq gg le leq ll sim % default
gtrsim ≳ ≈
,
begindocument
SIrange≳9≈40kilogram
SIrangegtrsim9approx40kilogram
enddocument
answered Mar 17 at 21:10
egregegreg
729k8819273240
You can add other comparators to the default list:
documentclassarticle
usepackagesiunitx
usepackageunicode-math
sisetup
input-comparators =
< = > approx ge geq gg le leq ll sim % default
gtrsim ≳ ≈
,
begindocument
SIrange≳9≈40kilogram
SIrangegtrsim9approx40kilogram
enddocument
answered Mar 17 at 21:10
egregegreg
729k8819273240
answered Mar 17 at 21:10
egregegreg
729k8819273240
answered Mar 17 at 21:10
egregegreg
729k8819273240
answered Mar 17 at 21:10
egregegreg
729k8819273240
729k8819273240
Awesome, thanks. I guess there are reasons for the initial list being limited to those symbols? Like symbols origins (TeX/LaTeX/amssymb…) for the others or something in that vein?
– Archange
Mar 18 at 15:11
@ArchangeThe author added the most common comparators, I guess.
– egreg
Mar 18 at 15:32
add a comment |
Awesome, thanks. I guess there are reasons for the initial list being limited to those symbols? Like symbols origins (TeX/LaTeX/amssymb…) for the others or something in that vein?
– Archange
Mar 18 at 15:11
@ArchangeThe author added the most common comparators, I guess.
– egreg
Mar 18 at 15:32
Awesome, thanks. I guess there are reasons for the initial list being limited to those symbols? Like symbols origins (TeX/LaTeX/amssymb…) for the others or something in that vein?
– Archange
Mar 18 at 15:11
Awesome, thanks. I guess there are reasons for the initial list being limited to those symbols? Like symbols origins (TeX/LaTeX/amssymb…) for the others or something in that vein?
– Archange
Mar 18 at 15:11
@ArchangeThe author added the most common comparators, I guess.
– egreg
Mar 18 at 15:32
@ArchangeThe author added the most common comparators, I guess.
– egreg
Mar 18 at 15:32
add a comment |
You could set parse-numbers to false to allow arbitrary code in the number fields:
documentclassstandalone
usepackagesiunitx
usepackageunicode-math
begindocument
SIrange[parse-numbers = false]≳9≈40kilogram\
SIrange[parse-numbers = false]gtrsim9approx40kilogram
enddocument
Or, you could declare the symbols explicitly in sisetup:
documentclassstandalone
usepackagesiunitx
sisetup
input-symbols=≈≳gtrsimapprox
usepackageunicode-math
begindocument
SIrange≳9≈40kilogram\
SIrangegtrsim9approx40kilogram
enddocument
answered Mar 17 at 19:15
DG'DG'
11.1k21846
1
parse-numbers=falsehas side effects I would prefer to avoid.input-symbolsis good, butinput-comparatorsfrom @egreg has even better semantical value. ;)
– Archange
Mar 18 at 15:14
add a comment |
You could set parse-numbers to false to allow arbitrary code in the number fields:
documentclassstandalone
usepackagesiunitx
usepackageunicode-math
begindocument
SIrange[parse-numbers = false]≳9≈40kilogram\
SIrange[parse-numbers = false]gtrsim9approx40kilogram
enddocument
Or, you could declare the symbols explicitly in sisetup:
documentclassstandalone
usepackagesiunitx
sisetup
input-symbols=≈≳gtrsimapprox
usepackageunicode-math
begindocument
SIrange≳9≈40kilogram\
SIrangegtrsim9approx40kilogram
enddocument
answered Mar 17 at 19:15
DG'DG'
11.1k21846
1
parse-numbers=falsehas side effects I would prefer to avoid.input-symbolsis good, butinput-comparatorsfrom @egreg has even better semantical value. ;)
– Archange
Mar 18 at 15:14
add a comment |
You could set parse-numbers to false to allow arbitrary code in the number fields:
documentclassstandalone
usepackagesiunitx
usepackageunicode-math
begindocument
SIrange[parse-numbers = false]≳9≈40kilogram\
SIrange[parse-numbers = false]gtrsim9approx40kilogram
enddocument
Or, you could declare the symbols explicitly in sisetup:
documentclassstandalone
usepackagesiunitx
sisetup
input-symbols=≈≳gtrsimapprox
usepackageunicode-math
begindocument
SIrange≳9≈40kilogram\
SIrangegtrsim9approx40kilogram
enddocument
answered Mar 17 at 19:15
DG'DG'
11.1k21846
You could set parse-numbers to false to allow arbitrary code in the number fields:
documentclassstandalone
usepackagesiunitx
usepackageunicode-math
begindocument
SIrange[parse-numbers = false]≳9≈40kilogram\
SIrange[parse-numbers = false]gtrsim9approx40kilogram
enddocument
Or, you could declare the symbols explicitly in sisetup:
documentclassstandalone
usepackagesiunitx
sisetup
input-symbols=≈≳gtrsimapprox
usepackageunicode-math
begindocument
SIrange≳9≈40kilogram\
SIrangegtrsim9approx40kilogram
enddocument
answered Mar 17 at 19:15
DG'DG'
11.1k21846
edited Mar 17 at 20:14
answered Mar 17 at 19:15
DG'DG'
11.1k21846
answered Mar 17 at 19:15
DG'DG'
11.1k21846
answered Mar 17 at 19:15
DG'DG'
11.1k21846
11.1k21846
1
parse-numbers=falsehas side effects I would prefer to avoid.input-symbolsis good, butinput-comparatorsfrom @egreg has even better semantical value. ;)
– Archange
Mar 18 at 15:14
add a comment |
1
parse-numbers=falsehas side effects I would prefer to avoid.input-symbolsis good, butinput-comparatorsfrom @egreg has even better semantical value. ;)
– Archange
Mar 18 at 15:14
1
1
parse-numbers=false has side effects I would prefer to avoid. input-symbols is good, but input-comparators from @egreg has even better semantical value. ;)– Archange
Mar 18 at 15:14
parse-numbers=false has side effects I would prefer to avoid. input-symbols is good, but input-comparators from @egreg has even better semantical value. ;)– Archange
Mar 18 at 15:14
add a comment |
Thanks for contributing an answer to TeX - LaTeX Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f479968%2fmaths-symbols-and-unicode-math-input-inside-siunitx-commands%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
I think the parser needs to know those in advance to support them. It does not handle all symbols by default only common ones. The ones you present here are not really common
– daleif
Mar 17 at 18:11