The microtype package

CONFIGURATION FILES: Note on admissible characters 13715.4 Note on admissible charactersAll printable ASCII characters are allowed in the settings, with the followingexceptions (on the left hand side, the replacements on the right):\ : \textbackslash{ : \textbraceleft} : \textbraceright^ : \textasciicircum% : \%# : \#Comma and equal sign must be guarded with braces (‘{,}’, ‘{=}’) to keep keyvalhappy.Character commands are allowed as far as they have been defined in the properL A TEX way, that is, when they have been assigned a slot in the font encoding with\DeclareTextSymbol or \DeclareTextComposite. Characters defined via \chardefare also possible.Ligatures and \mathchardefed symbols have to be specified numerically. Ofcourse, numerical identification is possible in any other case, too.8-bit characters are also admissible, provided they have been declared in theinput encoding file. They should, however, only be used in private configurationfiles, where the proper input encoding is guaranteed, or else in combination withthe ‘inputenc’ key.15.5 Character inheritanceFirst the lists of inheriting characters. We only declare those characters that are thesame on both sides, i.e., not Œ for O.4659 4660 4661 %%% -----------------------------------------------------------------------4662 %%% CHARACTER INHERITANCE46634664 4665 15.5.1 OT1Glyphs that should possibly inherit settings on one side only: 012 (‘fi’ ligature),013 (‘fl’), 014 (‘ffi’), 015 (‘ffl’), Æ, æ, Œ, œ.4666 \DeclareCharacterInheritance4667 { encoding = OT1 }4668 { f = {011}, % ff4669 i = {\i},4670 j = {\j},4671 O = {\O},4672 o = {\o}4673 }4674