-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
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
Using this font in XeLaTeX #1
Comments
I noticed that when we explicitly define that whitespace character in our content, XeLaTeX correctly identifies it..! Although this should not be required, it may give us a clue of what may be defected. I used the following XeLaTeX code (MarathiCursive 2.1 is used) :
In the above image, some characters are misplaced, but the topline is working correctly. Also, it may be possible that its a XeLaTeX bug. |
Newer version of XeTeX has |
@khaledhosny you were right on that count. I added |
@khaledhosny I diagnosed this issue a bit deeper and found that the misplacing of characters in XeLaTeX was due to the fact that I was not using I am sharing my code for someone finding references or help : \documentclass{article}
\usepackage{fontspec}
\newfontfamily\graphite[Renderer=Graphite]{MarathiCursiveG}
\XeTeXinterwordspaceshaping=2
\begin{document}
\graphite 𑘮𑘱 𑘦𑘻𑘚𑘲 𑘩𑘱𑘢𑘲 𑘁𑘮𑘹.
\end{document} Now speaking about Scribus, It currently does not have Graphite support, as mentioned in this open bug :
So it seems that this issue is completely solved. Thanks @khaledhosny & @MihailJP for their outstanding work in typography...! |
Hi,
thank you for this font! I could use this font in XeLaTeX; following is the MWE:
\documentclass{article}
\usepackage{polyglossia}
\setdefaultlanguage{marathi}
\newfontfamily{\devanagarifont}{MarathiCursiveT}
\setmainfont[Script=Devanagari]{MarathiCursiveT}
\begin{document}
मोडी मधील लाटेक्-वापरून बनवलेला पहिला दस्तऐवज.
\end{document}
However, in the output the line on the top of the words breaks when there is space in the source; this should not happen, and neither does this happen in Pages (OSX document editor). How can one overcome this issue?
The text was updated successfully, but these errors were encountered: