# Tag Info

7

The character maps of T2A and T1 are identical in the first 128 positions. So english texts should work fine with T2A. But if you want to insert umlauts and other accented chars from the upper part of the char table of T1-encoding you should consider to switch to T1 for such texts instead of relying on LaTeX to fall back to the correct definitions.

4

Polyglossia loads fontspec, but the default font is Latin Modern, which has no support for Cyrillic. You can load the Computer Modern Unicode fonts instead: \documentclass{article} \usepackage{fontspec} \setmainfont[Ligatures=TeX]{CMU Serif} \usepackage{polyglossia} \setdefaultlanguage{english} \setotherlanguage{russian} ...

2

There are three issues here: Glossary labels can't contain active characters (non-Latin characters, including accented letters such as é, are all active). This is because the label is used to define various control sequences used to store the glossary information. Older versions of glossaries had a problem with fragile commands in fields such as text. ...

8

Add the line \usepackage[T2A,T1]{fontenc} in the preamble so to have the right font encodings. Thus the MWE \documentclass{letter} \usepackage[utf8]{inputenc} \usepackage[T2A,T1]{fontenc} \usepackage[russian]{babel} \begin{document} \MakeUppercase{English Text. Русский текст.} \end{document} yields the desired result P.S.: The T1 option is not ...

Top 50 recent answers are included