I am facing issue in Windows 10 (MS Word 2016) in printing a circle Ornament around Arabic Digits. It is displaying correctly in MS Word as required, but when I print it or make a PDF it just Print the Arabic Digits without Ornament, also same with generating PDF from MS Word.
But this is printing fine with Circle Ornament through NOTEPAD (Windows 10).
Also this is working and Printing perfectly in Windows 7 (Word2013).
I made a feature (Liga) to substitute the digit with Ornamental shape of Digit.
Does I am missing some setting in MS Word 2016 (Windows10).
Attached here sample Font and docx file.
Comments
Right now you've got:
feature liga { # Standard Ligatures
Should that not actually be:
My approach to handling this sign would be to first contextually substitute variant forms of numerals that will behave as marks within the enclosing ornament, and then use contextual GPOS to anchor either individual numerals or sequences of numerals correctly within the enclosing ornament. But a similar affect can be achieved using contextual kerning, which I believe is the method used in e.g. Microsoft's Arabic Typesetting font.
I test this sample on Windows 7, its working fine, You test it on Mac/MSWord, working fine, so why we need to add this 06DD.
This sample numbers(Font) is displaying fine in windows 10 (MSWord), may be it means Ligature substitution is working fine, but only problem is when I print, through windows 10 using MSWord, it does not print the outer Circle.
USING SAME WINDOWS 10 and NOTEPAD, THESE DIGITS ARE DISPLAYING AND PRINTING FINE WITH CIRCLE AS REQUIRED.
The only issue is when I print these digits through MSWord, it have problem, but when I Print same file through Notepad, in Windows 10, it prints OK.
So if the same numbers are printing OK, with circle in Windows 10 through Notepad and print Wrong (Without circle) through MSWord, What does this means.
I tried to help Ashfaq with some other issue he was having and was unable to reproduce the problems using the current version of word running under virtual windows 10 and, like these issues, he finds them in windows 10 but not windows 7. So I suspect that Office 2016 doesn't play well with the shaping engine used in Windows 10.
Unfortunately, whereas I have Mac systems dating back to 1984, I only have versions of Windows going back to Redstone 1, so was unable to test this.
Root cause is few places where GDI/Uniscribe is still used in Office, mainly on printing codepath.
Thanks,
Sergey
In my sample font attached in this post, I used Ligature Substitution feature;
Standard Ligature <liga>;
with this feature I was getting wrong printing result in Windows10, but now I try another feature;
Required Ligature <rliga>,
After using this feature <rliga> instead of <liga> now everything goes fine with windows10 word 2013,16. Now I can print numbers with outer circle as it is required now.
'rlig' is always on and cannot be turned off by the user.
'rlig' was originally proposed for Semitic languages (Arabic and Syriac). Its support for other scripts is somewhat inconsistent across applications.
It's not clear to me why your feature would work when implemented as 'rlig' but not as 'liga', but I'm glad you've solved your problem.