Siunitx does not let me use letter e











up vote
4
down vote

favorite












I am using siunitx to align the decimals in a table. The problem is that for some reason the it does not let me input the letter e. Other letters, such as a are fine.



Here is the code I am using.



usepackage{multirow}
usepackage[detect-all]{siunitx}

begin{table}
begin{tabular}{@{}c S[table-format=2.1] S[table-format=2.1] @{}}

header & a & e \
a & 32.4 & 12.2 \
c & 0.1 & 3.4 \

end{tabular}
end{table}


Here is what I get. I was expecting to see both a and e in the header row. However, I only get a.



Letter e does not appear in the table header.



The only error message I get is Invalid numerical input 'e'. How to fix this? Thanks!










share|improve this question


















  • 3




    Use {a} and {e} in the header.
    – egreg
    Nov 18 at 10:48










  • Wow, that works. If you write an answer, I'll accept it.
    – rkioji
    Nov 18 at 10:49






  • 1




    Escape all non-numeric input in Scolumns with braces: header & {a} & {e} \.
    – moewe
    Nov 18 at 10:50

















up vote
4
down vote

favorite












I am using siunitx to align the decimals in a table. The problem is that for some reason the it does not let me input the letter e. Other letters, such as a are fine.



Here is the code I am using.



usepackage{multirow}
usepackage[detect-all]{siunitx}

begin{table}
begin{tabular}{@{}c S[table-format=2.1] S[table-format=2.1] @{}}

header & a & e \
a & 32.4 & 12.2 \
c & 0.1 & 3.4 \

end{tabular}
end{table}


Here is what I get. I was expecting to see both a and e in the header row. However, I only get a.



Letter e does not appear in the table header.



The only error message I get is Invalid numerical input 'e'. How to fix this? Thanks!










share|improve this question


















  • 3




    Use {a} and {e} in the header.
    – egreg
    Nov 18 at 10:48










  • Wow, that works. If you write an answer, I'll accept it.
    – rkioji
    Nov 18 at 10:49






  • 1




    Escape all non-numeric input in Scolumns with braces: header & {a} & {e} \.
    – moewe
    Nov 18 at 10:50















up vote
4
down vote

favorite









up vote
4
down vote

favorite











I am using siunitx to align the decimals in a table. The problem is that for some reason the it does not let me input the letter e. Other letters, such as a are fine.



Here is the code I am using.



usepackage{multirow}
usepackage[detect-all]{siunitx}

begin{table}
begin{tabular}{@{}c S[table-format=2.1] S[table-format=2.1] @{}}

header & a & e \
a & 32.4 & 12.2 \
c & 0.1 & 3.4 \

end{tabular}
end{table}


Here is what I get. I was expecting to see both a and e in the header row. However, I only get a.



Letter e does not appear in the table header.



The only error message I get is Invalid numerical input 'e'. How to fix this? Thanks!










share|improve this question













I am using siunitx to align the decimals in a table. The problem is that for some reason the it does not let me input the letter e. Other letters, such as a are fine.



Here is the code I am using.



usepackage{multirow}
usepackage[detect-all]{siunitx}

begin{table}
begin{tabular}{@{}c S[table-format=2.1] S[table-format=2.1] @{}}

header & a & e \
a & 32.4 & 12.2 \
c & 0.1 & 3.4 \

end{tabular}
end{table}


Here is what I get. I was expecting to see both a and e in the header row. However, I only get a.



Letter e does not appear in the table header.



The only error message I get is Invalid numerical input 'e'. How to fix this? Thanks!







tables






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 18 at 10:47









rkioji

20918




20918








  • 3




    Use {a} and {e} in the header.
    – egreg
    Nov 18 at 10:48










  • Wow, that works. If you write an answer, I'll accept it.
    – rkioji
    Nov 18 at 10:49






  • 1




    Escape all non-numeric input in Scolumns with braces: header & {a} & {e} \.
    – moewe
    Nov 18 at 10:50
















  • 3




    Use {a} and {e} in the header.
    – egreg
    Nov 18 at 10:48










  • Wow, that works. If you write an answer, I'll accept it.
    – rkioji
    Nov 18 at 10:49






  • 1




    Escape all non-numeric input in Scolumns with braces: header & {a} & {e} \.
    – moewe
    Nov 18 at 10:50










3




3




Use {a} and {e} in the header.
– egreg
Nov 18 at 10:48




Use {a} and {e} in the header.
– egreg
Nov 18 at 10:48












Wow, that works. If you write an answer, I'll accept it.
– rkioji
Nov 18 at 10:49




Wow, that works. If you write an answer, I'll accept it.
– rkioji
Nov 18 at 10:49




1




1




Escape all non-numeric input in Scolumns with braces: header & {a} & {e} \.
– moewe
Nov 18 at 10:50






Escape all non-numeric input in Scolumns with braces: header & {a} & {e} \.
– moewe
Nov 18 at 10:50












1 Answer
1






active

oldest

votes

















up vote
4
down vote



accepted










siunitx parses the contents of a column of type S unless the option parse-numbers=false was set -- which isn't the case in the code snippet you posted. For this reason, the letters d, e, and j will cause a crash unless they're encountered in numeric expressions such as 1e5, 2d7, or -j. (In the third example, j is taken to be a way to encode the imaginary number, aka i.) Depending on the circumstances, the letter g can also be interpreted to have a special meaning.



siunitx has become smart enough in recent years to be able to figure out that inputs such as cat and fly cannot possibly represent numbers and hence should be treated as pure text. This smartness is, incidentally, the reason why a in one of the cells of your code snippet doesn't cause a problem. However, since it isn't all that challenging to write {cat} and {fly}, do make a habit of encasing non-numeric terms -- they occur rather frequently in the header cell(s) of S columns... -- in curly braces. That way, you're sure to have eliminated all uncertainty about how text in header cells should be processed.






share|improve this answer





















    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',
    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%2f460570%2fsiunitx-does-not-let-me-use-letter-e%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








    up vote
    4
    down vote



    accepted










    siunitx parses the contents of a column of type S unless the option parse-numbers=false was set -- which isn't the case in the code snippet you posted. For this reason, the letters d, e, and j will cause a crash unless they're encountered in numeric expressions such as 1e5, 2d7, or -j. (In the third example, j is taken to be a way to encode the imaginary number, aka i.) Depending on the circumstances, the letter g can also be interpreted to have a special meaning.



    siunitx has become smart enough in recent years to be able to figure out that inputs such as cat and fly cannot possibly represent numbers and hence should be treated as pure text. This smartness is, incidentally, the reason why a in one of the cells of your code snippet doesn't cause a problem. However, since it isn't all that challenging to write {cat} and {fly}, do make a habit of encasing non-numeric terms -- they occur rather frequently in the header cell(s) of S columns... -- in curly braces. That way, you're sure to have eliminated all uncertainty about how text in header cells should be processed.






    share|improve this answer

























      up vote
      4
      down vote



      accepted










      siunitx parses the contents of a column of type S unless the option parse-numbers=false was set -- which isn't the case in the code snippet you posted. For this reason, the letters d, e, and j will cause a crash unless they're encountered in numeric expressions such as 1e5, 2d7, or -j. (In the third example, j is taken to be a way to encode the imaginary number, aka i.) Depending on the circumstances, the letter g can also be interpreted to have a special meaning.



      siunitx has become smart enough in recent years to be able to figure out that inputs such as cat and fly cannot possibly represent numbers and hence should be treated as pure text. This smartness is, incidentally, the reason why a in one of the cells of your code snippet doesn't cause a problem. However, since it isn't all that challenging to write {cat} and {fly}, do make a habit of encasing non-numeric terms -- they occur rather frequently in the header cell(s) of S columns... -- in curly braces. That way, you're sure to have eliminated all uncertainty about how text in header cells should be processed.






      share|improve this answer























        up vote
        4
        down vote



        accepted







        up vote
        4
        down vote



        accepted






        siunitx parses the contents of a column of type S unless the option parse-numbers=false was set -- which isn't the case in the code snippet you posted. For this reason, the letters d, e, and j will cause a crash unless they're encountered in numeric expressions such as 1e5, 2d7, or -j. (In the third example, j is taken to be a way to encode the imaginary number, aka i.) Depending on the circumstances, the letter g can also be interpreted to have a special meaning.



        siunitx has become smart enough in recent years to be able to figure out that inputs such as cat and fly cannot possibly represent numbers and hence should be treated as pure text. This smartness is, incidentally, the reason why a in one of the cells of your code snippet doesn't cause a problem. However, since it isn't all that challenging to write {cat} and {fly}, do make a habit of encasing non-numeric terms -- they occur rather frequently in the header cell(s) of S columns... -- in curly braces. That way, you're sure to have eliminated all uncertainty about how text in header cells should be processed.






        share|improve this answer












        siunitx parses the contents of a column of type S unless the option parse-numbers=false was set -- which isn't the case in the code snippet you posted. For this reason, the letters d, e, and j will cause a crash unless they're encountered in numeric expressions such as 1e5, 2d7, or -j. (In the third example, j is taken to be a way to encode the imaginary number, aka i.) Depending on the circumstances, the letter g can also be interpreted to have a special meaning.



        siunitx has become smart enough in recent years to be able to figure out that inputs such as cat and fly cannot possibly represent numbers and hence should be treated as pure text. This smartness is, incidentally, the reason why a in one of the cells of your code snippet doesn't cause a problem. However, since it isn't all that challenging to write {cat} and {fly}, do make a habit of encasing non-numeric terms -- they occur rather frequently in the header cell(s) of S columns... -- in curly braces. That way, you're sure to have eliminated all uncertainty about how text in header cells should be processed.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 18 at 11:17









        Mico

        269k30367751




        269k30367751






























             

            draft saved


            draft discarded



















































             


            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f460570%2fsiunitx-does-not-let-me-use-letter-e%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?