Kerning for subscripts of sigma? The 2019 Stack Overflow Developer Survey Results Are InSubscript kerning for specific letters in XeLaTeXMargin kerning in Xe(La)TeX for TeXlive 2010: how to enable?Fix math mode kerning of “C”Turning off TeXnical enhancementsKerning of subscriptsPair kerning strategies in (pdf)LaTeXKerning super- and subscripts “semantically”Subscript kerning for specific letters in XeLaTeXMicrotype kerning won't work with quotationmarksKerning of HyphensIs there a LuaLaTeX solution to adjust superscript kerning on large delimiters?

Why couldn't they take pictures of a closer black hole?

Is bread bad for ducks?

Why are there uneven bright areas in this photo of black hole?

If a sorcerer casts the Banishment spell on a PC while in Avernus, does the PC return to their home plane?

Will it cause any balance problems to have PCs level up and gain the benefits of a long rest mid-fight?

Cooking pasta in a water boiler

Is it ethical to upload a automatically generated paper to a non peer-reviewed site as part of a larger research?

Did the UK government pay "millions and millions of dollars" to try to snag Julian Assange?

Is it okay to consider publishing in my first year of PhD?

Can a rogue use sneak attack with weapons that have the thrown property even if they are not thrown?

How to type a long/em dash `—`

Flight paths in orbit around Ceres?

How come people say “Would of”?

Merge two greps into single one

What's the name of these plastic connectors

Slides for 30 min~1 hr Skype tenure track application interview

Is Cinnamon a desktop environment or a window manager? (Or both?)

Is it possible for absolutely everyone to attain enlightenment?

Why isn't the circumferential light around the M87 black hole's event horizon symmetric?

How can I define good in a religion that claims no moral authority?

What is the most efficient way to store a numeric range?

Can we generate random numbers using irrational numbers like π and e?

The phrase "to the numbers born"?

What do these terms in Caesar's Gallic wars mean?



Kerning for subscripts of sigma?



The 2019 Stack Overflow Developer Survey Results Are InSubscript kerning for specific letters in XeLaTeXMargin kerning in Xe(La)TeX for TeXlive 2010: how to enable?Fix math mode kerning of “C”Turning off TeXnical enhancementsKerning of subscriptsPair kerning strategies in (pdf)LaTeXKerning super- and subscripts “semantically”Subscript kerning for specific letters in XeLaTeXMicrotype kerning won't work with quotationmarksKerning of HyphensIs there a LuaLaTeX solution to adjust superscript kerning on large delimiters?










2















Is there any way to reduce the distance inside σ₀ and between sigma and its subscript in general in the following setup automatically? That is, each time you type in sigma_0 (or sigma_1 etc.), you wish the actual output to be more consistent with sigma_!0 (or sigma_!1 etc.).



Input:



documentclassbook
usepackagefontspec
usepackage[american,british,french,norsk,german,ngerman]babel
usepackagemathtools
mathtoolssetmathic=true %%% See http://tex.stackexchange.com/a/3496/
usepackageamssymb
usepackageunicode-math
setmainfont[Ligatures=TeX]TeX Gyre Termes
setsansfontTeX Gyre Heros[Scale=0.88]
setmonofontTeX Gyre Cursor
setmathfont[Ligatures=TeX]TeX Gyre Termes Math
setmathfont[Ligatures=TeX,range=setminus]Asana Math
setmathfont[Ligatures=TeX,Extension=.otf,range="2A3E,BoldFont=XITSMath-Bold]XITSMath-Regular%%% The fat semicolon
usepackage[babel=true,verbose=errors]microtype
begindocument
[sigma_0 sigma_0]
[sigma_!0 sigma_!0]
enddocument


Output so far:



enter image description here



As you see, in the upper line the left zero seems to be more close to the right σ (which doesn't make any sense) than to the left one (which would make sense). The kerning in the lower line makes more sense.



I guess, this would be easier than Subscript kerning for specific letters in XeLaTeX, since we already have sigma as a macro and can redefine it.



For which letters in the subscript position the kerning should be improved is intentionally left unspecified; improving the kerning in sigma_<any single arabic digit or any single Latin small letter> would suffice as a start. Of course, for σ_T we might need less kerning (e.g., only -1mu rather than -3mu), and that's why capital Latin letters would need more work (and are not asked for in the first step).










share|improve this question
























  • Do you want to change the behaviour for sigma_<any single number>, or for sigma_<any single character>, or sigma_<anything>, or somthing else?

    – Phelype Oleinik
    1 hour ago











  • @PhelypeOleinik Question updated.

    – user49915
    1 hour ago















2















Is there any way to reduce the distance inside σ₀ and between sigma and its subscript in general in the following setup automatically? That is, each time you type in sigma_0 (or sigma_1 etc.), you wish the actual output to be more consistent with sigma_!0 (or sigma_!1 etc.).



Input:



documentclassbook
usepackagefontspec
usepackage[american,british,french,norsk,german,ngerman]babel
usepackagemathtools
mathtoolssetmathic=true %%% See http://tex.stackexchange.com/a/3496/
usepackageamssymb
usepackageunicode-math
setmainfont[Ligatures=TeX]TeX Gyre Termes
setsansfontTeX Gyre Heros[Scale=0.88]
setmonofontTeX Gyre Cursor
setmathfont[Ligatures=TeX]TeX Gyre Termes Math
setmathfont[Ligatures=TeX,range=setminus]Asana Math
setmathfont[Ligatures=TeX,Extension=.otf,range="2A3E,BoldFont=XITSMath-Bold]XITSMath-Regular%%% The fat semicolon
usepackage[babel=true,verbose=errors]microtype
begindocument
[sigma_0 sigma_0]
[sigma_!0 sigma_!0]
enddocument


Output so far:



enter image description here



As you see, in the upper line the left zero seems to be more close to the right σ (which doesn't make any sense) than to the left one (which would make sense). The kerning in the lower line makes more sense.



I guess, this would be easier than Subscript kerning for specific letters in XeLaTeX, since we already have sigma as a macro and can redefine it.



For which letters in the subscript position the kerning should be improved is intentionally left unspecified; improving the kerning in sigma_<any single arabic digit or any single Latin small letter> would suffice as a start. Of course, for σ_T we might need less kerning (e.g., only -1mu rather than -3mu), and that's why capital Latin letters would need more work (and are not asked for in the first step).










share|improve this question
























  • Do you want to change the behaviour for sigma_<any single number>, or for sigma_<any single character>, or sigma_<anything>, or somthing else?

    – Phelype Oleinik
    1 hour ago











  • @PhelypeOleinik Question updated.

    – user49915
    1 hour ago













2












2








2








Is there any way to reduce the distance inside σ₀ and between sigma and its subscript in general in the following setup automatically? That is, each time you type in sigma_0 (or sigma_1 etc.), you wish the actual output to be more consistent with sigma_!0 (or sigma_!1 etc.).



Input:



documentclassbook
usepackagefontspec
usepackage[american,british,french,norsk,german,ngerman]babel
usepackagemathtools
mathtoolssetmathic=true %%% See http://tex.stackexchange.com/a/3496/
usepackageamssymb
usepackageunicode-math
setmainfont[Ligatures=TeX]TeX Gyre Termes
setsansfontTeX Gyre Heros[Scale=0.88]
setmonofontTeX Gyre Cursor
setmathfont[Ligatures=TeX]TeX Gyre Termes Math
setmathfont[Ligatures=TeX,range=setminus]Asana Math
setmathfont[Ligatures=TeX,Extension=.otf,range="2A3E,BoldFont=XITSMath-Bold]XITSMath-Regular%%% The fat semicolon
usepackage[babel=true,verbose=errors]microtype
begindocument
[sigma_0 sigma_0]
[sigma_!0 sigma_!0]
enddocument


Output so far:



enter image description here



As you see, in the upper line the left zero seems to be more close to the right σ (which doesn't make any sense) than to the left one (which would make sense). The kerning in the lower line makes more sense.



I guess, this would be easier than Subscript kerning for specific letters in XeLaTeX, since we already have sigma as a macro and can redefine it.



For which letters in the subscript position the kerning should be improved is intentionally left unspecified; improving the kerning in sigma_<any single arabic digit or any single Latin small letter> would suffice as a start. Of course, for σ_T we might need less kerning (e.g., only -1mu rather than -3mu), and that's why capital Latin letters would need more work (and are not asked for in the first step).










share|improve this question
















Is there any way to reduce the distance inside σ₀ and between sigma and its subscript in general in the following setup automatically? That is, each time you type in sigma_0 (or sigma_1 etc.), you wish the actual output to be more consistent with sigma_!0 (or sigma_!1 etc.).



Input:



documentclassbook
usepackagefontspec
usepackage[american,british,french,norsk,german,ngerman]babel
usepackagemathtools
mathtoolssetmathic=true %%% See http://tex.stackexchange.com/a/3496/
usepackageamssymb
usepackageunicode-math
setmainfont[Ligatures=TeX]TeX Gyre Termes
setsansfontTeX Gyre Heros[Scale=0.88]
setmonofontTeX Gyre Cursor
setmathfont[Ligatures=TeX]TeX Gyre Termes Math
setmathfont[Ligatures=TeX,range=setminus]Asana Math
setmathfont[Ligatures=TeX,Extension=.otf,range="2A3E,BoldFont=XITSMath-Bold]XITSMath-Regular%%% The fat semicolon
usepackage[babel=true,verbose=errors]microtype
begindocument
[sigma_0 sigma_0]
[sigma_!0 sigma_!0]
enddocument


Output so far:



enter image description here



As you see, in the upper line the left zero seems to be more close to the right σ (which doesn't make any sense) than to the left one (which would make sense). The kerning in the lower line makes more sense.



I guess, this would be easier than Subscript kerning for specific letters in XeLaTeX, since we already have sigma as a macro and can redefine it.



For which letters in the subscript position the kerning should be improved is intentionally left unspecified; improving the kerning in sigma_<any single arabic digit or any single Latin small letter> would suffice as a start. Of course, for σ_T we might need less kerning (e.g., only -1mu rather than -3mu), and that's why capital Latin letters would need more work (and are not asked for in the first step).







xetex microtype kerning






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited 38 mins ago







user49915

















asked 2 hours ago









user49915user49915

756122




756122












  • Do you want to change the behaviour for sigma_<any single number>, or for sigma_<any single character>, or sigma_<anything>, or somthing else?

    – Phelype Oleinik
    1 hour ago











  • @PhelypeOleinik Question updated.

    – user49915
    1 hour ago

















  • Do you want to change the behaviour for sigma_<any single number>, or for sigma_<any single character>, or sigma_<anything>, or somthing else?

    – Phelype Oleinik
    1 hour ago











  • @PhelypeOleinik Question updated.

    – user49915
    1 hour ago
















Do you want to change the behaviour for sigma_<any single number>, or for sigma_<any single character>, or sigma_<anything>, or somthing else?

– Phelype Oleinik
1 hour ago





Do you want to change the behaviour for sigma_<any single number>, or for sigma_<any single character>, or sigma_<anything>, or somthing else?

– Phelype Oleinik
1 hour ago













@PhelypeOleinik Question updated.

– user49915
1 hour ago





@PhelypeOleinik Question updated.

– user49915
1 hour ago










2 Answers
2






active

oldest

votes


















2














The following definition does it:



ExplSyntaxOn
cs_new_eq:NN __userxlixk_actual_sigma: sigma
RenewDocumentCommandsigma
__userxlixk_sigma:
cs_new_protected:Npn __userxlixk_sigma:

peek_catcode_remove:NTF c_math_subscript_token
__userxlixk_sigma_check_group:n
__userxlixk_actual_sigma:

cs_new_protected:Npn __userxlixk_sigma_check_group:n #1

tl_if_single_token:nTF #1
__userxlixk_actual_sigma: c_math_subscript_token ! #1
__userxlixk_actual_sigma: c_math_subscript_token #1

ExplSyntaxOff


I save the definition of sigma in __userxlixk_actual_sigma: then redefine sigma to check:



  1. if it is followed by a c_math_subscript_token: if it is not, then just print __userxlixk_actual_sigma: otherwise;


  2. grab what follows the subscript token as argument and check if the argument consists of a single token: if it does, apply a !, otherwise print normally.


Here's the output before and after the redefinition (I used LuaTeX and lua-visual-debug to show the negative kern):




enter image description here




Code:



documentclass[varwidth]standalone
usepackagelua-visual-debug
usepackageluatexbase
usepackageunravel
usepackagefontspec
usepackage[american,british,french,norsk,german,ngerman]babel
usepackagemathtools
mathtoolssetmathic=true %%% See http://tex.stackexchange.com/a/3496/
usepackageamssymb
usepackageunicode-math
setmainfont[Ligatures=TeX]TeX Gyre Termes
setsansfontTeX Gyre Heros[Scale=0.88]
setmonofontTeX Gyre Cursor
setmathfont[Ligatures=TeX]TeX Gyre Termes Math
setmathfont[Ligatures=TeX,range=setminus]Asana Math
setmathfont[Ligatures=TeX,Extension=.otf,range="2A3E,BoldFont=XITSMath-Bold]XITSMath-Regular%%% The fat semicolon
usepackage[babel=true,verbose=errors]microtype
begindocument
$sigma_abc sigma_0 sigma_0$

ExplSyntaxOn
cs_new_eq:NN __userxlixk_actual_sigma: sigma
RenewDocumentCommandsigma
__userxlixk_sigma:
cs_new_protected:Npn __userxlixk_sigma:

peek_catcode_remove:NTF c_math_subscript_token
__userxlixk_sigma_check_group:n
__userxlixk_actual_sigma:

cs_new_protected:Npn __userxlixk_sigma_check_group:n #1

tl_if_single_token:nTF #1
__userxlixk_actual_sigma: c_math_subscript_token ! #1
__userxlixk_actual_sigma: c_math_subscript_token #1

ExplSyntaxOff

$sigma_abc sigma_0 sigma_0$
enddocument


Note, however, that this code will work if you use sigma_a^b but not if you use sigma^b_a.






share|improve this answer























  • To make it work for both sigma_a^b and sigma^b_a you could use an e-type argument (“embellishments”).

    – Henri Menke
    30 mins ago











  • First, thanks! Second, could you adapt your code slightly such that it checks that the first subscript letter (or all subscript letters, it doesn't matter as of now) is small alphanumeric rather than checking that the whole subscript is single-token?

    – user49915
    21 mins ago



















2














I'd use the e argument type of xparse.



documentclassbook
usepackagefontspec
usepackage[american,british,french,norsk,german,ngerman]babel
usepackagemathtools
usepackageamssymb
usepackageunicode-math
usepackage[babel=true,verbose=errors]microtype

setmainfontTeX Gyre Termes
setsansfontTeX Gyre Heros[Scale=0.88]
setmonofontTeX Gyre Cursor
setmathfontTeX Gyre Termes Math
setmathfontAsana Math[
range=setminus,
]
setmathfontXITSMath-Regular[
Extension=.otf,
range="2A3E,
BoldFont=XITSMath-Bold,
]

%mathtoolssetmathic=true %%% See http://tex.stackexchange.com/a/3496/

AtBeginDocument%
letstandardsigmasigma
letsigmakernedsigma


NewDocumentCommandkernedsigmae_^%
standardsigma
IfValueT#1_!#1%
IfValueT#2^#2%


begindocument

[sigma_0 sigma_0^2 sigma^2_0]
[standardsigma_!0 standardsigma_!0^2 standardsigma^2_!0]

enddocument


enter image description here






share|improve this answer























  • First, thanks! Second, could you adapt your code slightly such that it checks that the first subscript letter (or all subscript letters, it doesn't matter as of now) is small alphanumeric? We don't really know whether it would produce a pleasant kerning for all other possible subscripts, would we?

    – user49915
    9 mins ago












  • @user49915 I'm not sure what could be the difference. One can quite easily exclude some symbols from being kerned.

    – egreg
    4 mins ago











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
);



);













draft saved

draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f484404%2fkerning-for-subscripts-of-sigma%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









2














The following definition does it:



ExplSyntaxOn
cs_new_eq:NN __userxlixk_actual_sigma: sigma
RenewDocumentCommandsigma
__userxlixk_sigma:
cs_new_protected:Npn __userxlixk_sigma:

peek_catcode_remove:NTF c_math_subscript_token
__userxlixk_sigma_check_group:n
__userxlixk_actual_sigma:

cs_new_protected:Npn __userxlixk_sigma_check_group:n #1

tl_if_single_token:nTF #1
__userxlixk_actual_sigma: c_math_subscript_token ! #1
__userxlixk_actual_sigma: c_math_subscript_token #1

ExplSyntaxOff


I save the definition of sigma in __userxlixk_actual_sigma: then redefine sigma to check:



  1. if it is followed by a c_math_subscript_token: if it is not, then just print __userxlixk_actual_sigma: otherwise;


  2. grab what follows the subscript token as argument and check if the argument consists of a single token: if it does, apply a !, otherwise print normally.


Here's the output before and after the redefinition (I used LuaTeX and lua-visual-debug to show the negative kern):




enter image description here




Code:



documentclass[varwidth]standalone
usepackagelua-visual-debug
usepackageluatexbase
usepackageunravel
usepackagefontspec
usepackage[american,british,french,norsk,german,ngerman]babel
usepackagemathtools
mathtoolssetmathic=true %%% See http://tex.stackexchange.com/a/3496/
usepackageamssymb
usepackageunicode-math
setmainfont[Ligatures=TeX]TeX Gyre Termes
setsansfontTeX Gyre Heros[Scale=0.88]
setmonofontTeX Gyre Cursor
setmathfont[Ligatures=TeX]TeX Gyre Termes Math
setmathfont[Ligatures=TeX,range=setminus]Asana Math
setmathfont[Ligatures=TeX,Extension=.otf,range="2A3E,BoldFont=XITSMath-Bold]XITSMath-Regular%%% The fat semicolon
usepackage[babel=true,verbose=errors]microtype
begindocument
$sigma_abc sigma_0 sigma_0$

ExplSyntaxOn
cs_new_eq:NN __userxlixk_actual_sigma: sigma
RenewDocumentCommandsigma
__userxlixk_sigma:
cs_new_protected:Npn __userxlixk_sigma:

peek_catcode_remove:NTF c_math_subscript_token
__userxlixk_sigma_check_group:n
__userxlixk_actual_sigma:

cs_new_protected:Npn __userxlixk_sigma_check_group:n #1

tl_if_single_token:nTF #1
__userxlixk_actual_sigma: c_math_subscript_token ! #1
__userxlixk_actual_sigma: c_math_subscript_token #1

ExplSyntaxOff

$sigma_abc sigma_0 sigma_0$
enddocument


Note, however, that this code will work if you use sigma_a^b but not if you use sigma^b_a.






share|improve this answer























  • To make it work for both sigma_a^b and sigma^b_a you could use an e-type argument (“embellishments”).

    – Henri Menke
    30 mins ago











  • First, thanks! Second, could you adapt your code slightly such that it checks that the first subscript letter (or all subscript letters, it doesn't matter as of now) is small alphanumeric rather than checking that the whole subscript is single-token?

    – user49915
    21 mins ago
















2














The following definition does it:



ExplSyntaxOn
cs_new_eq:NN __userxlixk_actual_sigma: sigma
RenewDocumentCommandsigma
__userxlixk_sigma:
cs_new_protected:Npn __userxlixk_sigma:

peek_catcode_remove:NTF c_math_subscript_token
__userxlixk_sigma_check_group:n
__userxlixk_actual_sigma:

cs_new_protected:Npn __userxlixk_sigma_check_group:n #1

tl_if_single_token:nTF #1
__userxlixk_actual_sigma: c_math_subscript_token ! #1
__userxlixk_actual_sigma: c_math_subscript_token #1

ExplSyntaxOff


I save the definition of sigma in __userxlixk_actual_sigma: then redefine sigma to check:



  1. if it is followed by a c_math_subscript_token: if it is not, then just print __userxlixk_actual_sigma: otherwise;


  2. grab what follows the subscript token as argument and check if the argument consists of a single token: if it does, apply a !, otherwise print normally.


Here's the output before and after the redefinition (I used LuaTeX and lua-visual-debug to show the negative kern):




enter image description here




Code:



documentclass[varwidth]standalone
usepackagelua-visual-debug
usepackageluatexbase
usepackageunravel
usepackagefontspec
usepackage[american,british,french,norsk,german,ngerman]babel
usepackagemathtools
mathtoolssetmathic=true %%% See http://tex.stackexchange.com/a/3496/
usepackageamssymb
usepackageunicode-math
setmainfont[Ligatures=TeX]TeX Gyre Termes
setsansfontTeX Gyre Heros[Scale=0.88]
setmonofontTeX Gyre Cursor
setmathfont[Ligatures=TeX]TeX Gyre Termes Math
setmathfont[Ligatures=TeX,range=setminus]Asana Math
setmathfont[Ligatures=TeX,Extension=.otf,range="2A3E,BoldFont=XITSMath-Bold]XITSMath-Regular%%% The fat semicolon
usepackage[babel=true,verbose=errors]microtype
begindocument
$sigma_abc sigma_0 sigma_0$

ExplSyntaxOn
cs_new_eq:NN __userxlixk_actual_sigma: sigma
RenewDocumentCommandsigma
__userxlixk_sigma:
cs_new_protected:Npn __userxlixk_sigma:

peek_catcode_remove:NTF c_math_subscript_token
__userxlixk_sigma_check_group:n
__userxlixk_actual_sigma:

cs_new_protected:Npn __userxlixk_sigma_check_group:n #1

tl_if_single_token:nTF #1
__userxlixk_actual_sigma: c_math_subscript_token ! #1
__userxlixk_actual_sigma: c_math_subscript_token #1

ExplSyntaxOff

$sigma_abc sigma_0 sigma_0$
enddocument


Note, however, that this code will work if you use sigma_a^b but not if you use sigma^b_a.






share|improve this answer























  • To make it work for both sigma_a^b and sigma^b_a you could use an e-type argument (“embellishments”).

    – Henri Menke
    30 mins ago











  • First, thanks! Second, could you adapt your code slightly such that it checks that the first subscript letter (or all subscript letters, it doesn't matter as of now) is small alphanumeric rather than checking that the whole subscript is single-token?

    – user49915
    21 mins ago














2












2








2







The following definition does it:



ExplSyntaxOn
cs_new_eq:NN __userxlixk_actual_sigma: sigma
RenewDocumentCommandsigma
__userxlixk_sigma:
cs_new_protected:Npn __userxlixk_sigma:

peek_catcode_remove:NTF c_math_subscript_token
__userxlixk_sigma_check_group:n
__userxlixk_actual_sigma:

cs_new_protected:Npn __userxlixk_sigma_check_group:n #1

tl_if_single_token:nTF #1
__userxlixk_actual_sigma: c_math_subscript_token ! #1
__userxlixk_actual_sigma: c_math_subscript_token #1

ExplSyntaxOff


I save the definition of sigma in __userxlixk_actual_sigma: then redefine sigma to check:



  1. if it is followed by a c_math_subscript_token: if it is not, then just print __userxlixk_actual_sigma: otherwise;


  2. grab what follows the subscript token as argument and check if the argument consists of a single token: if it does, apply a !, otherwise print normally.


Here's the output before and after the redefinition (I used LuaTeX and lua-visual-debug to show the negative kern):




enter image description here




Code:



documentclass[varwidth]standalone
usepackagelua-visual-debug
usepackageluatexbase
usepackageunravel
usepackagefontspec
usepackage[american,british,french,norsk,german,ngerman]babel
usepackagemathtools
mathtoolssetmathic=true %%% See http://tex.stackexchange.com/a/3496/
usepackageamssymb
usepackageunicode-math
setmainfont[Ligatures=TeX]TeX Gyre Termes
setsansfontTeX Gyre Heros[Scale=0.88]
setmonofontTeX Gyre Cursor
setmathfont[Ligatures=TeX]TeX Gyre Termes Math
setmathfont[Ligatures=TeX,range=setminus]Asana Math
setmathfont[Ligatures=TeX,Extension=.otf,range="2A3E,BoldFont=XITSMath-Bold]XITSMath-Regular%%% The fat semicolon
usepackage[babel=true,verbose=errors]microtype
begindocument
$sigma_abc sigma_0 sigma_0$

ExplSyntaxOn
cs_new_eq:NN __userxlixk_actual_sigma: sigma
RenewDocumentCommandsigma
__userxlixk_sigma:
cs_new_protected:Npn __userxlixk_sigma:

peek_catcode_remove:NTF c_math_subscript_token
__userxlixk_sigma_check_group:n
__userxlixk_actual_sigma:

cs_new_protected:Npn __userxlixk_sigma_check_group:n #1

tl_if_single_token:nTF #1
__userxlixk_actual_sigma: c_math_subscript_token ! #1
__userxlixk_actual_sigma: c_math_subscript_token #1

ExplSyntaxOff

$sigma_abc sigma_0 sigma_0$
enddocument


Note, however, that this code will work if you use sigma_a^b but not if you use sigma^b_a.






share|improve this answer













The following definition does it:



ExplSyntaxOn
cs_new_eq:NN __userxlixk_actual_sigma: sigma
RenewDocumentCommandsigma
__userxlixk_sigma:
cs_new_protected:Npn __userxlixk_sigma:

peek_catcode_remove:NTF c_math_subscript_token
__userxlixk_sigma_check_group:n
__userxlixk_actual_sigma:

cs_new_protected:Npn __userxlixk_sigma_check_group:n #1

tl_if_single_token:nTF #1
__userxlixk_actual_sigma: c_math_subscript_token ! #1
__userxlixk_actual_sigma: c_math_subscript_token #1

ExplSyntaxOff


I save the definition of sigma in __userxlixk_actual_sigma: then redefine sigma to check:



  1. if it is followed by a c_math_subscript_token: if it is not, then just print __userxlixk_actual_sigma: otherwise;


  2. grab what follows the subscript token as argument and check if the argument consists of a single token: if it does, apply a !, otherwise print normally.


Here's the output before and after the redefinition (I used LuaTeX and lua-visual-debug to show the negative kern):




enter image description here




Code:



documentclass[varwidth]standalone
usepackagelua-visual-debug
usepackageluatexbase
usepackageunravel
usepackagefontspec
usepackage[american,british,french,norsk,german,ngerman]babel
usepackagemathtools
mathtoolssetmathic=true %%% See http://tex.stackexchange.com/a/3496/
usepackageamssymb
usepackageunicode-math
setmainfont[Ligatures=TeX]TeX Gyre Termes
setsansfontTeX Gyre Heros[Scale=0.88]
setmonofontTeX Gyre Cursor
setmathfont[Ligatures=TeX]TeX Gyre Termes Math
setmathfont[Ligatures=TeX,range=setminus]Asana Math
setmathfont[Ligatures=TeX,Extension=.otf,range="2A3E,BoldFont=XITSMath-Bold]XITSMath-Regular%%% The fat semicolon
usepackage[babel=true,verbose=errors]microtype
begindocument
$sigma_abc sigma_0 sigma_0$

ExplSyntaxOn
cs_new_eq:NN __userxlixk_actual_sigma: sigma
RenewDocumentCommandsigma
__userxlixk_sigma:
cs_new_protected:Npn __userxlixk_sigma:

peek_catcode_remove:NTF c_math_subscript_token
__userxlixk_sigma_check_group:n
__userxlixk_actual_sigma:

cs_new_protected:Npn __userxlixk_sigma_check_group:n #1

tl_if_single_token:nTF #1
__userxlixk_actual_sigma: c_math_subscript_token ! #1
__userxlixk_actual_sigma: c_math_subscript_token #1

ExplSyntaxOff

$sigma_abc sigma_0 sigma_0$
enddocument


Note, however, that this code will work if you use sigma_a^b but not if you use sigma^b_a.







share|improve this answer












share|improve this answer



share|improve this answer










answered 32 mins ago









Phelype OleinikPhelype Oleinik

25k54690




25k54690












  • To make it work for both sigma_a^b and sigma^b_a you could use an e-type argument (“embellishments”).

    – Henri Menke
    30 mins ago











  • First, thanks! Second, could you adapt your code slightly such that it checks that the first subscript letter (or all subscript letters, it doesn't matter as of now) is small alphanumeric rather than checking that the whole subscript is single-token?

    – user49915
    21 mins ago


















  • To make it work for both sigma_a^b and sigma^b_a you could use an e-type argument (“embellishments”).

    – Henri Menke
    30 mins ago











  • First, thanks! Second, could you adapt your code slightly such that it checks that the first subscript letter (or all subscript letters, it doesn't matter as of now) is small alphanumeric rather than checking that the whole subscript is single-token?

    – user49915
    21 mins ago

















To make it work for both sigma_a^b and sigma^b_a you could use an e-type argument (“embellishments”).

– Henri Menke
30 mins ago





To make it work for both sigma_a^b and sigma^b_a you could use an e-type argument (“embellishments”).

– Henri Menke
30 mins ago













First, thanks! Second, could you adapt your code slightly such that it checks that the first subscript letter (or all subscript letters, it doesn't matter as of now) is small alphanumeric rather than checking that the whole subscript is single-token?

– user49915
21 mins ago






First, thanks! Second, could you adapt your code slightly such that it checks that the first subscript letter (or all subscript letters, it doesn't matter as of now) is small alphanumeric rather than checking that the whole subscript is single-token?

– user49915
21 mins ago












2














I'd use the e argument type of xparse.



documentclassbook
usepackagefontspec
usepackage[american,british,french,norsk,german,ngerman]babel
usepackagemathtools
usepackageamssymb
usepackageunicode-math
usepackage[babel=true,verbose=errors]microtype

setmainfontTeX Gyre Termes
setsansfontTeX Gyre Heros[Scale=0.88]
setmonofontTeX Gyre Cursor
setmathfontTeX Gyre Termes Math
setmathfontAsana Math[
range=setminus,
]
setmathfontXITSMath-Regular[
Extension=.otf,
range="2A3E,
BoldFont=XITSMath-Bold,
]

%mathtoolssetmathic=true %%% See http://tex.stackexchange.com/a/3496/

AtBeginDocument%
letstandardsigmasigma
letsigmakernedsigma


NewDocumentCommandkernedsigmae_^%
standardsigma
IfValueT#1_!#1%
IfValueT#2^#2%


begindocument

[sigma_0 sigma_0^2 sigma^2_0]
[standardsigma_!0 standardsigma_!0^2 standardsigma^2_!0]

enddocument


enter image description here






share|improve this answer























  • First, thanks! Second, could you adapt your code slightly such that it checks that the first subscript letter (or all subscript letters, it doesn't matter as of now) is small alphanumeric? We don't really know whether it would produce a pleasant kerning for all other possible subscripts, would we?

    – user49915
    9 mins ago












  • @user49915 I'm not sure what could be the difference. One can quite easily exclude some symbols from being kerned.

    – egreg
    4 mins ago















2














I'd use the e argument type of xparse.



documentclassbook
usepackagefontspec
usepackage[american,british,french,norsk,german,ngerman]babel
usepackagemathtools
usepackageamssymb
usepackageunicode-math
usepackage[babel=true,verbose=errors]microtype

setmainfontTeX Gyre Termes
setsansfontTeX Gyre Heros[Scale=0.88]
setmonofontTeX Gyre Cursor
setmathfontTeX Gyre Termes Math
setmathfontAsana Math[
range=setminus,
]
setmathfontXITSMath-Regular[
Extension=.otf,
range="2A3E,
BoldFont=XITSMath-Bold,
]

%mathtoolssetmathic=true %%% See http://tex.stackexchange.com/a/3496/

AtBeginDocument%
letstandardsigmasigma
letsigmakernedsigma


NewDocumentCommandkernedsigmae_^%
standardsigma
IfValueT#1_!#1%
IfValueT#2^#2%


begindocument

[sigma_0 sigma_0^2 sigma^2_0]
[standardsigma_!0 standardsigma_!0^2 standardsigma^2_!0]

enddocument


enter image description here






share|improve this answer























  • First, thanks! Second, could you adapt your code slightly such that it checks that the first subscript letter (or all subscript letters, it doesn't matter as of now) is small alphanumeric? We don't really know whether it would produce a pleasant kerning for all other possible subscripts, would we?

    – user49915
    9 mins ago












  • @user49915 I'm not sure what could be the difference. One can quite easily exclude some symbols from being kerned.

    – egreg
    4 mins ago













2












2








2







I'd use the e argument type of xparse.



documentclassbook
usepackagefontspec
usepackage[american,british,french,norsk,german,ngerman]babel
usepackagemathtools
usepackageamssymb
usepackageunicode-math
usepackage[babel=true,verbose=errors]microtype

setmainfontTeX Gyre Termes
setsansfontTeX Gyre Heros[Scale=0.88]
setmonofontTeX Gyre Cursor
setmathfontTeX Gyre Termes Math
setmathfontAsana Math[
range=setminus,
]
setmathfontXITSMath-Regular[
Extension=.otf,
range="2A3E,
BoldFont=XITSMath-Bold,
]

%mathtoolssetmathic=true %%% See http://tex.stackexchange.com/a/3496/

AtBeginDocument%
letstandardsigmasigma
letsigmakernedsigma


NewDocumentCommandkernedsigmae_^%
standardsigma
IfValueT#1_!#1%
IfValueT#2^#2%


begindocument

[sigma_0 sigma_0^2 sigma^2_0]
[standardsigma_!0 standardsigma_!0^2 standardsigma^2_!0]

enddocument


enter image description here






share|improve this answer













I'd use the e argument type of xparse.



documentclassbook
usepackagefontspec
usepackage[american,british,french,norsk,german,ngerman]babel
usepackagemathtools
usepackageamssymb
usepackageunicode-math
usepackage[babel=true,verbose=errors]microtype

setmainfontTeX Gyre Termes
setsansfontTeX Gyre Heros[Scale=0.88]
setmonofontTeX Gyre Cursor
setmathfontTeX Gyre Termes Math
setmathfontAsana Math[
range=setminus,
]
setmathfontXITSMath-Regular[
Extension=.otf,
range="2A3E,
BoldFont=XITSMath-Bold,
]

%mathtoolssetmathic=true %%% See http://tex.stackexchange.com/a/3496/

AtBeginDocument%
letstandardsigmasigma
letsigmakernedsigma


NewDocumentCommandkernedsigmae_^%
standardsigma
IfValueT#1_!#1%
IfValueT#2^#2%


begindocument

[sigma_0 sigma_0^2 sigma^2_0]
[standardsigma_!0 standardsigma_!0^2 standardsigma^2_!0]

enddocument


enter image description here







share|improve this answer












share|improve this answer



share|improve this answer










answered 14 mins ago









egregegreg

733k8919313254




733k8919313254












  • First, thanks! Second, could you adapt your code slightly such that it checks that the first subscript letter (or all subscript letters, it doesn't matter as of now) is small alphanumeric? We don't really know whether it would produce a pleasant kerning for all other possible subscripts, would we?

    – user49915
    9 mins ago












  • @user49915 I'm not sure what could be the difference. One can quite easily exclude some symbols from being kerned.

    – egreg
    4 mins ago

















  • First, thanks! Second, could you adapt your code slightly such that it checks that the first subscript letter (or all subscript letters, it doesn't matter as of now) is small alphanumeric? We don't really know whether it would produce a pleasant kerning for all other possible subscripts, would we?

    – user49915
    9 mins ago












  • @user49915 I'm not sure what could be the difference. One can quite easily exclude some symbols from being kerned.

    – egreg
    4 mins ago
















First, thanks! Second, could you adapt your code slightly such that it checks that the first subscript letter (or all subscript letters, it doesn't matter as of now) is small alphanumeric? We don't really know whether it would produce a pleasant kerning for all other possible subscripts, would we?

– user49915
9 mins ago






First, thanks! Second, could you adapt your code slightly such that it checks that the first subscript letter (or all subscript letters, it doesn't matter as of now) is small alphanumeric? We don't really know whether it would produce a pleasant kerning for all other possible subscripts, would we?

– user49915
9 mins ago














@user49915 I'm not sure what could be the difference. One can quite easily exclude some symbols from being kerned.

– egreg
4 mins ago





@user49915 I'm not sure what could be the difference. One can quite easily exclude some symbols from being kerned.

– egreg
4 mins ago

















draft saved

draft discarded
















































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.




draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f484404%2fkerning-for-subscripts-of-sigma%23new-answer', 'question_page');

);

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







Popular posts from this blog

Best approach to update all entries in a list that is paginated?Best way to add items to a paginated listChoose Your Country: Best Usability approachUpdate list when a user is viewing the list without annoying themWhen would the best day to update your webpage be?What should happen when I add a Row to a paginated, sorted listShould I adopt infinite scrolling or classical pagination?How to show user that page objects automatically updateWhat is the best location to locate the comments section in a list pageBest way to combine filtering and selecting items in a listWhen one of two inputs must be updated to satisfy a consistency criteria, which should you update (if at all)?

Вунгтау (аеропорт) Загальні відомості | Див. також | Посилання | Навігаційне меню10°22′00″ пн. ш. 107°05′00″ сх. д. / 10.36667° пн. ш. 107.08333° сх. д. / 10.36667; 107.0833310°22′00″ пн. ш. 107°05′00″ сх. д. / 10.36667° пн. ш. 107.08333° сх. д. / 10.36667; 107.083337731608Vinh AirportVinh airport facelift improves serviceвиправивши або дописавши їївиправивши або дописавши їїр

Тонконіг бульбистий Зміст Опис | Поширення | Екологія | Господарське значення | Примітки | Див. також | Література | Джерела | Посилання | Навігаційне меню1114601320038-241116202404kew-435458Poa bulbosaЭлектронный каталог сосудистых растений Азиатской России [Електронний каталог судинних рослин Азіатської Росії]Малышев Л. Л. Дикие родичи культурных растений. Poa bulbosa L. - Мятлик луковичный. [Малишев Л. Л. Дикі родичи культурних рослин. Poa bulbosa L. - Тонконіг бульбистий.]Мятлик (POA) Сем. Злаки (Мятликовые) [Тонконіг (POA) Род. Злаки (Тонконогові)]Poa bulbosa Linnaeus, Sp. Pl. 1: 70. 1753. 鳞茎早熟禾 lin jing zao shu he (Description from Flora of China) [Poa bulbosa Linnaeus, Sp. Pl. 1: 70. 1753. 鳞茎早熟禾 lin jing zao shu he (Опис від Флора Китаю)]Poa bulbosa L. – lipnice cibulkatá / lipnica cibulkatáPoa bulbosa в базі даних Poa bulbosa на сайті Poa bulbosa в базі даних «Global Biodiversity Information Facility» (GBIF)Poa bulbosa в базі даних «Euro + Med PlantBase» — інформаційному ресурсі для Євро-середземноморського розмаїття рослинPoa bulbosa L. на сайті «Плантариум»