Why do the less than symbol () appear wrong as upside down exclamation (¡) or question mark (¿)?











up vote
219
down vote

favorite
50












When typing < or > in LaTeX and compiling with pdflatex, the less than and greater than symbols appear at upside down exclamation points. I'm not in math mode.






symbols punctuation font-encodings







share|improve this question
























  • using it in a regression results table in a paper.
    – biased_estimator
    Aug 28 '10 at 2:44










  • @ShreevatsaR: "This example holds true for all cases where n >= 3".
    – SabreWolfy
    Feb 2 '12 at 13:02










  • see also beramono and texttt : angle brackets show as inverted exclamation mark and inverted question mark symbols (upside-down signs, like in spanish) for a font-specific answer with bera mono
    – barbara beeton
    Feb 10 '16 at 17:08












  • Worth noting that you can also use modern OpenType or TrueType fonts, in either LuaLaTeX or XeLaTeX, with the fontspec package. In this case, you do not want to load the T1 encoding. The encodings will already be set up properly.
    – Davislor
    Oct 6 at 19:21

















up vote
219
down vote

favorite
50












When typing < or > in LaTeX and compiling with pdflatex, the less than and greater than symbols appear at upside down exclamation points. I'm not in math mode.






symbols punctuation font-encodings







share|improve this question
























  • using it in a regression results table in a paper.
    – biased_estimator
    Aug 28 '10 at 2:44










  • @ShreevatsaR: "This example holds true for all cases where n >= 3".
    – SabreWolfy
    Feb 2 '12 at 13:02










  • see also beramono and texttt : angle brackets show as inverted exclamation mark and inverted question mark symbols (upside-down signs, like in spanish) for a font-specific answer with bera mono
    – barbara beeton
    Feb 10 '16 at 17:08












  • Worth noting that you can also use modern OpenType or TrueType fonts, in either LuaLaTeX or XeLaTeX, with the fontspec package. In this case, you do not want to load the T1 encoding. The encodings will already be set up properly.
    – Davislor
    Oct 6 at 19:21















up vote
219
down vote

favorite
50









up vote
219
down vote

favorite
50






50





When typing < or > in LaTeX and compiling with pdflatex, the less than and greater than symbols appear at upside down exclamation points. I'm not in math mode.






symbols punctuation font-encodings







share|improve this question















When typing < or > in LaTeX and compiling with pdflatex, the less than and greater than symbols appear at upside down exclamation points. I'm not in math mode.






symbols punctuation font-encodings




symbols punctuation font-encodings






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Aug 6 '13 at 8:17









lockstep

189k52584718




189k52584718










asked Aug 26 '10 at 19:18









biased_estimator

1,198284




1,198284












  • using it in a regression results table in a paper.
    – biased_estimator
    Aug 28 '10 at 2:44










  • @ShreevatsaR: "This example holds true for all cases where n >= 3".
    – SabreWolfy
    Feb 2 '12 at 13:02










  • see also beramono and texttt : angle brackets show as inverted exclamation mark and inverted question mark symbols (upside-down signs, like in spanish) for a font-specific answer with bera mono
    – barbara beeton
    Feb 10 '16 at 17:08












  • Worth noting that you can also use modern OpenType or TrueType fonts, in either LuaLaTeX or XeLaTeX, with the fontspec package. In this case, you do not want to load the T1 encoding. The encodings will already be set up properly.
    – Davislor
    Oct 6 at 19:21




















  • using it in a regression results table in a paper.
    – biased_estimator
    Aug 28 '10 at 2:44










  • @ShreevatsaR: "This example holds true for all cases where n >= 3".
    – SabreWolfy
    Feb 2 '12 at 13:02










  • see also beramono and texttt : angle brackets show as inverted exclamation mark and inverted question mark symbols (upside-down signs, like in spanish) for a font-specific answer with bera mono
    – barbara beeton
    Feb 10 '16 at 17:08












  • Worth noting that you can also use modern OpenType or TrueType fonts, in either LuaLaTeX or XeLaTeX, with the fontspec package. In this case, you do not want to load the T1 encoding. The encodings will already be set up properly.
    – Davislor
    Oct 6 at 19:21


















using it in a regression results table in a paper.
– biased_estimator
Aug 28 '10 at 2:44




using it in a regression results table in a paper.
– biased_estimator
Aug 28 '10 at 2:44












@ShreevatsaR: "This example holds true for all cases where n >= 3".
– SabreWolfy
Feb 2 '12 at 13:02




@ShreevatsaR: "This example holds true for all cases where n >= 3".
– SabreWolfy
Feb 2 '12 at 13:02












see also beramono and texttt : angle brackets show as inverted exclamation mark and inverted question mark symbols (upside-down signs, like in spanish) for a font-specific answer with bera mono
– barbara beeton
Feb 10 '16 at 17:08






see also beramono and texttt : angle brackets show as inverted exclamation mark and inverted question mark symbols (upside-down signs, like in spanish) for a font-specific answer with bera mono
– barbara beeton
Feb 10 '16 at 17:08














Worth noting that you can also use modern OpenType or TrueType fonts, in either LuaLaTeX or XeLaTeX, with the fontspec package. In this case, you do not want to load the T1 encoding. The encodings will already be set up properly.
– Davislor
Oct 6 at 19:21






Worth noting that you can also use modern OpenType or TrueType fonts, in either LuaLaTeX or XeLaTeX, with the fontspec package. In this case, you do not want to load the T1 encoding. The encodings will already be set up properly.
– Davislor
Oct 6 at 19:21












4 Answers
4






active

oldest

votes

















up vote
189
down vote



accepted










Geoffs tip with textless and textgreater will work well for you. However, you could type these symbols < and > directly in your editor and they would be correctly printed if you use the recommended font encoding, Cork resp. T1:



usepackage[T1]{fontenc}


Have a look at the T1 encoding table, search for the symbols < and >. Afterwards, open the OT1 encoding table, which is the default. At the two corresponding places you will find the upside down exclamation resp. quotation mark. That should explain it.



For further reasons, why you should use T1 encoding, have a look at this question: Why should I use usepackage[T1]{fontenc}?



You should use a font supporting T1. For instance use the very good Latin Modern font, derived from the standard fonts:



usepackage{lmodern}


Or install the cm-super package which provides the standard Computer Modern fonts with T1 support.






share|improve this answer



















  • 2




    Further reading: Latin Modern vs cm-super?
    – doncherry
    Jan 31 '13 at 6:46










  • will this screw up any other part of the document?
    – Hao Sun
    Jun 13 '16 at 20:52






  • 1




    @HaoSun It's an improvement. If something would change that you don't desire, it can be fixed. If you don't want any change, just don't change.
    – Stefan Kottwitz♦
    Jun 13 '16 at 22:24


















up vote
86
down vote













Use textless and textgreater.






share|improve this answer

















  • 8




    unless they are part of a math expression, in which case they should be between dollar signs or ( ... ) along with the rest of the math expression.
    – barbara beeton
    Aug 26 '10 at 19:51


















up vote
17
down vote













What I usually do is just enter mathmode to type them, e.g. This object is $<$ that object.






share|improve this answer

















  • 17




    That is generally considered poor style. You should just write out "This object is less than that object." Occasionally, you'll see "foo is <0." This looks bad.
    – TH.
    Aug 27 '10 at 23:32








  • 10




    That's definitely true. However, if you're using LaTeX to organize your thoughts (as i often do), 'good style' equates to 'will I understand what I wrote if I come back and look at it in a week'!
    – Avi Steiner
    Sep 3 '10 at 3:30










  • @TH.: I agree with you. My experiency tells me too that text and math code should not be mixed up. Good style would be either writing "The variable $foo$ is less than zero." (as you mentioned) or "The variable $foo$ satisfies the relation/condition $foo<0$.", which would probably suit your application. Good style means also to define variables at the first use.
    – strpeter
    Dec 7 '13 at 8:07






  • 1




    @strpeter While mentioning style, it is worth noting that variable $foo$ is not good style either: it refers to the product of $f$, $o$, and $o$. You mean variable $mathit{foo}$.
    – akim
    Dec 8 '14 at 9:19










  • OK, I was not typing it correct in the sense of the variable as I focused on the operator. You're right - use your preferred version $mathit{foo}<0$, $mathrm{foo}<0$, $mathbf{foo}<0$, or whatever variable. ;)
    – strpeter
    Dec 8 '14 at 10:40


















up vote
15
down vote













May be using some other sane font encoding, something like usepackage[T1]{fontenc} or something. (Well, I don't think any of this legacy font encoding and input encoding is sane any way).






share|improve this answer




















    protected by percusse Mar 28 '16 at 17:08



    Thank you for your interest in this question.
    Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).



    Would you like to answer one of these unanswered questions instead?














    4 Answers
    4






    active

    oldest

    votes








    4 Answers
    4






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes








    up vote
    189
    down vote



    accepted










    Geoffs tip with textless and textgreater will work well for you. However, you could type these symbols < and > directly in your editor and they would be correctly printed if you use the recommended font encoding, Cork resp. T1:



    usepackage[T1]{fontenc}


    Have a look at the T1 encoding table, search for the symbols < and >. Afterwards, open the OT1 encoding table, which is the default. At the two corresponding places you will find the upside down exclamation resp. quotation mark. That should explain it.



    For further reasons, why you should use T1 encoding, have a look at this question: Why should I use usepackage[T1]{fontenc}?



    You should use a font supporting T1. For instance use the very good Latin Modern font, derived from the standard fonts:



    usepackage{lmodern}


    Or install the cm-super package which provides the standard Computer Modern fonts with T1 support.






    share|improve this answer



















    • 2




      Further reading: Latin Modern vs cm-super?
      – doncherry
      Jan 31 '13 at 6:46










    • will this screw up any other part of the document?
      – Hao Sun
      Jun 13 '16 at 20:52






    • 1




      @HaoSun It's an improvement. If something would change that you don't desire, it can be fixed. If you don't want any change, just don't change.
      – Stefan Kottwitz♦
      Jun 13 '16 at 22:24















    up vote
    189
    down vote



    accepted










    Geoffs tip with textless and textgreater will work well for you. However, you could type these symbols < and > directly in your editor and they would be correctly printed if you use the recommended font encoding, Cork resp. T1:



    usepackage[T1]{fontenc}


    Have a look at the T1 encoding table, search for the symbols < and >. Afterwards, open the OT1 encoding table, which is the default. At the two corresponding places you will find the upside down exclamation resp. quotation mark. That should explain it.



    For further reasons, why you should use T1 encoding, have a look at this question: Why should I use usepackage[T1]{fontenc}?



    You should use a font supporting T1. For instance use the very good Latin Modern font, derived from the standard fonts:



    usepackage{lmodern}


    Or install the cm-super package which provides the standard Computer Modern fonts with T1 support.






    share|improve this answer



















    • 2




      Further reading: Latin Modern vs cm-super?
      – doncherry
      Jan 31 '13 at 6:46










    • will this screw up any other part of the document?
      – Hao Sun
      Jun 13 '16 at 20:52






    • 1




      @HaoSun It's an improvement. If something would change that you don't desire, it can be fixed. If you don't want any change, just don't change.
      – Stefan Kottwitz♦
      Jun 13 '16 at 22:24













    up vote
    189
    down vote



    accepted







    up vote
    189
    down vote



    accepted






    Geoffs tip with textless and textgreater will work well for you. However, you could type these symbols < and > directly in your editor and they would be correctly printed if you use the recommended font encoding, Cork resp. T1:



    usepackage[T1]{fontenc}


    Have a look at the T1 encoding table, search for the symbols < and >. Afterwards, open the OT1 encoding table, which is the default. At the two corresponding places you will find the upside down exclamation resp. quotation mark. That should explain it.



    For further reasons, why you should use T1 encoding, have a look at this question: Why should I use usepackage[T1]{fontenc}?



    You should use a font supporting T1. For instance use the very good Latin Modern font, derived from the standard fonts:



    usepackage{lmodern}


    Or install the cm-super package which provides the standard Computer Modern fonts with T1 support.






    share|improve this answer














    Geoffs tip with textless and textgreater will work well for you. However, you could type these symbols < and > directly in your editor and they would be correctly printed if you use the recommended font encoding, Cork resp. T1:



    usepackage[T1]{fontenc}


    Have a look at the T1 encoding table, search for the symbols < and >. Afterwards, open the OT1 encoding table, which is the default. At the two corresponding places you will find the upside down exclamation resp. quotation mark. That should explain it.



    For further reasons, why you should use T1 encoding, have a look at this question: Why should I use usepackage[T1]{fontenc}?



    You should use a font supporting T1. For instance use the very good Latin Modern font, derived from the standard fonts:



    usepackage{lmodern}


    Or install the cm-super package which provides the standard Computer Modern fonts with T1 support.







    share|improve this answer














    share|improve this answer



    share|improve this answer








    edited Apr 13 '17 at 12:35









    Community♦

    1




    1










    answered Aug 26 '10 at 20:30









    Stefan Kottwitz♦

    174k63566754




    174k63566754








    • 2




      Further reading: Latin Modern vs cm-super?
      – doncherry
      Jan 31 '13 at 6:46










    • will this screw up any other part of the document?
      – Hao Sun
      Jun 13 '16 at 20:52






    • 1




      @HaoSun It's an improvement. If something would change that you don't desire, it can be fixed. If you don't want any change, just don't change.
      – Stefan Kottwitz♦
      Jun 13 '16 at 22:24














    • 2




      Further reading: Latin Modern vs cm-super?
      – doncherry
      Jan 31 '13 at 6:46










    • will this screw up any other part of the document?
      – Hao Sun
      Jun 13 '16 at 20:52






    • 1




      @HaoSun It's an improvement. If something would change that you don't desire, it can be fixed. If you don't want any change, just don't change.
      – Stefan Kottwitz♦
      Jun 13 '16 at 22:24








    2




    2




    Further reading: Latin Modern vs cm-super?
    – doncherry
    Jan 31 '13 at 6:46




    Further reading: Latin Modern vs cm-super?
    – doncherry
    Jan 31 '13 at 6:46












    will this screw up any other part of the document?
    – Hao Sun
    Jun 13 '16 at 20:52




    will this screw up any other part of the document?
    – Hao Sun
    Jun 13 '16 at 20:52




    1




    1




    @HaoSun It's an improvement. If something would change that you don't desire, it can be fixed. If you don't want any change, just don't change.
    – Stefan Kottwitz♦
    Jun 13 '16 at 22:24




    @HaoSun It's an improvement. If something would change that you don't desire, it can be fixed. If you don't want any change, just don't change.
    – Stefan Kottwitz♦
    Jun 13 '16 at 22:24










    up vote
    86
    down vote













    Use textless and textgreater.






    share|improve this answer

















    • 8




      unless they are part of a math expression, in which case they should be between dollar signs or ( ... ) along with the rest of the math expression.
      – barbara beeton
      Aug 26 '10 at 19:51















    up vote
    86
    down vote













    Use textless and textgreater.






    share|improve this answer

















    • 8




      unless they are part of a math expression, in which case they should be between dollar signs or ( ... ) along with the rest of the math expression.
      – barbara beeton
      Aug 26 '10 at 19:51













    up vote
    86
    down vote










    up vote
    86
    down vote









    Use textless and textgreater.






    share|improve this answer












    Use textless and textgreater.







    share|improve this answer












    share|improve this answer



    share|improve this answer










    answered Aug 26 '10 at 19:24









    Geoff

    1,92121214




    1,92121214








    • 8




      unless they are part of a math expression, in which case they should be between dollar signs or ( ... ) along with the rest of the math expression.
      – barbara beeton
      Aug 26 '10 at 19:51














    • 8




      unless they are part of a math expression, in which case they should be between dollar signs or ( ... ) along with the rest of the math expression.
      – barbara beeton
      Aug 26 '10 at 19:51








    8




    8




    unless they are part of a math expression, in which case they should be between dollar signs or ( ... ) along with the rest of the math expression.
    – barbara beeton
    Aug 26 '10 at 19:51




    unless they are part of a math expression, in which case they should be between dollar signs or ( ... ) along with the rest of the math expression.
    – barbara beeton
    Aug 26 '10 at 19:51










    up vote
    17
    down vote













    What I usually do is just enter mathmode to type them, e.g. This object is $<$ that object.






    share|improve this answer

















    • 17




      That is generally considered poor style. You should just write out "This object is less than that object." Occasionally, you'll see "foo is <0." This looks bad.
      – TH.
      Aug 27 '10 at 23:32








    • 10




      That's definitely true. However, if you're using LaTeX to organize your thoughts (as i often do), 'good style' equates to 'will I understand what I wrote if I come back and look at it in a week'!
      – Avi Steiner
      Sep 3 '10 at 3:30










    • @TH.: I agree with you. My experiency tells me too that text and math code should not be mixed up. Good style would be either writing "The variable $foo$ is less than zero." (as you mentioned) or "The variable $foo$ satisfies the relation/condition $foo<0$.", which would probably suit your application. Good style means also to define variables at the first use.
      – strpeter
      Dec 7 '13 at 8:07






    • 1




      @strpeter While mentioning style, it is worth noting that variable $foo$ is not good style either: it refers to the product of $f$, $o$, and $o$. You mean variable $mathit{foo}$.
      – akim
      Dec 8 '14 at 9:19










    • OK, I was not typing it correct in the sense of the variable as I focused on the operator. You're right - use your preferred version $mathit{foo}<0$, $mathrm{foo}<0$, $mathbf{foo}<0$, or whatever variable. ;)
      – strpeter
      Dec 8 '14 at 10:40















    up vote
    17
    down vote













    What I usually do is just enter mathmode to type them, e.g. This object is $<$ that object.






    share|improve this answer

















    • 17




      That is generally considered poor style. You should just write out "This object is less than that object." Occasionally, you'll see "foo is <0." This looks bad.
      – TH.
      Aug 27 '10 at 23:32








    • 10




      That's definitely true. However, if you're using LaTeX to organize your thoughts (as i often do), 'good style' equates to 'will I understand what I wrote if I come back and look at it in a week'!
      – Avi Steiner
      Sep 3 '10 at 3:30










    • @TH.: I agree with you. My experiency tells me too that text and math code should not be mixed up. Good style would be either writing "The variable $foo$ is less than zero." (as you mentioned) or "The variable $foo$ satisfies the relation/condition $foo<0$.", which would probably suit your application. Good style means also to define variables at the first use.
      – strpeter
      Dec 7 '13 at 8:07






    • 1




      @strpeter While mentioning style, it is worth noting that variable $foo$ is not good style either: it refers to the product of $f$, $o$, and $o$. You mean variable $mathit{foo}$.
      – akim
      Dec 8 '14 at 9:19










    • OK, I was not typing it correct in the sense of the variable as I focused on the operator. You're right - use your preferred version $mathit{foo}<0$, $mathrm{foo}<0$, $mathbf{foo}<0$, or whatever variable. ;)
      – strpeter
      Dec 8 '14 at 10:40













    up vote
    17
    down vote










    up vote
    17
    down vote









    What I usually do is just enter mathmode to type them, e.g. This object is $<$ that object.






    share|improve this answer












    What I usually do is just enter mathmode to type them, e.g. This object is $<$ that object.







    share|improve this answer












    share|improve this answer



    share|improve this answer










    answered Aug 27 '10 at 20:39









    Avi Steiner

    43929




    43929








    • 17




      That is generally considered poor style. You should just write out "This object is less than that object." Occasionally, you'll see "foo is <0." This looks bad.
      – TH.
      Aug 27 '10 at 23:32








    • 10




      That's definitely true. However, if you're using LaTeX to organize your thoughts (as i often do), 'good style' equates to 'will I understand what I wrote if I come back and look at it in a week'!
      – Avi Steiner
      Sep 3 '10 at 3:30










    • @TH.: I agree with you. My experiency tells me too that text and math code should not be mixed up. Good style would be either writing "The variable $foo$ is less than zero." (as you mentioned) or "The variable $foo$ satisfies the relation/condition $foo<0$.", which would probably suit your application. Good style means also to define variables at the first use.
      – strpeter
      Dec 7 '13 at 8:07






    • 1




      @strpeter While mentioning style, it is worth noting that variable $foo$ is not good style either: it refers to the product of $f$, $o$, and $o$. You mean variable $mathit{foo}$.
      – akim
      Dec 8 '14 at 9:19










    • OK, I was not typing it correct in the sense of the variable as I focused on the operator. You're right - use your preferred version $mathit{foo}<0$, $mathrm{foo}<0$, $mathbf{foo}<0$, or whatever variable. ;)
      – strpeter
      Dec 8 '14 at 10:40














    • 17




      That is generally considered poor style. You should just write out "This object is less than that object." Occasionally, you'll see "foo is <0." This looks bad.
      – TH.
      Aug 27 '10 at 23:32








    • 10




      That's definitely true. However, if you're using LaTeX to organize your thoughts (as i often do), 'good style' equates to 'will I understand what I wrote if I come back and look at it in a week'!
      – Avi Steiner
      Sep 3 '10 at 3:30










    • @TH.: I agree with you. My experiency tells me too that text and math code should not be mixed up. Good style would be either writing "The variable $foo$ is less than zero." (as you mentioned) or "The variable $foo$ satisfies the relation/condition $foo<0$.", which would probably suit your application. Good style means also to define variables at the first use.
      – strpeter
      Dec 7 '13 at 8:07






    • 1




      @strpeter While mentioning style, it is worth noting that variable $foo$ is not good style either: it refers to the product of $f$, $o$, and $o$. You mean variable $mathit{foo}$.
      – akim
      Dec 8 '14 at 9:19










    • OK, I was not typing it correct in the sense of the variable as I focused on the operator. You're right - use your preferred version $mathit{foo}<0$, $mathrm{foo}<0$, $mathbf{foo}<0$, or whatever variable. ;)
      – strpeter
      Dec 8 '14 at 10:40








    17




    17




    That is generally considered poor style. You should just write out "This object is less than that object." Occasionally, you'll see "foo is <0." This looks bad.
    – TH.
    Aug 27 '10 at 23:32






    That is generally considered poor style. You should just write out "This object is less than that object." Occasionally, you'll see "foo is <0." This looks bad.
    – TH.
    Aug 27 '10 at 23:32






    10




    10




    That's definitely true. However, if you're using LaTeX to organize your thoughts (as i often do), 'good style' equates to 'will I understand what I wrote if I come back and look at it in a week'!
    – Avi Steiner
    Sep 3 '10 at 3:30




    That's definitely true. However, if you're using LaTeX to organize your thoughts (as i often do), 'good style' equates to 'will I understand what I wrote if I come back and look at it in a week'!
    – Avi Steiner
    Sep 3 '10 at 3:30












    @TH.: I agree with you. My experiency tells me too that text and math code should not be mixed up. Good style would be either writing "The variable $foo$ is less than zero." (as you mentioned) or "The variable $foo$ satisfies the relation/condition $foo<0$.", which would probably suit your application. Good style means also to define variables at the first use.
    – strpeter
    Dec 7 '13 at 8:07




    @TH.: I agree with you. My experiency tells me too that text and math code should not be mixed up. Good style would be either writing "The variable $foo$ is less than zero." (as you mentioned) or "The variable $foo$ satisfies the relation/condition $foo<0$.", which would probably suit your application. Good style means also to define variables at the first use.
    – strpeter
    Dec 7 '13 at 8:07




    1




    1




    @strpeter While mentioning style, it is worth noting that variable $foo$ is not good style either: it refers to the product of $f$, $o$, and $o$. You mean variable $mathit{foo}$.
    – akim
    Dec 8 '14 at 9:19




    @strpeter While mentioning style, it is worth noting that variable $foo$ is not good style either: it refers to the product of $f$, $o$, and $o$. You mean variable $mathit{foo}$.
    – akim
    Dec 8 '14 at 9:19












    OK, I was not typing it correct in the sense of the variable as I focused on the operator. You're right - use your preferred version $mathit{foo}<0$, $mathrm{foo}<0$, $mathbf{foo}<0$, or whatever variable. ;)
    – strpeter
    Dec 8 '14 at 10:40




    OK, I was not typing it correct in the sense of the variable as I focused on the operator. You're right - use your preferred version $mathit{foo}<0$, $mathrm{foo}<0$, $mathbf{foo}<0$, or whatever variable. ;)
    – strpeter
    Dec 8 '14 at 10:40










    up vote
    15
    down vote













    May be using some other sane font encoding, something like usepackage[T1]{fontenc} or something. (Well, I don't think any of this legacy font encoding and input encoding is sane any way).






    share|improve this answer

























      up vote
      15
      down vote













      May be using some other sane font encoding, something like usepackage[T1]{fontenc} or something. (Well, I don't think any of this legacy font encoding and input encoding is sane any way).






      share|improve this answer























        up vote
        15
        down vote










        up vote
        15
        down vote









        May be using some other sane font encoding, something like usepackage[T1]{fontenc} or something. (Well, I don't think any of this legacy font encoding and input encoding is sane any way).






        share|improve this answer












        May be using some other sane font encoding, something like usepackage[T1]{fontenc} or something. (Well, I don't think any of this legacy font encoding and input encoding is sane any way).







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Aug 26 '10 at 20:26









        Khaled Hosny

        21.4k172108




        21.4k172108

















            protected by percusse Mar 28 '16 at 17:08



            Thank you for your interest in this question.
            Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).



            Would you like to answer one of these unanswered questions instead?



            -

            Popular posts from this blog

            How to change which sound is reproduced for terminal bell?

            Image
            3 Recently upgrade to 18.10 from 18.04, and using the terminal is becoming annoying: the new alert sound is a drip ( /usr/share/sounds/gnome/default/alerts/drip.ogg ), and the previous one is still located at ( /usr/share/sounds/ubuntu/stereo/bell.ogg ). My issue is that at the gnome-terminal, when autocompleting or pressing left BOTH sounds are reproduced, at the same time. I want to just have ubuntu/stereo/bell.ogg active, not both . At the moment I have been only able to reduce the volume of the alerts (but still both are played), or turn the alerts down (but I dislike both "solutions"). gnome-terminal 18.10 teminal-bell share | improve this question
            Read more

            Title Spacing in Bjornstrup Chapter, Removing Chapter Number From Contents

            Image
            up vote 5 down vote favorite 2 I would like to make it so that the vertical space below the title of each chapter is the same when using the Bjornstrup package (i.e. so that the descenders do not affect the spacing - as shown by the red arrow in the picture below). I think I'm fairly happy with the spacing around "A chapter", so I'd really like titles without descenders (e.g. "Contents") to have the same vertical spacing as "A chapter" below the title. I would also like to remove the large "0" in the contents title. Any help appreciated, as always. documentclass[11pt,a4paper]{book} % Packages[![enter image description here][1]][1] usepackage[left=3.5cm, right=3.5cm, top=4.3cm, bottom=4.25cm]{geometry} usepackage[utf8]{inputenc} usepackage{libertine} usepackage[libertine]{newtx
            Read more

            Can I use Tabulator js library in my java Spring + Thymeleaf project?

            Image
            0 I want to add Tabulator js to my java project. I added tabulator.min.js, tabulator.min.css to resources folder. After that added to my html page these dependencies as recommending in readme.md. <link rel="stylesheet" th:href="@{/css/tabulator.min.css}"> <script type="text/javascript" th:src="@{/js/tabulator.min.js}"></script> Now my tables view all elements, that I have in the html page, but not correct. In the documentation of Tabulator is example how to create header and table, var table = new Tabulator("#example-table", { columns:[ {title:"Name", field:"name", sorter:"string", width:200, editor:true}, {title:"Age", field:"age", sorter:"
            Read more