MakeIndex: entries rejected because of duodecimal page numbers












1















I recently changed the page numbers to duodecimal ones (see here). The package makeidx didn't like that at all. In fact my index isn't written at all anymore:




done (0 entries accepted, 341 rejected). Nothing written in
Kyroledorn Yartolikor.ind. Transcript written in Kyroledorn
Yartolikor.ilg.




Everything worked before the change, so this is the only problem here. Other questions imply that makeidx has some restrictions regarding alterations in the page numbers but I didn't find a solution for this problem. Any ideas?



As a code example I added an index into the code sample from the question above, exactly as I did it in my other file.



documentclass[11pt,a4paper,final]{book}
usepackage[left=2cm,right=2cm,top=2cm,bottom=2cm]{geometry}
usepackage{makeidx}
makeindex
usepackage{graphicx} % I need this to rotate my numbers...
usepackage{xparse} % this is the magic package...
ExplSyntaxOn % for the missing numbers after 9 the package uses "a" and "b",
% but I want to use "↊" and "↋" as defined by the Dozenal
% Society of Great Britain. The following lines do that for me:

NewDocumentCommand{basetwelve}{m}
{ duodec_convert:n { #1 } }

tl_new:N l_duodec_string_tl
cs_new_protected:Npn duodec_convert:n #1
{
tl_set:Nx l_duodec_string_tl { int_to_base:nn { #1 } { 12 } }
tl_replace_all:Nnn l_duodec_string_tl { a } { rotatebox[origin=c]{180}{2} }
% I rotate the numbers, because standard fonts don't contain ↊ and ↋.
tl_replace_all:Nnn l_duodec_string_tl { b } { rotatebox[origin=c]{180}{3} }
tl_use:N l_duodec_string_tl
}
ExplSyntaxOff

renewcommand{thepage}{basetwelve{arabic{page}}}
renewcommand{thepart}{basetwelve{arabic{part}}}
renewcommand{thechapter}{basetwelve{arabic{chapter}}}
% No problems so far...
% This is how you get numbering formatted as chapter.section:
renewcommand{thesection}{thechapter.basetwelve{arabic{section}}}
renewcommand{thesubsection}{thesection.basetwelve{arabic{subsection}}}
% Dont put thechapter here, it is already contained in thesection!!!
renewcommand{thefigure}{basetwelve{arabic{figure}}}
% As I told you, I wanted to change the figcaptions too.
% But I don't need the chapter's number here.
renewcommand{labelenumi}{basetwelve{arabic{enumi}}.}
% And this is my first dozenal enumeration with a dot behind the number.

%let's see, if it works:
begin{document}
part{Quick demonstration}
chapter{Here we go!}
Just scroll down...
chapter{I}
chapter{need}
chapter{lots}
Whoops, nearly there...
newpage
On this and on the following page you see the dozenal page numbers! index{dozenal page number}
chapter{of}
See? It works! index{working!}
chapter{pages}
chapter{and}
chapter{chapters}
chapter{for}
chapter{dozenal}
This is the dozenal number rotatebox[origin=c]{180}{2}, equal to $ 10_{(10)} $.
chapter{numbers.}
This is the second dozenal number: rotatebox[origin=c]{180}{3}, it is just a turned 3 and equal to $ 11_{(10)} $.
section{What are these symbols?!}
I use fonts like Times New Roman, they have symbols index{symbols} like rotatebox[origin=c]{180}{2} and rotatebox[origin=c]{180}{3} integrated as Unicode glyphs U+218A and U+218B. They are just rotated numbers too, basicly. These numbers are defined by the Dozenal Society of Great Britain and I like them. If you complie with XeLaTeX you can just copy and paste these signs: ↊ and ↋ (in this font they will probably be invisible).

section{Why so many chapters?}
I need more than 12 pages and chapters for the numbers index{numbers} rotatebox[origin=c]{180}{2} and rotatebox[origin=c]{180}{3} to appear.

section{Enumeration}
begin{enumerate}
item Just
item a
item very
item short
item demonstration
item of
item a
item dozenal
item enumeration
item for
item you
item to
item admire.
end{enumerate}
section{Just a random section}
subsection{with a subsection}
subsubsection{and a subsubsection}
These all work just finde with dozenal numbers aswell but I think the code is already long enough. And as you see, subsubsections usually don't have numbers at all.
printindex
end{document}









share|improve this question

























  • you should write the page numbers for makeindex in decimal so it can sort and handle ranges, just use duodecimal as a final print format when you print the numbers/

    – David Carlisle
    Jan 28 at 21:14













  • But this would show decimal page numbers in the printed index, right?

    – DonMeles
    Jan 28 at 21:15






  • 1





    no as I say print them in duodecimal, makindex can apply formatting to numbers so you can have them bold or italic or whatever in this case you want to fomat them something like duodecimal{12} to print the number twelve in duodecimal so that's typically appending |duodecimal to the index entry, depending on your makindex style.

    – David Carlisle
    Jan 28 at 21:17













  • When I open the .idx file one example entry is "indexentry{Fkeritandi}{basetwelve {17}}" which looks exactly how you said but it is not written in the .ind file anyway...

    – DonMeles
    Jan 28 at 21:25






  • 1





    no should be something like indexentry{Fkeritandi|basetwelve }{17} so that just a number appears in the final argument, makeindex can then use the number and will just move the |basetwelve to basetwelve{..} after it has finished sorting.

    – David Carlisle
    Jan 28 at 21:33
















1















I recently changed the page numbers to duodecimal ones (see here). The package makeidx didn't like that at all. In fact my index isn't written at all anymore:




done (0 entries accepted, 341 rejected). Nothing written in
Kyroledorn Yartolikor.ind. Transcript written in Kyroledorn
Yartolikor.ilg.




Everything worked before the change, so this is the only problem here. Other questions imply that makeidx has some restrictions regarding alterations in the page numbers but I didn't find a solution for this problem. Any ideas?



As a code example I added an index into the code sample from the question above, exactly as I did it in my other file.



documentclass[11pt,a4paper,final]{book}
usepackage[left=2cm,right=2cm,top=2cm,bottom=2cm]{geometry}
usepackage{makeidx}
makeindex
usepackage{graphicx} % I need this to rotate my numbers...
usepackage{xparse} % this is the magic package...
ExplSyntaxOn % for the missing numbers after 9 the package uses "a" and "b",
% but I want to use "↊" and "↋" as defined by the Dozenal
% Society of Great Britain. The following lines do that for me:

NewDocumentCommand{basetwelve}{m}
{ duodec_convert:n { #1 } }

tl_new:N l_duodec_string_tl
cs_new_protected:Npn duodec_convert:n #1
{
tl_set:Nx l_duodec_string_tl { int_to_base:nn { #1 } { 12 } }
tl_replace_all:Nnn l_duodec_string_tl { a } { rotatebox[origin=c]{180}{2} }
% I rotate the numbers, because standard fonts don't contain ↊ and ↋.
tl_replace_all:Nnn l_duodec_string_tl { b } { rotatebox[origin=c]{180}{3} }
tl_use:N l_duodec_string_tl
}
ExplSyntaxOff

renewcommand{thepage}{basetwelve{arabic{page}}}
renewcommand{thepart}{basetwelve{arabic{part}}}
renewcommand{thechapter}{basetwelve{arabic{chapter}}}
% No problems so far...
% This is how you get numbering formatted as chapter.section:
renewcommand{thesection}{thechapter.basetwelve{arabic{section}}}
renewcommand{thesubsection}{thesection.basetwelve{arabic{subsection}}}
% Dont put thechapter here, it is already contained in thesection!!!
renewcommand{thefigure}{basetwelve{arabic{figure}}}
% As I told you, I wanted to change the figcaptions too.
% But I don't need the chapter's number here.
renewcommand{labelenumi}{basetwelve{arabic{enumi}}.}
% And this is my first dozenal enumeration with a dot behind the number.

%let's see, if it works:
begin{document}
part{Quick demonstration}
chapter{Here we go!}
Just scroll down...
chapter{I}
chapter{need}
chapter{lots}
Whoops, nearly there...
newpage
On this and on the following page you see the dozenal page numbers! index{dozenal page number}
chapter{of}
See? It works! index{working!}
chapter{pages}
chapter{and}
chapter{chapters}
chapter{for}
chapter{dozenal}
This is the dozenal number rotatebox[origin=c]{180}{2}, equal to $ 10_{(10)} $.
chapter{numbers.}
This is the second dozenal number: rotatebox[origin=c]{180}{3}, it is just a turned 3 and equal to $ 11_{(10)} $.
section{What are these symbols?!}
I use fonts like Times New Roman, they have symbols index{symbols} like rotatebox[origin=c]{180}{2} and rotatebox[origin=c]{180}{3} integrated as Unicode glyphs U+218A and U+218B. They are just rotated numbers too, basicly. These numbers are defined by the Dozenal Society of Great Britain and I like them. If you complie with XeLaTeX you can just copy and paste these signs: ↊ and ↋ (in this font they will probably be invisible).

section{Why so many chapters?}
I need more than 12 pages and chapters for the numbers index{numbers} rotatebox[origin=c]{180}{2} and rotatebox[origin=c]{180}{3} to appear.

section{Enumeration}
begin{enumerate}
item Just
item a
item very
item short
item demonstration
item of
item a
item dozenal
item enumeration
item for
item you
item to
item admire.
end{enumerate}
section{Just a random section}
subsection{with a subsection}
subsubsection{and a subsubsection}
These all work just finde with dozenal numbers aswell but I think the code is already long enough. And as you see, subsubsections usually don't have numbers at all.
printindex
end{document}









share|improve this question

























  • you should write the page numbers for makeindex in decimal so it can sort and handle ranges, just use duodecimal as a final print format when you print the numbers/

    – David Carlisle
    Jan 28 at 21:14













  • But this would show decimal page numbers in the printed index, right?

    – DonMeles
    Jan 28 at 21:15






  • 1





    no as I say print them in duodecimal, makindex can apply formatting to numbers so you can have them bold or italic or whatever in this case you want to fomat them something like duodecimal{12} to print the number twelve in duodecimal so that's typically appending |duodecimal to the index entry, depending on your makindex style.

    – David Carlisle
    Jan 28 at 21:17













  • When I open the .idx file one example entry is "indexentry{Fkeritandi}{basetwelve {17}}" which looks exactly how you said but it is not written in the .ind file anyway...

    – DonMeles
    Jan 28 at 21:25






  • 1





    no should be something like indexentry{Fkeritandi|basetwelve }{17} so that just a number appears in the final argument, makeindex can then use the number and will just move the |basetwelve to basetwelve{..} after it has finished sorting.

    – David Carlisle
    Jan 28 at 21:33














1












1








1








I recently changed the page numbers to duodecimal ones (see here). The package makeidx didn't like that at all. In fact my index isn't written at all anymore:




done (0 entries accepted, 341 rejected). Nothing written in
Kyroledorn Yartolikor.ind. Transcript written in Kyroledorn
Yartolikor.ilg.




Everything worked before the change, so this is the only problem here. Other questions imply that makeidx has some restrictions regarding alterations in the page numbers but I didn't find a solution for this problem. Any ideas?



As a code example I added an index into the code sample from the question above, exactly as I did it in my other file.



documentclass[11pt,a4paper,final]{book}
usepackage[left=2cm,right=2cm,top=2cm,bottom=2cm]{geometry}
usepackage{makeidx}
makeindex
usepackage{graphicx} % I need this to rotate my numbers...
usepackage{xparse} % this is the magic package...
ExplSyntaxOn % for the missing numbers after 9 the package uses "a" and "b",
% but I want to use "↊" and "↋" as defined by the Dozenal
% Society of Great Britain. The following lines do that for me:

NewDocumentCommand{basetwelve}{m}
{ duodec_convert:n { #1 } }

tl_new:N l_duodec_string_tl
cs_new_protected:Npn duodec_convert:n #1
{
tl_set:Nx l_duodec_string_tl { int_to_base:nn { #1 } { 12 } }
tl_replace_all:Nnn l_duodec_string_tl { a } { rotatebox[origin=c]{180}{2} }
% I rotate the numbers, because standard fonts don't contain ↊ and ↋.
tl_replace_all:Nnn l_duodec_string_tl { b } { rotatebox[origin=c]{180}{3} }
tl_use:N l_duodec_string_tl
}
ExplSyntaxOff

renewcommand{thepage}{basetwelve{arabic{page}}}
renewcommand{thepart}{basetwelve{arabic{part}}}
renewcommand{thechapter}{basetwelve{arabic{chapter}}}
% No problems so far...
% This is how you get numbering formatted as chapter.section:
renewcommand{thesection}{thechapter.basetwelve{arabic{section}}}
renewcommand{thesubsection}{thesection.basetwelve{arabic{subsection}}}
% Dont put thechapter here, it is already contained in thesection!!!
renewcommand{thefigure}{basetwelve{arabic{figure}}}
% As I told you, I wanted to change the figcaptions too.
% But I don't need the chapter's number here.
renewcommand{labelenumi}{basetwelve{arabic{enumi}}.}
% And this is my first dozenal enumeration with a dot behind the number.

%let's see, if it works:
begin{document}
part{Quick demonstration}
chapter{Here we go!}
Just scroll down...
chapter{I}
chapter{need}
chapter{lots}
Whoops, nearly there...
newpage
On this and on the following page you see the dozenal page numbers! index{dozenal page number}
chapter{of}
See? It works! index{working!}
chapter{pages}
chapter{and}
chapter{chapters}
chapter{for}
chapter{dozenal}
This is the dozenal number rotatebox[origin=c]{180}{2}, equal to $ 10_{(10)} $.
chapter{numbers.}
This is the second dozenal number: rotatebox[origin=c]{180}{3}, it is just a turned 3 and equal to $ 11_{(10)} $.
section{What are these symbols?!}
I use fonts like Times New Roman, they have symbols index{symbols} like rotatebox[origin=c]{180}{2} and rotatebox[origin=c]{180}{3} integrated as Unicode glyphs U+218A and U+218B. They are just rotated numbers too, basicly. These numbers are defined by the Dozenal Society of Great Britain and I like them. If you complie with XeLaTeX you can just copy and paste these signs: ↊ and ↋ (in this font they will probably be invisible).

section{Why so many chapters?}
I need more than 12 pages and chapters for the numbers index{numbers} rotatebox[origin=c]{180}{2} and rotatebox[origin=c]{180}{3} to appear.

section{Enumeration}
begin{enumerate}
item Just
item a
item very
item short
item demonstration
item of
item a
item dozenal
item enumeration
item for
item you
item to
item admire.
end{enumerate}
section{Just a random section}
subsection{with a subsection}
subsubsection{and a subsubsection}
These all work just finde with dozenal numbers aswell but I think the code is already long enough. And as you see, subsubsections usually don't have numbers at all.
printindex
end{document}









share|improve this question
















I recently changed the page numbers to duodecimal ones (see here). The package makeidx didn't like that at all. In fact my index isn't written at all anymore:




done (0 entries accepted, 341 rejected). Nothing written in
Kyroledorn Yartolikor.ind. Transcript written in Kyroledorn
Yartolikor.ilg.




Everything worked before the change, so this is the only problem here. Other questions imply that makeidx has some restrictions regarding alterations in the page numbers but I didn't find a solution for this problem. Any ideas?



As a code example I added an index into the code sample from the question above, exactly as I did it in my other file.



documentclass[11pt,a4paper,final]{book}
usepackage[left=2cm,right=2cm,top=2cm,bottom=2cm]{geometry}
usepackage{makeidx}
makeindex
usepackage{graphicx} % I need this to rotate my numbers...
usepackage{xparse} % this is the magic package...
ExplSyntaxOn % for the missing numbers after 9 the package uses "a" and "b",
% but I want to use "↊" and "↋" as defined by the Dozenal
% Society of Great Britain. The following lines do that for me:

NewDocumentCommand{basetwelve}{m}
{ duodec_convert:n { #1 } }

tl_new:N l_duodec_string_tl
cs_new_protected:Npn duodec_convert:n #1
{
tl_set:Nx l_duodec_string_tl { int_to_base:nn { #1 } { 12 } }
tl_replace_all:Nnn l_duodec_string_tl { a } { rotatebox[origin=c]{180}{2} }
% I rotate the numbers, because standard fonts don't contain ↊ and ↋.
tl_replace_all:Nnn l_duodec_string_tl { b } { rotatebox[origin=c]{180}{3} }
tl_use:N l_duodec_string_tl
}
ExplSyntaxOff

renewcommand{thepage}{basetwelve{arabic{page}}}
renewcommand{thepart}{basetwelve{arabic{part}}}
renewcommand{thechapter}{basetwelve{arabic{chapter}}}
% No problems so far...
% This is how you get numbering formatted as chapter.section:
renewcommand{thesection}{thechapter.basetwelve{arabic{section}}}
renewcommand{thesubsection}{thesection.basetwelve{arabic{subsection}}}
% Dont put thechapter here, it is already contained in thesection!!!
renewcommand{thefigure}{basetwelve{arabic{figure}}}
% As I told you, I wanted to change the figcaptions too.
% But I don't need the chapter's number here.
renewcommand{labelenumi}{basetwelve{arabic{enumi}}.}
% And this is my first dozenal enumeration with a dot behind the number.

%let's see, if it works:
begin{document}
part{Quick demonstration}
chapter{Here we go!}
Just scroll down...
chapter{I}
chapter{need}
chapter{lots}
Whoops, nearly there...
newpage
On this and on the following page you see the dozenal page numbers! index{dozenal page number}
chapter{of}
See? It works! index{working!}
chapter{pages}
chapter{and}
chapter{chapters}
chapter{for}
chapter{dozenal}
This is the dozenal number rotatebox[origin=c]{180}{2}, equal to $ 10_{(10)} $.
chapter{numbers.}
This is the second dozenal number: rotatebox[origin=c]{180}{3}, it is just a turned 3 and equal to $ 11_{(10)} $.
section{What are these symbols?!}
I use fonts like Times New Roman, they have symbols index{symbols} like rotatebox[origin=c]{180}{2} and rotatebox[origin=c]{180}{3} integrated as Unicode glyphs U+218A and U+218B. They are just rotated numbers too, basicly. These numbers are defined by the Dozenal Society of Great Britain and I like them. If you complie with XeLaTeX you can just copy and paste these signs: ↊ and ↋ (in this font they will probably be invisible).

section{Why so many chapters?}
I need more than 12 pages and chapters for the numbers index{numbers} rotatebox[origin=c]{180}{2} and rotatebox[origin=c]{180}{3} to appear.

section{Enumeration}
begin{enumerate}
item Just
item a
item very
item short
item demonstration
item of
item a
item dozenal
item enumeration
item for
item you
item to
item admire.
end{enumerate}
section{Just a random section}
subsection{with a subsection}
subsubsection{and a subsubsection}
These all work just finde with dozenal numbers aswell but I think the code is already long enough. And as you see, subsubsections usually don't have numbers at all.
printindex
end{document}






xetex page-numbering makeindex






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jan 28 at 22:00







DonMeles

















asked Jan 28 at 21:05









DonMelesDonMeles

438




438













  • you should write the page numbers for makeindex in decimal so it can sort and handle ranges, just use duodecimal as a final print format when you print the numbers/

    – David Carlisle
    Jan 28 at 21:14













  • But this would show decimal page numbers in the printed index, right?

    – DonMeles
    Jan 28 at 21:15






  • 1





    no as I say print them in duodecimal, makindex can apply formatting to numbers so you can have them bold or italic or whatever in this case you want to fomat them something like duodecimal{12} to print the number twelve in duodecimal so that's typically appending |duodecimal to the index entry, depending on your makindex style.

    – David Carlisle
    Jan 28 at 21:17













  • When I open the .idx file one example entry is "indexentry{Fkeritandi}{basetwelve {17}}" which looks exactly how you said but it is not written in the .ind file anyway...

    – DonMeles
    Jan 28 at 21:25






  • 1





    no should be something like indexentry{Fkeritandi|basetwelve }{17} so that just a number appears in the final argument, makeindex can then use the number and will just move the |basetwelve to basetwelve{..} after it has finished sorting.

    – David Carlisle
    Jan 28 at 21:33



















  • you should write the page numbers for makeindex in decimal so it can sort and handle ranges, just use duodecimal as a final print format when you print the numbers/

    – David Carlisle
    Jan 28 at 21:14













  • But this would show decimal page numbers in the printed index, right?

    – DonMeles
    Jan 28 at 21:15






  • 1





    no as I say print them in duodecimal, makindex can apply formatting to numbers so you can have them bold or italic or whatever in this case you want to fomat them something like duodecimal{12} to print the number twelve in duodecimal so that's typically appending |duodecimal to the index entry, depending on your makindex style.

    – David Carlisle
    Jan 28 at 21:17













  • When I open the .idx file one example entry is "indexentry{Fkeritandi}{basetwelve {17}}" which looks exactly how you said but it is not written in the .ind file anyway...

    – DonMeles
    Jan 28 at 21:25






  • 1





    no should be something like indexentry{Fkeritandi|basetwelve }{17} so that just a number appears in the final argument, makeindex can then use the number and will just move the |basetwelve to basetwelve{..} after it has finished sorting.

    – David Carlisle
    Jan 28 at 21:33

















you should write the page numbers for makeindex in decimal so it can sort and handle ranges, just use duodecimal as a final print format when you print the numbers/

– David Carlisle
Jan 28 at 21:14







you should write the page numbers for makeindex in decimal so it can sort and handle ranges, just use duodecimal as a final print format when you print the numbers/

– David Carlisle
Jan 28 at 21:14















But this would show decimal page numbers in the printed index, right?

– DonMeles
Jan 28 at 21:15





But this would show decimal page numbers in the printed index, right?

– DonMeles
Jan 28 at 21:15




1




1





no as I say print them in duodecimal, makindex can apply formatting to numbers so you can have them bold or italic or whatever in this case you want to fomat them something like duodecimal{12} to print the number twelve in duodecimal so that's typically appending |duodecimal to the index entry, depending on your makindex style.

– David Carlisle
Jan 28 at 21:17







no as I say print them in duodecimal, makindex can apply formatting to numbers so you can have them bold or italic or whatever in this case you want to fomat them something like duodecimal{12} to print the number twelve in duodecimal so that's typically appending |duodecimal to the index entry, depending on your makindex style.

– David Carlisle
Jan 28 at 21:17















When I open the .idx file one example entry is "indexentry{Fkeritandi}{basetwelve {17}}" which looks exactly how you said but it is not written in the .ind file anyway...

– DonMeles
Jan 28 at 21:25





When I open the .idx file one example entry is "indexentry{Fkeritandi}{basetwelve {17}}" which looks exactly how you said but it is not written in the .ind file anyway...

– DonMeles
Jan 28 at 21:25




1




1





no should be something like indexentry{Fkeritandi|basetwelve }{17} so that just a number appears in the final argument, makeindex can then use the number and will just move the |basetwelve to basetwelve{..} after it has finished sorting.

– David Carlisle
Jan 28 at 21:33





no should be something like indexentry{Fkeritandi|basetwelve }{17} so that just a number appears in the final argument, makeindex can then use the number and will just move the |basetwelve to basetwelve{..} after it has finished sorting.

– David Carlisle
Jan 28 at 21:33










0






active

oldest

votes











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%2f472304%2fmakeindex-entries-rejected-because-of-duodecimal-page-numbers%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes
















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%2f472304%2fmakeindex-entries-rejected-because-of-duodecimal-page-numbers%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

Biblatex bibliography style without URLs when DOI exists (in Overleaf with Zotero bibliography)

ComboBox Display Member on multiple fields

Is it possible to collect Nectar points via Trainline?