Kdtyjb

How did the USSR manage to innovate in an environment characterized by government censorship and high bureaucracy?

What's the point of deactivating Num Lock on login screens?

How to find program name(s) of an installed package?

How old can references or sources in a thesis be?

Problem of parity - Can we draw a closed path made up of 20 line segments...

Why are 150k or 200k jobs considered good when there are 300k+ births a month?

Why can't I see bouncing of a switch on an oscilloscope?

What is the offset in a seaplane's hull?

What do you call a Matrix-like slowdown and camera movement effect?

A newer friend of my brother's gave him a load of baseball cards that are supposedly extremely valuable. Is this a scam?

I’m planning on buying a laser printer but concerned about the life cycle of toner in the machine

Arthur Somervell: 1000 Exercises - Meaning of this notation

TGV timetables / schedules?

Can I make popcorn with any corn?

Today is the Center

Is it unprofessional to ask if a job posting on GlassDoor is real?

Python: next in for loop

Mathematical cryptic clues

Fencing style for blades that can attack from a distance

The Two and the One

Why dont electromagnetic waves interact with each other?

"You are your self first supporter", a more proper way to say it

What does it mean to describe someone as a butt steak?

How can I make my BBEG immortal short of making them a Lich or Vampire?

Index ordering when using math symbols

Occasionally wrong page numbers for index entriesRedefining ordering in indexSorting index entries with accented wordsSimplify index nested entriesIndexes using datagidx where multiple terms have a single index entryNicely showing 'special' index entries in the marginNomenclature Sorting: Correct sorting of math while using groupsOccasionally wrong page numbers for index entriesmakeindex - Sorting by page number using many math symbolsnewcommand for index inserts unwanted spaces when using {}How to add custom letter groups to an index, e.g. for greek letters or brackets?

13

7

I'm making an index where certain entries start with the math symbols $k$, $mathcal{C}$, $ast$-a.... In the first two cases, I want them to appear in the index as if they start with k and c respectively. In the last case I want the index to ignore $ast$- and treat the word as if it begins with the letter a.

How might I go about doing that?

indexing sorting

share|improve this question

edited Aug 22 '12 at 13:31

Thorsten

9,86965663

asked Aug 22 '12 at 13:26

Eivind DahlEivind Dahl

385211

• 
  
  
  

  
  4
  

  
  
  
  
  
  

  
  
  index{k@$k$} and index{c@$mathcal{C}$}
  
  – egreg
  Aug 22 '12 at 13:28
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @egreg: why don't you post this as an answer?
  
  – bodo
  Aug 22 '12 at 13:29
  

  
  
  
  

add a comment | 

13

7

I'm making an index where certain entries start with the math symbols $k$, $mathcal{C}$, $ast$-a.... In the first two cases, I want them to appear in the index as if they start with k and c respectively. In the last case I want the index to ignore $ast$- and treat the word as if it begins with the letter a.

How might I go about doing that?

indexing sorting

share|improve this question

edited Aug 22 '12 at 13:31

Thorsten

9,86965663

asked Aug 22 '12 at 13:26

Eivind DahlEivind Dahl

385211

• 
  
  
  

  
  4
  

  
  
  
  
  
  

  
  
  index{k@$k$} and index{c@$mathcal{C}$}
  
  – egreg
  Aug 22 '12 at 13:28
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @egreg: why don't you post this as an answer?
  
  – bodo
  Aug 22 '12 at 13:29
  

  
  
  
  

add a comment | 

I'm making an index where certain entries start with the math symbols $k$, $mathcal{C}$, $ast$-a.... In the first two cases, I want them to appear in the index as if they start with k and c respectively. In the last case I want the index to ignore $ast$- and treat the word as if it begins with the letter a.

How might I go about doing that?

indexing sorting

share|improve this question

edited Aug 22 '12 at 13:31

Thorsten

9,86965663

asked Aug 22 '12 at 13:26

Eivind DahlEivind Dahl

385211

share|improve this question

edited Aug 22 '12 at 13:31

Thorsten

9,86965663

asked Aug 22 '12 at 13:26

Eivind DahlEivind Dahl

385211

share|improve this question

edited Aug 22 '12 at 13:31

Thorsten

9,86965663

asked Aug 22 '12 at 13:26

Eivind DahlEivind Dahl

385211

edited Aug 22 '12 at 13:31

Thorsten

9,86965663

edited Aug 22 '12 at 13:31

Thorsten

9,86965663

asked Aug 22 '12 at 13:26

Eivind DahlEivind Dahl

385211

asked Aug 22 '12 at 13:26

Eivind DahlEivind Dahl

385211

1 Answer
1

active

oldest

votes

18

you need to give these entries a sort field. you've actually chosen the easiest approach, sorting them in with the alphabetic entries. egreg has provided good examples for the first two:

index{k@$k$} and index{c@$mathcal{C}$}

my suggestion for the * is

index{a sterisk@$ast$}

including a space after the a to make sure it sorts at the beginning.

i've been compiling a set of notes on how to prepare a "clean" index, presenting tactics for avoiding all the problems i've seen in my experience as author technical support for the ams; when it's ready for general consumption, it will be posted on the ams web site for general reference, and i'll update this answer with a link.

Addendum:

(1) Regarding the index sort: Remember that the sorting is parallel at each level, so if a symbol is subsidiary to another entry, a sort field needs to be provided at the relevant level. Say you have this two-level entry with multiple sub-entries at the second level:

Entry

  First sub-entry

  Omega (the symbol)

Assuming you want the sub-entries in alphabetical order, you should enter the second sub-entry as

index{Entry!Omega@$Omega$}

otherwise it will be sorted before the first sub-entry.

The same principle applies at the third level, if your index entries are nested that deeply.

(2) Between the time of the original answer and this addendum, I have retired, and there is no longer any question that an answer might be the "official" position of my employer. Hence any posting by me will now be in "proper" upper- and lowercase.

There is another consequence implied here. The notes I was compiling on preparing a "clean" index weren't completed before I left AMS. I do intend to complete them, but it's not certain that they will be posted on the AMS web site. They will, however, be posted to CTAN and I'll give a link when this happens.

share|improve this answer

edited 5 hours ago

answered Aug 22 '12 at 13:36

barbara beetonbarbara beeton

70.1k9159380

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  Makeindex knows a section for symbols before the letter A. Therefore I would start the sort key with a symbol, if the symbols should be sorted in the symbol section: index{$asterisk@$ast$}, index{$colon@:}, …
  
  – Heiko Oberdiek
  Aug 22 '12 at 13:52
  

  
  
  
  


• 
  
  
  

  
  4
  

  
  
  
  
  
  

  
  
  Were the notes ever published?
  
  – Yiannis Lazarides
  Jun 26 '15 at 7:20
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  @YiannisLazarides -- sadly, it's still on my "to do" list, er, pushdown stack. it'll come to the surface sometime, but right now, i can't predict when.
  
  – barbara beeton
  Jun 26 '15 at 12:25
  

  
  
  
  


• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  
  @barbarabeeton Will be looking forward to it :)
  
  – Eivind Dahl
  Jun 26 '15 at 12:35
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  @EivindDahl -- still working; new developments in the glossaries area have caused me to rethink this area. (please keep nagging.)
  
  – barbara beeton
  Jun 1 '18 at 12:47
  

  
  
  
  

 | 
show 13 more comments

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

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

Name

Email

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f68240%2findex-ordering-when-using-math-symbols%23new-answer', 'question_page');
}
);

Post as a guest

Name

Email

Required, but never shown

18

you need to give these entries a sort field. you've actually chosen the easiest approach, sorting them in with the alphabetic entries. egreg has provided good examples for the first two:

index{k@$k$} and index{c@$mathcal{C}$}

my suggestion for the * is

index{a sterisk@$ast$}

including a space after the a to make sure it sorts at the beginning.

i've been compiling a set of notes on how to prepare a "clean" index, presenting tactics for avoiding all the problems i've seen in my experience as author technical support for the ams; when it's ready for general consumption, it will be posted on the ams web site for general reference, and i'll update this answer with a link.

Addendum:

(1) Regarding the index sort: Remember that the sorting is parallel at each level, so if a symbol is subsidiary to another entry, a sort field needs to be provided at the relevant level. Say you have this two-level entry with multiple sub-entries at the second level:

Entry

  First sub-entry

  Omega (the symbol)

Assuming you want the sub-entries in alphabetical order, you should enter the second sub-entry as

index{Entry!Omega@$Omega$}

otherwise it will be sorted before the first sub-entry.

The same principle applies at the third level, if your index entries are nested that deeply.

(2) Between the time of the original answer and this addendum, I have retired, and there is no longer any question that an answer might be the "official" position of my employer. Hence any posting by me will now be in "proper" upper- and lowercase.

There is another consequence implied here. The notes I was compiling on preparing a "clean" index weren't completed before I left AMS. I do intend to complete them, but it's not certain that they will be posted on the AMS web site. They will, however, be posted to CTAN and I'll give a link when this happens.

share|improve this answer

edited 5 hours ago

answered Aug 22 '12 at 13:36

barbara beetonbarbara beeton

70.1k9159380

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  Makeindex knows a section for symbols before the letter A. Therefore I would start the sort key with a symbol, if the symbols should be sorted in the symbol section: index{$asterisk@$ast$}, index{$colon@:}, …
  
  – Heiko Oberdiek
  Aug 22 '12 at 13:52
  

  
  
  
  


• 
  
  
  

  
  4
  

  
  
  
  
  
  

  
  
  Were the notes ever published?
  
  – Yiannis Lazarides
  Jun 26 '15 at 7:20
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  @YiannisLazarides -- sadly, it's still on my "to do" list, er, pushdown stack. it'll come to the surface sometime, but right now, i can't predict when.
  
  – barbara beeton
  Jun 26 '15 at 12:25
  

  
  
  
  


• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  
  @barbarabeeton Will be looking forward to it :)
  
  – Eivind Dahl
  Jun 26 '15 at 12:35
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  @EivindDahl -- still working; new developments in the glossaries area have caused me to rethink this area. (please keep nagging.)
  
  – barbara beeton
  Jun 1 '18 at 12:47
  

  
  
  
  

 | 
show 13 more comments

18

you need to give these entries a sort field. you've actually chosen the easiest approach, sorting them in with the alphabetic entries. egreg has provided good examples for the first two:

index{k@$k$} and index{c@$mathcal{C}$}

my suggestion for the * is

index{a sterisk@$ast$}

including a space after the a to make sure it sorts at the beginning.

i've been compiling a set of notes on how to prepare a "clean" index, presenting tactics for avoiding all the problems i've seen in my experience as author technical support for the ams; when it's ready for general consumption, it will be posted on the ams web site for general reference, and i'll update this answer with a link.

Addendum:

(1) Regarding the index sort: Remember that the sorting is parallel at each level, so if a symbol is subsidiary to another entry, a sort field needs to be provided at the relevant level. Say you have this two-level entry with multiple sub-entries at the second level:

Entry

  First sub-entry

  Omega (the symbol)

Assuming you want the sub-entries in alphabetical order, you should enter the second sub-entry as

index{Entry!Omega@$Omega$}

otherwise it will be sorted before the first sub-entry.

The same principle applies at the third level, if your index entries are nested that deeply.

(2) Between the time of the original answer and this addendum, I have retired, and there is no longer any question that an answer might be the "official" position of my employer. Hence any posting by me will now be in "proper" upper- and lowercase.

There is another consequence implied here. The notes I was compiling on preparing a "clean" index weren't completed before I left AMS. I do intend to complete them, but it's not certain that they will be posted on the AMS web site. They will, however, be posted to CTAN and I'll give a link when this happens.

share|improve this answer

edited 5 hours ago

answered Aug 22 '12 at 13:36

barbara beetonbarbara beeton

70.1k9159380

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  Makeindex knows a section for symbols before the letter A. Therefore I would start the sort key with a symbol, if the symbols should be sorted in the symbol section: index{$asterisk@$ast$}, index{$colon@:}, …
  
  – Heiko Oberdiek
  Aug 22 '12 at 13:52
  

  
  
  
  


• 
  
  
  

  
  4
  

  
  
  
  
  
  

  
  
  Were the notes ever published?
  
  – Yiannis Lazarides
  Jun 26 '15 at 7:20
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  @YiannisLazarides -- sadly, it's still on my "to do" list, er, pushdown stack. it'll come to the surface sometime, but right now, i can't predict when.
  
  – barbara beeton
  Jun 26 '15 at 12:25
  

  
  
  
  


• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  
  @barbarabeeton Will be looking forward to it :)
  
  – Eivind Dahl
  Jun 26 '15 at 12:35
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  @EivindDahl -- still working; new developments in the glossaries area have caused me to rethink this area. (please keep nagging.)
  
  – barbara beeton
  Jun 1 '18 at 12:47
  

  
  
  
  

 | 
show 13 more comments

you need to give these entries a sort field. you've actually chosen the easiest approach, sorting them in with the alphabetic entries. egreg has provided good examples for the first two:

index{k@$k$} and index{c@$mathcal{C}$}

my suggestion for the * is

index{a sterisk@$ast$}

including a space after the a to make sure it sorts at the beginning.

i've been compiling a set of notes on how to prepare a "clean" index, presenting tactics for avoiding all the problems i've seen in my experience as author technical support for the ams; when it's ready for general consumption, it will be posted on the ams web site for general reference, and i'll update this answer with a link.

Addendum:

(1) Regarding the index sort: Remember that the sorting is parallel at each level, so if a symbol is subsidiary to another entry, a sort field needs to be provided at the relevant level. Say you have this two-level entry with multiple sub-entries at the second level:

Entry

  First sub-entry

  Omega (the symbol)

Assuming you want the sub-entries in alphabetical order, you should enter the second sub-entry as

index{Entry!Omega@$Omega$}

otherwise it will be sorted before the first sub-entry.

The same principle applies at the third level, if your index entries are nested that deeply.

(2) Between the time of the original answer and this addendum, I have retired, and there is no longer any question that an answer might be the "official" position of my employer. Hence any posting by me will now be in "proper" upper- and lowercase.

There is another consequence implied here. The notes I was compiling on preparing a "clean" index weren't completed before I left AMS. I do intend to complete them, but it's not certain that they will be posted on the AMS web site. They will, however, be posted to CTAN and I'll give a link when this happens.

share|improve this answer

edited 5 hours ago

answered Aug 22 '12 at 13:36

barbara beetonbarbara beeton

70.1k9159380

index{Entry!Omega@$Omega$}

share|improve this answer

edited 5 hours ago

answered Aug 22 '12 at 13:36

barbara beetonbarbara beeton

70.1k9159380

answered Aug 22 '12 at 13:36

barbara beetonbarbara beeton

70.1k9159380

answered Aug 22 '12 at 13:36

barbara beetonbarbara beeton

70.1k9159380