# Tag Info

0

I see no real problem: \documentclass{article} \usepackage{amsmath} \usepackage{kmath} \usepackage[no-math]{fontspec} \usepackage{polyglossia} \setmainfont[ UprightFont = *, ItalicFont = *Italics, SlantedFont = *Italics, BoldFont = *sb, BoldItalicFont = *sbi, BoldSlantedFont = *sbi, SmallCapsFont = *SmallCaps ]{Kerkis} ...

3

This is a ligature of two 's' characters, one following another. It was in common usage in English as well, until the end of the 1700s. A single "s" character was often drawn as an "f" without the crossbar. When two consecutive "s" characters were drawn, they were combined into the form about which you are asking. In English, the first character morphed ...

17

I don't know why Knuth designed the ß as it is in the cm-fonts. I don't quite remember why Jörg Knappen changed the look of the ß in the ec-fonts, but I do remember that there was some quite heated discussions about the choice. If you don't like both ß there is no much you can do (apart from redesigning the glyph yourself). But as the cm-super fonts ...

13

What you are complaining about is the "ß" of the dc fonts created by Jörg Knappen, the first 8 bit extension of the original 7 bit Computer Modern fonts. This was digitized in the cm-super fonts (see Latin Modern vs cm-super?). This new ß was disliked a lot when Jörg created the dc fonts (which later became the ec fonts). The ß as designed by Knuth (and ...

38

The glyph makes much more sense visually when seen as a ligature of long s and round s, one of the two traditional forms of the ß (the other, of course, being long s and z). Here's a comparison, using outlines from cm-unicode, version 0.6.3a: Here I've used f as a reference for the first part of the ligature, since I couldn't find a long s in cm-unicode. ...

17

I can't do anything about the font you are using but would recommend to use the lmodern fonts, a modernised variant of the Computer Modern fonts. \documentclass{minimal} \usepackage{lmodern} \usepackage[T1]{fontenc} \usepackage[utf8]{inputenc} \begin{document} \begin{center} Große Straße ließen gießen maßen heißt Spaß Fuß Maß Gruß reißend \end{center} ...

0

I don't know if it was mentioned before but you might try LuaLaTex or XeLaTeX which have genuine support for UTF8, means you can write äöüß how you want and all other characters too and don't have to worry about it normally. They have other advantages, too, like embedding other fonts easily etc. Just ensure you save the TEX files in UTF8 encoding.

26

It is for the Polish ł and Ł (l and L with stroke). Plain TeX contains \def\l{\char32l}. And LaTeX (OT1enc.def) defines \DeclareTextCommand{\l}{OT1} {\hmode@bgroup\@xxxii l\egroup} where \@xxxii stands for char32. \documentclass{article} \begin{document} \char32l \l \end{document}

22

From plain.tex: 663 \def\l{\char32l} 664 \def\L{\leavevmode\setbox0\hbox{L}\hbox to\wd0{\hss\char32L}} The glyph is used just for the Polish “suppressed l”. The support for Polish in Computer Modern is not complete, as the ogonek is missing, but, apparently, Knuth didn't need to typeset Polish names sporting the ogonek.

4

The behaviour is as designed but if you want to lose all (log-only) font warnings then: \documentclass{article} \makeatletter \def\@font@info#1{} \makeatother \usepackage{lmodern} %% see below \usepackage[T1]{fontenc} %% \begin{document} Hello \textbf{World \texttt{of} Code!} %% ^^^^^^^^^^^ \end{document} has 66 rather than ...

5

The font set up in beamer is somewhat non-standard (to get as much as possible in sans serif). If you want a more 'normal' arrangement, do \documentclass[professionalfont]{beamer} which will solve your issue here.

6

I'm using as example the \' accent instead of yours for easier markdown input. In OT-encoding the accent command \' is defined as \DeclareTextAccent{\'}{OT1}{19} So it puts at the end an accent from position 19 over an character a. In T1-encoding (t1enc.def) one find this definition: \DeclareTextComposite{\'}{T1}{a}{225} This means at the end \'a ...

2

From the discussion in comments the source of the problem was that the cm-super fonts were not installed and so bitmap fonts were used. In miktex the fonts can be installed with the package manager. In some installations it is necessary to run the command updmap after the installation to update the user map files.

Top 50 recent answers are included