We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
There is currently a formatting issue in which the existing ACL template breaks when using any Type 2A characters.
Authors have been instructed to follow the comment in the ACL 2023 template (% See https://www.latex-project.org/help/documentation/encguide.pdf for other character sets). Doing so points to the following:
\usepackage[T2A]{fontenc} %aaron https://www.overleaf.com/learn/latex/Russian %Hyphenation rules %-------------------------------------- \usepackage{hyphenat} \hyphenation{ма-те-ма-ти-ка вос-ста-нав-ли-вать} %-------------------------------------- \usepackage[english, russian]{babel}
Unfortunately, this appears to heavily affect the ACL template in such a way that it fails Pubcheck and visibly changes formatting.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
There is currently a formatting issue in which the existing ACL template breaks when using any Type 2A characters.
Authors have been instructed to follow the comment in the ACL 2023 template (% See https://www.latex-project.org/help/documentation/encguide.pdf for other character sets). Doing so points to the following:
\usepackage[T2A]{fontenc} %aaron https://www.overleaf.com/learn/latex/Russian
%Hyphenation rules
%--------------------------------------
\usepackage{hyphenat}
\hyphenation{ма-те-ма-ти-ка вос-ста-нав-ли-вать}
%--------------------------------------
\usepackage[english, russian]{babel}
Unfortunately, this appears to heavily affect the ACL template in such a way that it fails Pubcheck and visibly changes formatting.
The text was updated successfully, but these errors were encountered: