DeclareMathDelimiter not working with Unicode fontLuaTeX with unicode-math, how to get the font id of current math fontDifferent appearance of dots, ldots in text and math mode in LuaLaTex + unicode-math (bug)?Font found with XeLaTeX not found with LuaLaTeX on LinuxDefine fallback font for specific Unicode characters in LuaLaTeXWhy does kerning work with LuaLaTex but not XeLaTex for the same font?Rendering a unicode en-dash in XeLaTeXHow do I get the XITS font to work with unicode-math and hepnames in lualatexCopy and paste unicode mathSome LuaTeX unicode characters not workingHow to use the non-unicode glyphs
Did the CIA blow up a Siberian pipeline in 1982?
Counterfeit checks were created for my account. How does this type of fraud work?
What is the most suitable position for a bishop here?
King or Queen-Which piece is which?
How to remove stain from pavement after having dropped sulfuric acid on it?
I found a password with hashcat, but it doesn't work
Is there a term for the belief that "if it's legal, it's moral"?
Are there any individual aliens that have gained superpowers in the Marvel universe?
Is there any proof that high saturation and contrast makes a picture more appealing in social media?
Why don't countries like Japan just print more money?
Extending prime numbers digit by digit while retaining primality
How can a warlock learn from a spellbook?
Designing a magic-compatible polearm
"Correct me if I'm wrong"
Are there examples of rowers who also fought?
Improve appearance of the table in Latex
How could empty set be unique if it could be vacuously false
Why is "Congress shall have power to enforce this article by appropriate legislation" necessary?
How much steel armor can you wear and still be able to swim?
Why is oilcloth made with linseed oil?
What are the pros and cons for the two possible "gear directions" when parking the car on a hill?
Is declining an undergraduate award which causes me discomfort appropriate?
Umlaut character order when sorting
What does this Swiss black on yellow rectangular traffic sign with a symbol looking like a dart mean?
DeclareMathDelimiter not working with Unicode font
LuaTeX with unicode-math, how to get the font id of current math fontDifferent appearance of dots, ldots in text and math mode in LuaLaTex + unicode-math (bug)?Font found with XeLaTeX not found with LuaLaTeX on LinuxDefine fallback font for specific Unicode characters in LuaLaTeXWhy does kerning work with LuaLaTex but not XeLaTex for the same font?Rendering a unicode en-dash in XeLaTeXHow do I get the XITS font to work with unicode-math and hepnames in lualatexCopy and paste unicode mathSome LuaTeX unicode characters not workingHow to use the non-unicode glyphs
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
I am unable to get DeclareMathDelimiter to work correctly with a Unicode font. I get the same results with XeLaTex and LuaLaTex. The custom font has a MATH table defined with both size variants and stretchy parts defined. Here is the example code
documentclass[10pt,fleqn]amsart
usepackagefontspec
usepackageunicode-math
setmainfontSTIX Two Text
setmathfontSTIX Two Math
newfontface logix Logix.otf[Scale=1.0,NFSSFamily=logix]
DeclareSymbolFontLogixTUlogixmn
DeclareMathDelimiterOpnGrpXmathopen Logix"E301 Logix"EBE0
DeclareMathDelimiterClsGrpXmathclose Logix"E341 Logix"EBF0
begindocument
[ leftOpnGrpX frac12 rightClsGrpX ]
enddocument
and here is the generated output
luatex unicode delimiters
add a comment |
I am unable to get DeclareMathDelimiter to work correctly with a Unicode font. I get the same results with XeLaTex and LuaLaTex. The custom font has a MATH table defined with both size variants and stretchy parts defined. Here is the example code
documentclass[10pt,fleqn]amsart
usepackagefontspec
usepackageunicode-math
setmainfontSTIX Two Text
setmathfontSTIX Two Math
newfontface logix Logix.otf[Scale=1.0,NFSSFamily=logix]
DeclareSymbolFontLogixTUlogixmn
DeclareMathDelimiterOpnGrpXmathopen Logix"E301 Logix"EBE0
DeclareMathDelimiterClsGrpXmathclose Logix"E341 Logix"EBF0
begindocument
[ leftOpnGrpX frac12 rightClsGrpX ]
enddocument
and here is the generated output
luatex unicode delimiters
add a comment |
I am unable to get DeclareMathDelimiter to work correctly with a Unicode font. I get the same results with XeLaTex and LuaLaTex. The custom font has a MATH table defined with both size variants and stretchy parts defined. Here is the example code
documentclass[10pt,fleqn]amsart
usepackagefontspec
usepackageunicode-math
setmainfontSTIX Two Text
setmathfontSTIX Two Math
newfontface logix Logix.otf[Scale=1.0,NFSSFamily=logix]
DeclareSymbolFontLogixTUlogixmn
DeclareMathDelimiterOpnGrpXmathopen Logix"E301 Logix"EBE0
DeclareMathDelimiterClsGrpXmathclose Logix"E341 Logix"EBF0
begindocument
[ leftOpnGrpX frac12 rightClsGrpX ]
enddocument
and here is the generated output
luatex unicode delimiters
I am unable to get DeclareMathDelimiter to work correctly with a Unicode font. I get the same results with XeLaTex and LuaLaTex. The custom font has a MATH table defined with both size variants and stretchy parts defined. Here is the example code
documentclass[10pt,fleqn]amsart
usepackagefontspec
usepackageunicode-math
setmainfontSTIX Two Text
setmathfontSTIX Two Math
newfontface logix Logix.otf[Scale=1.0,NFSSFamily=logix]
DeclareSymbolFontLogixTUlogixmn
DeclareMathDelimiterOpnGrpXmathopen Logix"E301 Logix"EBE0
DeclareMathDelimiterClsGrpXmathclose Logix"E341 Logix"EBF0
begindocument
[ leftOpnGrpX frac12 rightClsGrpX ]
enddocument
and here is the generated output
luatex unicode delimiters
luatex unicode delimiters
asked Jun 3 at 0:12
Michael Lee FinneyMichael Lee Finney
1327
1327
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
DeclareMathDelimiter
uses the traditional TeX primitives delcode
or delimiter
. These accept a compact bitmap encoding both codepoints and the symbol families. This format only accepts codepoints up to 255, every else leads to odd behaviour because the additional digits leak into other fields of the bitmap.
So both XeTeX and LuaTeX support separate primitives for delimiters with higher codepoints: Udelcode
and Udelimiter
.
These only take a single codepoint, so instead of E301
and EBE0
, you only pass E301
. It is the responsibility of the font to add EBE0
to the linked list of bigger variants.
Then you get e.g.
documentclass[10pt,fleqn]amsart
usepackagefontspec
usepackageunicode-math
setmainfontSTIX Two Text
setmathfontSTIX Two Math
newfontface logix Logix.otf[Scale=1.0,NFSSFamily=logix]
DeclareSymbolFontLogixTUlogixmn
makeatletter
xdefOpnGrpXUdelimitermathchar@typemathopensymLogix"E301
xdefClsGrpXUdelimitermathchar@typemathclosesymLogix"E341
makeatother
begindocument
[ leftOpnGrpX frac12 rightClsGrpX ]
enddocument
Udelcode
could be used if you do not create a control sequence like OpnGrpX
, but want to make a character directly usable as a delimiter like (
or [
. For example, if you want [
and ]
to use your new glyphs iff they are used after left
, right
or similar, you could use
documentclass[10pt,fleqn]amsart
usepackagefontspec
usepackageunicode-math
setmainfontSTIX Two Text
setmathfontSTIX Two Math
newfontface logix Logix.otf[Scale=1.0,NFSSFamily=logix]
DeclareSymbolFontLogixTUlogixmn
Udelcode`[symLogix"E301
Udelcode`]symLogix"E341
begindocument
[ left[ frac12 right] ] -- Now uses the Logix glyphs
enddocument
You could also e.g. use Udelcode"E301symLogix"E301
to be able to type the Unicode character U+E301 after left
/right
directly.
(I would add a screenshot, but I would need the font first...)
Thank you! That worked perfectly. When would I use Udelcode?
– Michael Lee Finney
Jun 3 at 2:54
@MichaelLeeFinney I added something about that. It is used if you would have only passed a single character toDeclareMathDelimiter
– Marcel Krüger
Jun 3 at 8:11
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%2f493885%2fdeclaremathdelimiter-not-working-with-unicode-font%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
DeclareMathDelimiter
uses the traditional TeX primitives delcode
or delimiter
. These accept a compact bitmap encoding both codepoints and the symbol families. This format only accepts codepoints up to 255, every else leads to odd behaviour because the additional digits leak into other fields of the bitmap.
So both XeTeX and LuaTeX support separate primitives for delimiters with higher codepoints: Udelcode
and Udelimiter
.
These only take a single codepoint, so instead of E301
and EBE0
, you only pass E301
. It is the responsibility of the font to add EBE0
to the linked list of bigger variants.
Then you get e.g.
documentclass[10pt,fleqn]amsart
usepackagefontspec
usepackageunicode-math
setmainfontSTIX Two Text
setmathfontSTIX Two Math
newfontface logix Logix.otf[Scale=1.0,NFSSFamily=logix]
DeclareSymbolFontLogixTUlogixmn
makeatletter
xdefOpnGrpXUdelimitermathchar@typemathopensymLogix"E301
xdefClsGrpXUdelimitermathchar@typemathclosesymLogix"E341
makeatother
begindocument
[ leftOpnGrpX frac12 rightClsGrpX ]
enddocument
Udelcode
could be used if you do not create a control sequence like OpnGrpX
, but want to make a character directly usable as a delimiter like (
or [
. For example, if you want [
and ]
to use your new glyphs iff they are used after left
, right
or similar, you could use
documentclass[10pt,fleqn]amsart
usepackagefontspec
usepackageunicode-math
setmainfontSTIX Two Text
setmathfontSTIX Two Math
newfontface logix Logix.otf[Scale=1.0,NFSSFamily=logix]
DeclareSymbolFontLogixTUlogixmn
Udelcode`[symLogix"E301
Udelcode`]symLogix"E341
begindocument
[ left[ frac12 right] ] -- Now uses the Logix glyphs
enddocument
You could also e.g. use Udelcode"E301symLogix"E301
to be able to type the Unicode character U+E301 after left
/right
directly.
(I would add a screenshot, but I would need the font first...)
Thank you! That worked perfectly. When would I use Udelcode?
– Michael Lee Finney
Jun 3 at 2:54
@MichaelLeeFinney I added something about that. It is used if you would have only passed a single character toDeclareMathDelimiter
– Marcel Krüger
Jun 3 at 8:11
add a comment |
DeclareMathDelimiter
uses the traditional TeX primitives delcode
or delimiter
. These accept a compact bitmap encoding both codepoints and the symbol families. This format only accepts codepoints up to 255, every else leads to odd behaviour because the additional digits leak into other fields of the bitmap.
So both XeTeX and LuaTeX support separate primitives for delimiters with higher codepoints: Udelcode
and Udelimiter
.
These only take a single codepoint, so instead of E301
and EBE0
, you only pass E301
. It is the responsibility of the font to add EBE0
to the linked list of bigger variants.
Then you get e.g.
documentclass[10pt,fleqn]amsart
usepackagefontspec
usepackageunicode-math
setmainfontSTIX Two Text
setmathfontSTIX Two Math
newfontface logix Logix.otf[Scale=1.0,NFSSFamily=logix]
DeclareSymbolFontLogixTUlogixmn
makeatletter
xdefOpnGrpXUdelimitermathchar@typemathopensymLogix"E301
xdefClsGrpXUdelimitermathchar@typemathclosesymLogix"E341
makeatother
begindocument
[ leftOpnGrpX frac12 rightClsGrpX ]
enddocument
Udelcode
could be used if you do not create a control sequence like OpnGrpX
, but want to make a character directly usable as a delimiter like (
or [
. For example, if you want [
and ]
to use your new glyphs iff they are used after left
, right
or similar, you could use
documentclass[10pt,fleqn]amsart
usepackagefontspec
usepackageunicode-math
setmainfontSTIX Two Text
setmathfontSTIX Two Math
newfontface logix Logix.otf[Scale=1.0,NFSSFamily=logix]
DeclareSymbolFontLogixTUlogixmn
Udelcode`[symLogix"E301
Udelcode`]symLogix"E341
begindocument
[ left[ frac12 right] ] -- Now uses the Logix glyphs
enddocument
You could also e.g. use Udelcode"E301symLogix"E301
to be able to type the Unicode character U+E301 after left
/right
directly.
(I would add a screenshot, but I would need the font first...)
Thank you! That worked perfectly. When would I use Udelcode?
– Michael Lee Finney
Jun 3 at 2:54
@MichaelLeeFinney I added something about that. It is used if you would have only passed a single character toDeclareMathDelimiter
– Marcel Krüger
Jun 3 at 8:11
add a comment |
DeclareMathDelimiter
uses the traditional TeX primitives delcode
or delimiter
. These accept a compact bitmap encoding both codepoints and the symbol families. This format only accepts codepoints up to 255, every else leads to odd behaviour because the additional digits leak into other fields of the bitmap.
So both XeTeX and LuaTeX support separate primitives for delimiters with higher codepoints: Udelcode
and Udelimiter
.
These only take a single codepoint, so instead of E301
and EBE0
, you only pass E301
. It is the responsibility of the font to add EBE0
to the linked list of bigger variants.
Then you get e.g.
documentclass[10pt,fleqn]amsart
usepackagefontspec
usepackageunicode-math
setmainfontSTIX Two Text
setmathfontSTIX Two Math
newfontface logix Logix.otf[Scale=1.0,NFSSFamily=logix]
DeclareSymbolFontLogixTUlogixmn
makeatletter
xdefOpnGrpXUdelimitermathchar@typemathopensymLogix"E301
xdefClsGrpXUdelimitermathchar@typemathclosesymLogix"E341
makeatother
begindocument
[ leftOpnGrpX frac12 rightClsGrpX ]
enddocument
Udelcode
could be used if you do not create a control sequence like OpnGrpX
, but want to make a character directly usable as a delimiter like (
or [
. For example, if you want [
and ]
to use your new glyphs iff they are used after left
, right
or similar, you could use
documentclass[10pt,fleqn]amsart
usepackagefontspec
usepackageunicode-math
setmainfontSTIX Two Text
setmathfontSTIX Two Math
newfontface logix Logix.otf[Scale=1.0,NFSSFamily=logix]
DeclareSymbolFontLogixTUlogixmn
Udelcode`[symLogix"E301
Udelcode`]symLogix"E341
begindocument
[ left[ frac12 right] ] -- Now uses the Logix glyphs
enddocument
You could also e.g. use Udelcode"E301symLogix"E301
to be able to type the Unicode character U+E301 after left
/right
directly.
(I would add a screenshot, but I would need the font first...)
DeclareMathDelimiter
uses the traditional TeX primitives delcode
or delimiter
. These accept a compact bitmap encoding both codepoints and the symbol families. This format only accepts codepoints up to 255, every else leads to odd behaviour because the additional digits leak into other fields of the bitmap.
So both XeTeX and LuaTeX support separate primitives for delimiters with higher codepoints: Udelcode
and Udelimiter
.
These only take a single codepoint, so instead of E301
and EBE0
, you only pass E301
. It is the responsibility of the font to add EBE0
to the linked list of bigger variants.
Then you get e.g.
documentclass[10pt,fleqn]amsart
usepackagefontspec
usepackageunicode-math
setmainfontSTIX Two Text
setmathfontSTIX Two Math
newfontface logix Logix.otf[Scale=1.0,NFSSFamily=logix]
DeclareSymbolFontLogixTUlogixmn
makeatletter
xdefOpnGrpXUdelimitermathchar@typemathopensymLogix"E301
xdefClsGrpXUdelimitermathchar@typemathclosesymLogix"E341
makeatother
begindocument
[ leftOpnGrpX frac12 rightClsGrpX ]
enddocument
Udelcode
could be used if you do not create a control sequence like OpnGrpX
, but want to make a character directly usable as a delimiter like (
or [
. For example, if you want [
and ]
to use your new glyphs iff they are used after left
, right
or similar, you could use
documentclass[10pt,fleqn]amsart
usepackagefontspec
usepackageunicode-math
setmainfontSTIX Two Text
setmathfontSTIX Two Math
newfontface logix Logix.otf[Scale=1.0,NFSSFamily=logix]
DeclareSymbolFontLogixTUlogixmn
Udelcode`[symLogix"E301
Udelcode`]symLogix"E341
begindocument
[ left[ frac12 right] ] -- Now uses the Logix glyphs
enddocument
You could also e.g. use Udelcode"E301symLogix"E301
to be able to type the Unicode character U+E301 after left
/right
directly.
(I would add a screenshot, but I would need the font first...)
edited Jun 3 at 8:10
answered Jun 3 at 1:32
Marcel KrügerMarcel Krüger
13.9k11636
13.9k11636
Thank you! That worked perfectly. When would I use Udelcode?
– Michael Lee Finney
Jun 3 at 2:54
@MichaelLeeFinney I added something about that. It is used if you would have only passed a single character toDeclareMathDelimiter
– Marcel Krüger
Jun 3 at 8:11
add a comment |
Thank you! That worked perfectly. When would I use Udelcode?
– Michael Lee Finney
Jun 3 at 2:54
@MichaelLeeFinney I added something about that. It is used if you would have only passed a single character toDeclareMathDelimiter
– Marcel Krüger
Jun 3 at 8:11
Thank you! That worked perfectly. When would I use Udelcode?
– Michael Lee Finney
Jun 3 at 2:54
Thank you! That worked perfectly. When would I use Udelcode?
– Michael Lee Finney
Jun 3 at 2:54
@MichaelLeeFinney I added something about that. It is used if you would have only passed a single character to
DeclareMathDelimiter
– Marcel Krüger
Jun 3 at 8:11
@MichaelLeeFinney I added something about that. It is used if you would have only passed a single character to
DeclareMathDelimiter
– Marcel Krüger
Jun 3 at 8:11
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%2f493885%2fdeclaremathdelimiter-not-working-with-unicode-font%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