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
I have the following example, the headings on bookmarks when opening pdf file show strange characters unlike if we use bidi
\RequirePackage{latexbug} \documentclass[a4paper]{book} \usepackage{hyperref} \usepackage[english, bidi=basic-r, layout=counters]{babel} \babelprovide[import=ar, main]{arabic} \babelfont{rm}{Amiri} \begin{document} \tableofcontents \chapter{مقدمة} \chapter{نظرة عامة} \section{وجه التسمية} \section{تاريخ} \subsection{التيار الكهربائي} \subsection{جدول التوزيع الإلكتروني} \end{document}
With bidi
\RequirePackage{latexbug} \documentclass[a4paper]{book} \usepackage{hyperref} \usepackage{fontspec} \usepackage[rldocument]{bidi} \setmainfont[Script=Arabic]{Amiri} \begin{document} \tableofcontents \chapter{مقدمة} \chapter{نظرة عامة} \section{وجه التسمية} \section{تاريخ} \subsection{التيار الكهربائي} \subsection{جدول التوزيع الإلكتروني} \end{document}
Bookmarks with babel
Bookmarks with bidi
The text was updated successfully, but these errors were encountered:
This is no LaTeX bug. Just load hyperref after babel with the unicode option.
hyperref
babel
unicode
\documentclass[a4paper]{book} \usepackage[english, bidi=basic-r, layout=counters]{babel} \usepackage[unicode]{hyperref} \babelprovide[import=ar, main]{arabic} \babelfont{rm}{Amiri}
Sorry, something went wrong.
No branches or pull requests
Brief outline of the bug
I have the following example, the headings on bookmarks when opening pdf file show strange characters unlike if we use bidi
Minimal example showing the bug
With bidi
Log file (required) and possibly PDF file
Bookmarks with babel
Bookmarks with bidi
The text was updated successfully, but these errors were encountered: