Using polyglossia package with \setdefaultlanguage{russian} stops producing en-dashes and em-dashes from -- and ---, respectively. Also, no more nice 'upper 99' quotemarks (or any other nice quotemarks) from U+0022.
With \setdefaultlanguage{english} or with default language I get those. With russian I don't. The closest I've come was with babelshorthands=true option, but there are three issues:
- the rendering result doesn't look nice (line thickness visibly varies, at least with this font),
- spacing with
"--(or"--~for that matter) and linebreak after"---, - and of course having to use sequences which are mightily inconvenient if writing text in Russian.
I could of course directly input U+2014 and U+2015 and nice quotemarks, but why the package exhibits such strange behaviour at all? No language set (English?) works nice.
I need hyphenation, or I'd just ditch polyglossia, and babel conflicts with something I need.
The MWE:
\documentclass{article}
\usepackage{fontspec}
\setmainfont{Liberation Serif}[Ligatures=TeX]
\newfontfamily\cyrillicfont{Liberation Serif}[Script=Cyrillic]
\usepackage{polyglossia}
% these work (german - in its own specific manner):
%\setdefaultlanguage{english}
%\setdefaultlanguage[babelshorthands=true]{german}
% these don't (strange results with babelshorthands on):
\setdefaultlanguage[babelshorthands=true]{russian}
%\setdefaultlanguage[babelshorthands=false]{russian}
%\setdefaultlanguage{russian}
% polyglossia version: 2023/02/11 v1.60
\begin{document}
..........
-- ~ "en-dash"
--- ~ "em-dash"
"-- ~ "babelshorthands en-dash"
"--- ~ "babelshorthands em-dash"
\end{document}
UPDATE: The suggested reference 'Quotes don't work with polyglossia?', while it offers a solution actually, doesn't qualify as a 'precise' duplicate, I think, because the OP's question there is formulated in such way so that's easy to miss the issue's relation to my question.


Ligatures=TeXfor the Cyrillic font as well. – Marijn Mar 06 '24 at 06:53\newfontfamily(and indirect also usage of correct starting and ending quotes. BTW: I would suggest to use packagecsquotesfor quotes like shown, e.g., at this question or this answer.) – cabohah Mar 06 '24 at 08:47(And I remember seeing lots of unwieldy TeX tricks in olden times.)
– yury10578 Mar 06 '24 at 08:52As for today, I just gave babel a quick try, and I'm honestly impressed. Maybe something will crop up yet, but I can't make it misbehave as of now, also with the mathspec sequence from my notes. I'm definitely 'taking it for a spin'.
Documentation is comprehensive and pleasant-looking. Version tags are quite a nice touch.
– yury10578 Mar 07 '24 at 11:34"work. To say it once again clearly:"for quotes is wrong! not only TeXnical but also typographical. There is nothing else I can or should say. – cabohah Mar 09 '24 at 09:41