Index ordering when using math symbols












13















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




















  • 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
















13















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




















  • 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














13












13








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
















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




indexing sorting






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Aug 22 '12 at 13:31









Thorsten

9,86965663




9,86965663










asked Aug 22 '12 at 13:26









Eivind DahlEivind Dahl

385211




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














  • 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








4




4





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

– egreg
Aug 22 '12 at 13:28





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





@egreg: why don't you post this as an answer?

– bodo
Aug 22 '12 at 13:29










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





















  • 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












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%2f68240%2findex-ordering-when-using-math-symbols%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









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





















  • 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
















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





















  • 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














18












18








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















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














share|improve this answer



share|improve this answer








edited 5 hours ago

























answered Aug 22 '12 at 13:36









barbara beetonbarbara beeton

70.1k9159380




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














  • 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








1




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





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




4





Were the notes ever published?

– Yiannis Lazarides
Jun 26 '15 at 7:20





Were the notes ever published?

– Yiannis Lazarides
Jun 26 '15 at 7:20




1




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





@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




2





@barbarabeeton Will be looking forward to it :)

– Eivind Dahl
Jun 26 '15 at 12:35





@barbarabeeton Will be looking forward to it :)

– Eivind Dahl
Jun 26 '15 at 12:35




1




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





@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


















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%2f68240%2findex-ordering-when-using-math-symbols%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

Contact image not getting when fetch all contact list from iPhone by CNContact

Image
up vote 0 down vote favorite I know this question already asked but not getting solution. From this code I will get all the information from the contact but image not found when open vcf files on mac os, also not getting when share this file. I use this stackoverflow link here but It's not help full. var contacts = [CNContact]() let keys = [CNContactVCardSerialization.descriptorForRequiredKeys() ] as [Any] let request = CNContactFetchRequest(keysToFetch: keys as! [CNKeyDescriptor]) do { try self.contactStore.enumerateContacts(with: request) { (contact, stop) in // Array containing all unified contacts from everywhere contacts.append(contact) } } catch { print("unable to fetch contacts") } do { let data = try
Read more

count number of partitions of a set with n elements into k subsets

Image
up vote 6 down vote favorite 1 This program is for count number of partitions of a set with n elements into k subsets I am confusing here return k*countP(n-1, k) + countP(n-1, k-1); can some one explain what is happening here? why we are multiplying with k? NOTE->I know this is not the best way to calculate number of partitions that would be DP // A C++ program to count number of partitions // of a set with n elements into k subsets #include<iostream> using namespace std; // Returns count of different partitions of n // elements in k subsets int countP(int n, int k) { // Base cases if (n == 0 || k == 0 || k > n) return 0; if (k == 1 || k == n) return 1; // S(n+1, k) = k*S(n, k) + S(n, k-1) return k*countP(n-1, k) + countP(n-1, k-1); } // Driver program int ma
Read more

A CLEAN and SIMPLE way to add appendices to Table of Contents and bookmarks

Image
0 I found a lot of questions abount appendices and ToC. Many users want appendices to be grouped in an Appendix part, however some problems arise with ToC, hyperref, PDF viewer bookmarks, and so on. There are different solutions which require extra packages, command patching and other extra code, however none of them satisfies me. I almost found an easy way to accomplish a good result, where appendices are added to bookmarks in the right way and hyperref links point to the right page. However, the number of the "Appendix" part page is wrong (it's the number of appendix A). Is there any EASY way to fix that? This is a MWE: documentclass{book} usepackage[nottoc,notlot,notlof]{tocbibind} usepackage{hyperref} begin{document} frontmatter tableofcontents mainmatter part{First} chapter{
Read more