Skip to content
This repository has been archived by the owner on Sep 27, 2019. It is now read-only.

funny ligatures with Arabic script #361

Closed
ralessi opened this issue Jun 8, 2016 · 6 comments
Closed

funny ligatures with Arabic script #361

ralessi opened this issue Jun 8, 2016 · 6 comments

Comments

@ralessi
Copy link

ralessi commented Jun 8, 2016

Hi Philipp,

This mwe:

\documentclass[12pt]{article}

\usepackage{luaotfload}

\font\arabicfont = {name:Amiri:script=arab} at 12pt

\begin{document}

\textdir TRT\arabicfont
اَلحِمَارُ، اَلجَدِيدُ، اَلحَارِثُ.

\end{document}

gives me this, where the last two words are obvioulsy wrong::
amiri

I suspect this issue may be related to the latest luaotfload and not to Amiri for XeLaTeX + fontspec do not have it. I checked the following mwe with `xelatex:

\documentclass[12pt]{article}

\usepackage{fontspec}

\newfontfamily\arabicfont[Script=Arabic]{Amiri}

\usepackage{polyglossia}
\setdefaultlanguage{arabic}

\begin{document}
اَلحِمَارُ، اَلجَدِيدُ، اَلحَارِثُ.
\end{document}

Best,

Robert

@ralessi
Copy link
Author

ralessi commented Jun 8, 2016

[Update] Other ligatures are broken too, as in the name of God for example. Let's assume that they all are related to one and the same issue.

@phi-gamma
Copy link
Member

Dear Robert,

thanks for reporting. I’m not qualified to judge that output but
I do notice the difference to the Xetex version.

This mwe:

\documentclass[12pt]{article}
\usepackage{luaotfload}
\font\arabicfont = {name:Amiri:script=arab} at 12pt
\begin{document}
\textdir TRT\arabicfont
اَلحِمَارُ، اَلجَدِيدُ، اَلحَارِثُ.
\end{document}

gives me this, where the last two words are obvioulsy wrong::
amiri

It happens in Context too, so it’s most likely a problem in the
fontloader:

http://i.imgur.com/ihnxEEs.png

(Clockwise starting at the top: Luatex, Context, Xelatex.)

I’ll forward the issue to Hans.
Philipp

@ralessi
Copy link
Author

ralessi commented Jun 10, 2016 via email

@ralessi
Copy link
Author

ralessi commented Jun 17, 2016

Many thanks, it now works like a charm!

@u-fischer
Copy link

I'm closing this as probably resolved. Feel free to reopen if something still isn't working.

@ralessi
Copy link
Author

ralessi commented Oct 8, 2018 via email

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants